Mike November

The external content module provides a mechanism to make content from various external systems available within SilverStripe in a standard and familiar manner. Items from external content sources can be linked to and worked with as though they are normal SilverStripe data objects, while pulling the information through from the third party content provider. Additionally, content can be imported from the external system into native SilverStripe content items. 

Some examples include

• Connecting to a CMIS compliant document management system (eg Alfresco, Knowledge Tree, Nuxeo) and being able to view files and metadata via your SilverStripe website
• Viewing content from the filesystem as though it were SilverStripe content
• Connecting to Microsoft Sharepoint
• Connecting to another SilverStripe installation and duplicating content from one to another

The Queued Jobs module provides a framework for SilverStripe developers to define processes that should be run as background tasks. This asynchronous processing allows users to continue using the system while long running tasks proceed when time permits. It also lets developers schedule these processes to be executed in the future.

The kinds of jobs that can benefit from being executed as background tasks

• Sending emails
• Processing a file upload / import
• Publishing a page in the future
• Generating a google sitemap

The Pixlr module integrates the Pixlr image editor within the CMS, allowing the creation of new images, and modification of existing images. 

A different way of writing APIs for SilverStripe applications

This module changes SilverStripe's object access module to be locked down as the default case, meaning that by default, there are NO permissions to an object except those explicitly granted to a user on a node (or tree), with the exception of admin users, who always have full access to all objects)

The new model of permission access has a few concepts that are slightly different to the existing model, and draws off the model seen in Alfresco

• Permissions - low level units describing a capability. For example, View, Write, Publish, ChangePermissions. When writing code and you need to check permissions, these are the things checked against
• Roles - Groupings of permissions. For example, an Editor role is made up of the View and Edit permissions
• Authority - a user or a group within the system
• Grant - Being explicit about whether a user can or cannot do something (a permission is GRANTed or DENY'd to an authority)