Since 2.0 is new and provides many enhancements and new features, please help to document them with us. Send documentation patches and use the Wiki. Thanks in advance :)

More documentation (work in progress) can be found at the Apache Lenya Wiki. Please treat the Wiki with care for now, as much of the information there is outdated.

Download

You find different download options on the download page.

What's New in Lenya 2.0

Modularization: The monolithic architecture has been replaced by a small generic core and various modules for specific purposes. This makes the codebase easier to understand and simplifies making custom functionality available in multiple publications.
Improved Repository Access: The refactored and extended repository API and new protocols make it easier to access and manipulate documents.
UUIDs for Internal Links: Documents are now identified and referenced using UUIDs. Static link rewriting is not necessary anymore.
Assets Are Treated as Documents: There is no distinction between XML and binary documents anymore. Images, PDFs and other non-XML documents are now managed using the resource resource type. This simplifies both API and user interface.
Improved Access Control: It is now possible to explicitly deny permissions on specific pages.
Configurable Meta Data: Additionally to the default Dublin Core meta data, you can now declare your own custom meta data element sets. For each meta data element, you can specify if it can be edited using the GUI or if it is used for internal purposes only.
Publication Templating: Publication templating allows to re-use common functionality in multiple publications. All resources, like layout images, CSS, XSLT and Cocoon sitemap files, are inherited to child publications unless you explicitely override them.
Usecase Framework: The usecase framework simplifies the implementation of user interaction functionality. It is not necessary to implement Cocoon sitemaps for each usecase anymore.
Simplified Notification, Inboxes: It is now easier to trigger notification messages. Each user has a personal inbox to read and send messages.