Brian Remmington, Architect of Content Management of Alfresco lead us through the content model, custom behaviors and publish mechanisms upon which the Web Quick Start solution is based during the session, Web Quick Start: Under the Covers at the Alfresco Developers Conference NYC 2010.

Web Quick Start is a sample application built on the Alfresco WCM platform. Providing an end-to-end authoring and publishing solution using Alfresco Share and a web application built using Spring MVC, Spring Surf and OpenCMIS, sites are delivered dynamically using Alfresco as a CMIS runtime. 

Designed for both business and developers, the Alfresco WCM can be up and running in a short a time. A Quick Start (QS) website, consisting of sections, assets and asset collections, is designed to be even simpler.


The Quick Start (QS) model

Section Behaviors

Sections are basically folders with additional metadata and behavior, and assets are basically files with additional metadata and behavior that are located inside sections.

Asset Collections

Asset collections are groupings of assets that are published to your website. There are two types: static and dynamic. Static collections let editors choose which assets are included. Dynamic collections are configured with a search query, maximum number of results and a refresh period in minutes.

Generating Renditions

The Alfresco Rendition Service is used throughout Web Quick Start and allows content to be reformatted dynamically for the web. Used primarily for resizing images, producing flash previews of PDF documents and internally, for producing PDF web assets from business documents, the processing of renditions is governed by Alfresco behaviors.

Processing User Feedback

Each website has a corresponding data list for feedback, which are auto-created. Visitor feedback assets, like blog comments have a rating property. Each asset has a total comment count and an average rating summarizing the feedback for the asset.

Publishing Mechanism

Each website has a publishing queue that is driven by workflow. WQS has a PublishService that processes the queues. Articles are placed on a website's publishing queue when they have gone through the approval workflow, or on deletion.

Remmington showed us real life examples of WQS in action. Editors can easily interact through an interface to choose asset collections, schedule publishing process and execute search queries. Though a technical presentation, the ultimate aim of WQS is to simply workflow processes so as to streamline information and make collaboration seamless.