Silva CMS

This is a major release. The new architecture sports a state-of-the-art user interface, entirely AJAX-driven and much more user-friendly, responsive, and better performing. It includes a new content editor running on top of a new document type. Silva News Network has been refactored and provides advanced calendar functionality. On a system level, the performance of both the frontend and backend has been immensely improved.

Mobile skins based on browser detection. A robust reference management system that preserves links between resources. WSGI server support. A more consistent API. An improved testing infrastructure.

Images and linked objects use references. The form editor is gone; Documents (and News items in Silva News) are now rendered by default with XSLT. A content object cannot be deleted if it is the target of a reference. The XML import/export has been improved A Javascript pop up has been added to select references and uses the REST API. Silva supports WSGI servers. The z3c form has been replaced. The SMI uses silva.core.layout. Management of HTTP response headers has been improved. Better testing. A new test setup system. Silva integrates with Mobi, a middleware suite for detecting mobile devices.

The new TOC features made available in Silva 2.1 are now accessible within documents by using the TOC code source with the id “cs_toc”. Kupu now has merging and splitting table cells functionality for tables. External Sources can now have a preview in Kupu. DateTime widgets in the SMI now have a ‘calendar’ button which opens a popup calendar. The link and image tools were redesigned. Recursive publishing actions are now possible. Indexer objects now use IntIDs. Files and images now support blob storage. A local site feature has been introduced.

This release adds a range of features for Author/Editors (such as 'elaborate' Code Sources, an "Editor Comments" toolbox, much more configurable Automatic Table of Contents, preview with public layout, and an improved Lookup Window) and for Site Managers (e.g. a quota subsystem, Zope Pluggable Authentication Service, authentication with OpenID, and a CAPTCHA). It has performance and technical improvements such as functional tests.