http://portals.apache.org/images/Jetspeed_blue_med.png
Everything 
Jetspeed-2 is a complete rewrite of Jetspeed-1. It is the next-generation enterprise portal at Apache Portals. It's hard to pick out the coolest new feature. Some may think that the component architecture and Spring integration, others like CMS-based navigation model, and others like the standardization of portlet development. Personally, what is cool to me is the new community at Apache Portals, and how Jetspeed-2 fits into that community as the enterprise portal.
The complete answer of what is new in Jetspeed-2 is:
Jetspeed-2 is a part of an open enterprise development platform based on components and standards. You have an excellent deployment model and component integration framework that will enable people to write standard portlet applications and supporting components, and deploy them live to the portal.
Apache Portals provides a powerful integration platform for all kinds of enterprise software development. With Portals Bridges, you can now develop portlet applications with JSF, Struts, PHP, or Velocity. When the Portals applications project is accepted into Apache, we will have a community for developing vertical portlet applications that are not coupled to any portal server.
Jetspeed-2 Specifications
Features:
The target of the Apache Jetspeed 2 Documentation Project is to provide uptodate professional documentation for portal developers, portlet developers, system administrators and end-users.
Ron Wheeler (Use cases, General Documentation Coordination, Language Quality) since 2009.
=== Originals===
Marky Goldstein (General Documentation Coordination)
Benjamin Bratkus (General Documentation)
David Le Strat (Jetspeed 2 Website, Security Documentation)
Raphaël Luta
Robert Young (External Dependencies)
Philipp Mark Donaghy (Quick start for the impatient)
Ron Wheeler (Use cases, General Documentation Coordination, Language Quality) since 2009.
Spend a few minutes a day documenting... please sign in.
This is designed to support the development of a new custom portal. It includes includes overall system architecture and all of the features that are configured at the portal level.
This is documentation that an analyst or a programmer requires to develop a portlet that will run in a Jetspeed portal environment.
This is the information that a system administrator needs to know to install Jetspeed and get it ready to receive a portal developed by a third party or by an in-house development team. It deals with system requirements, installation and upgrade, backup, configuring the servlet container and tuning.
Since the end-user does not usually come into contact with Jetspeed, this is documentation is oriented to the administrative user and is about using the administration portlets that come with Jetspeed. This is also good reading for the other types of consumers mentioned above.
The following portals are built using the Jetspeed 2 engine:
(please list here)
