In this session we'll be introducing the Web Quick Start and taking a detailed look at the elements that sit in the background to make the system work. We'll be covering the content model, custom behaviours, rendition configuration, the publishing mechanism, and how user feedback is processed. Finally, we'll give a demonstration of it all in action.

1. Web Quick Start under the covers 1 Brian Remmington Alfresco Product Architect, WCM

2. Web Quick Start 2 The WQS model Behaviours tied to the model Asset collections Generating renditions Processing received feedback The publishing mechanism Primary goal: To equip you with knowledge of how the WQS works under the covers so you can take it, use it, and extend it What we’ll cover

3. The Web Quick Start model 3

4. The content model 4

5. Section behaviours – SectionType.java 5 Create an index page Create a collections folder Create default collections 3 asset collections by default Default asset collections are configurable by overriding a List bean: wqsmodule_sectionAssetCollections Upon creation Convert images to ws:image Convert text to ws:article Apply ws:webasset aspect Render Office documents as PDF Prevent the conversion to ws:image and ws:article type by overriding a Set bean: wqsmodule_sectionTypesToIgnore Upon child being added

6. More behaviours 6 On add aspect Set initial published time Generate renditions On update content Generate renditions Before delete Place deletion on the publish queue Assets – WebAssetAspect.java VisitorFeedbackType.java TaggableAspect.java TagScopeAspect.java WebSiteType.java … All in the same package: org.alfresco.module.org_alfresco_module_wcmquickstart. model And yet more…

7. Asset collections 7 Groups of assets that are uniquely named within the scope of a particular section Static asset collections Editor control over which assets are included Dynamic asset collections Configured with a search query, maximum number of results, and a refresh period in minutes The query is executed periodically (as configured), and the results are placed in the asset collection CMIS and Lucene supported

8. Dynamic asset collections 8 Queries can contain references to sections using the “section” placeholder: ${section:.} is the section that owns the asset collection ${section:/} is the root section of the website ${section:..} is the parent of this collection’s section ${section:/news/global} is the section at the path “news/global” from the root etc…

9. Generating renditions 9 Each section may define what renditions should be created when an asset is added or updated The configuration allows rendition definitions to be related to asset types (both by content type and MIME type) Rendition definitions are defined in a Spring bean named “wqsmodule_renditionDefinitions”(defaults are in the file “rendition-context.xml”) Each section may either inherit the rendition configuration from its parent section or not

10. Receiving and processing feedback 10 Each website has a corresponding data list for feedback (auto-created) New entries are periodically processed – each type of feedback can have its own handler defined CommentFeedbackProcessorHandler feedbackType = “Comment” ContactFeedbackProcessorHandler feedbackType = “Contact Request” <bean id="commentFeedbackProcessorHandler" parent="feedbackProcessorHandler" class="org.alfresco.module.org_alfresco_module_wcmquickstart.jobs.feedback.CommentFeedbackProcessorHandler"> <property name="feedbackType" value="Comment" /> </bean>

11. The publishing mechanism 11 Each website has a publishing queue WQS has a PublishService that processes the queues (“org_alfresco_module_wcmquickstart_publishingService” bean) Two processes defined: “wswf:publishTree” and “wswf:reviewPublish” Two actions defined: “webqs_publishTree”and “webqs_publish”

12. The publishing mechanism cont’d 12 Queues are published periodically – every minute by default (override with property wcmqs.publishQueueProcessor.schedule) Each website node may specify another website node that it publishes to A configurable node crawler is used to publish other nodes that the published ones depend on (override by specifying a replacement for the “wqsmodule_publishingCrawlerConfigurer”bean) A reconfigured transfer service is used to do the publishing

14. Learn More 15 wiki.alfresco.com forums.alfresco.com twitter: @AlfrescoECM