BEdita is a Web development framework that comes with a full-featured content management system out of the box. BEdita 3 is a solid software environment, fully compatible and respectful of Web standards. The user interface has been developed in accordance with well-established rules in usability and ergonomics, but it is also practical and enjoyable. BEdita has been built upon CakePHP, the well known framework, from which it inherits the MVC design pattern. Moreover, a number of third party libraries and tools have been used, like JQuery, Smarty, and so on.
Bike is a Web application framework that can make feature-rich applications using HTML files only. You need no database setup (by default), no scheme definition, and no command-line voodoo. Just put a good old HTML file under skin/, and your new app is already running. Bike is front-ended by Rack, back-ended by Sequel.
HTMLSplicer is a toolkit that provides methods to compose complex HTML documents from simpler HTML documents, called templates. It can be used to generate servlet responses in Java Web applications, without adopting a full-fledged presentation layer framework like JSP, JSF, Apache Wicket, or GWT.
JWt (Java Web Toolkit) is a library for developing accessible and interactive Web applications with an API that is widget-centric and inspired by desktop GUI APIs. To the developer, it offers abstraction of Web-specific implementation details, including graceful degradation. Under the hood, the library uses the latest techniques when available to handle events and update the user interface.
Kohana is a PHP 5 framework that uses the Model View Controller architectural pattern. It aims to be secure, lightweight, and easy to use. Although it reuses many common design patterns and concepts, there are some things that make Kohana stand out. It is community driven, uses strict PHP 5 OOP to provide visibility protection, automatic class loading, overloading, interfaces, abstracts, and singletons, and is extremely lightweight. Kohana has no dependencies on PECL extensions or PEAR libraries. Large, monolithic libraries are avoided in favor of optimized solutions.