User-visible changes

1. A new default UI, that features both usability improvement and a better-looking default skin. This makes working with CPS a more enjoyable experience for end-users.
2. Switch from HTML 4.01 Transitional to XHTML 1.0 Strict, with work on accessibility (A-level by default, AA and AAA-level possible at the expense of some features).
3. AJAXification: use of AJAX techniques for a more responsive and more powerful UI (asynchronous form updates).
4. CPSSkins, which is a very powerful web-based WYSIWYG theme editor for CMF-based applications, has been integrated. It makes it easy for graphic designers or webmasters to modify the look of CPS without writing CSS or template code.
5. CPSPortlets, a web-based WYSIWYG portlet editor that makes it easy for content administrators to modify the presentation of information on a CPS site.
6. New applicative products have been added to the CPS default application: CPSBlog (for blogs), CPSWiki (for wikis), CPSOOo (to manage OpenOffice.org documents).
7. The webmail and shared calendar components have been completely rewritten. They are available as separate packages.
8. CPSGeo, a GIS product for CPS that allows for geolocation of documents in a CPS application. It is available as a separate package.

Architecture changes

1. We have switched to recent versions of Zope (2.9) and CMF (1.6).
2. We have switched most new developments to the Zope 3 component architecture, thanks to Five, the bridge between Zope 2 and Zope 3.
3. We now use of GenericSetup, the new "default", XML-based, configuration tool, instead of CPSInstaller. Using declarative configuration makes it now much easier to manage upgrades between versions
4. We have switched the unit and functional test harnesses to the Zope 2.9 layer-based test runner. This eases the creation and speeds up the execution for the 2543 tests included in the CPS source code so far.
5. We now use CPSUserFolder as a powerful replacement to UserFolder. CPSUserFolder makes it possible to use a user directory managed by CPSDirectory as a source of users in CPS.
6. DCWorkflow has been extended as CPSWorkflow to provide a document-based workflow engine with dynamic schemas support (inspired by the activity-based workflow model) that can handle any document-based business process. This hybrid model gives all the power and flexibility needed to define dynamic validation / review / delegation states to model any paper process you have in the real world, while keeping workflow modeling simple enough to be easily understood by users.
7. CPSRemoteController provides a Web Service interface to remotely control CPS portals (both from another CPS portal or from totally different applications) in a language-independent manner through XML-RPC. CPSRemoteController is also very handy for task automation.
8. CPSRelation provides a tool that manages RDF relations between content objects.
9. Many, speed optimisations, at both low level (including work on ZODB transactions and CPSCore internal optimizations) and high level (rendering of CPSDocument and CPSPortlets caches) to make it possible to manage applications with hundreds of thousands of documents (soon: millions of documents) and tens of gigabytes of data (soon: terabytes of data).

Packaging changes

CPS is now distributed as several packages.

• "CPS Platform": the ECM platform. It embeds all the infrastructure components that are needed to develop ECM applications. The primary audience for CPS Platform is developers.
• "CPS": the application. A standard full-featured content management application based on CPS Platform, that features a rich set of default content types, a blog, a wiki and a forum. The primary audience for CPS Platform is people that want to try out CPS, as well as internet or intranet sites administrators with minimal customisation needs. CPS is available both as source code packages, and binary installers for several popular platforms (including MS-Windows).
• "CPS Legacy": a set of old components which are either deprecated or currently unmaintained. These components are needed to upgrade older versions of CPS. The primary audience for CPS Legacy: internet or intranet sites administrators who need to upgrade old instances of CPS.

More information

An updated document "What's new in CPS 3.4", as well as more information like tutorials and screencasts, will be published on http://cps-project.org/ in the upcoming days.