Immerse 2016 Efficient publishing with content fragments

© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
A virtual developer conference for Adobe Experience
Manager
Efficient Publishing with Content Fragments
Stefan Grimm | Senior Developer

© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 3
Content Fragments
A brief introduction

© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 4
Ecosystem

 Simple fragment template
 Generic component
 Typical AEM workflow required
 First, create the fragment
 Then, create a page, add the fragment to the page, configure it, etc.
OOTB

 Some use-cases require a more efficient workflow.
 OOTB component can be too generic
 Too much flexibility
 Not enough flexibility
Some use-cases require customization
 Customizing the component
 Implement a specific workflow
Context

Use-case:
A (imaginary) news site

Our goal …

 Create article.
 Enter title. Teaser. Text.
 Assign image(s).
 Classify.
 Save.
 Create page.
 Add Content Fragment.
 Reference article.
 Publish.
Efficiency!
let’s get rid of these steps!
add this new feature

Our news site
Section
Title
Teaser
Image
Text

 Fragment Elements
 Title
 Teaser
 Text
 Metadata
 Section
 Associated Content
 Image (tagged)
Articles
defining the article imagedefining the article image

 Article template
 Article component
 Page component
 A patched version of the CFM implementation bundle
 Required for AEM 6.2 only, will be included in upcoming releases
Prerequistes
Introduced in the ”Introducing Content Fragment” session

Hands on …
Prerequisites
13

Implementation

No production-ready code
in this session!
Disclaimer
15

Problems & solutions

 How to determine the article image?
 Only collections, no 1:1 assignment for associated content
 How to automate …?
 page creation
 adding Content Fragment component
 referencing & configuring the article fragment
 publishing the page
Problems ...

 Article image
 Use tagging to classify the images
 main image
 part of image gallery
 …
 Component queries associated content
 uses first image tagged as “main image”.
 Automating
 workflow launcher triggers workflow
 create page if necessary
 publish fragment, page & dependency
 several other stuff
... and solutions

Finding the article
image

 Article image
 main image
 …
 Automating
Recap

Getting associated collections:
Iterator<Resource> collections = fragment.getAssociatedContent();
Getting all associated resources:
SlingScriptHelper ssh = getSlingScriptHelper();
ContentFragmentManager cfm = ssh.getService(ContentFragmentManager.class);
List<Resource> assets = cfm.resolveAssociatedContentFlat(fragment);
API – Accessing associated content

Hands on ...
Finding the article image
22

Workflow commons

 Article image
 main image
 …
 Automating
Recap

 Can be registered on low level events
 node create
 node update
 Can‘t use directly
 intermediate saves
 but workflow should only be triggered on “save”
Workflow launcher

 On save
 Timestamp is persisted (only if content has been modified)
 jcr:content/lastFragmentSave (*)
 Each workflow process
 Executes only if there has been a “save” since the last publish workflow has been finished
 jcr:content/lastFragmentSave > jcr:content/lastFragmentPublish
 At the end of the publish workflow
 Updates publish timestamp
 jcr:content/lastFragmentPublish
(*) patched CFM implementation bundle required
Solution

Hands on ...
Workflow commons
com.adobe.immerse2016.cfm_ep.workflow.AbstractFragmentProcess
com.adobe.immerse2016.cfm_ep.workflow.FinishArticleProcess
27

Workflow process:
Resolving associated
content

Problem:
 Article image defined via collection
 Collections should not be used on publish
Solution:
 Determine article image on save
 Persist path to image on fragment
 jcr:content/articleImage
Article image

Hands on ...
Resolving dependencies
com.adobe.immerse2016.cfm_ep.workflow.ResolveDataProcess
30

Workflow process:
Creating the article
page

 Check if a page for the article has already been created
 If not, create a page, …
 Path: /<root>/<section>/<year>/<month>/<day>/<article.name>
 ... create the article paragraph
 jcr:content/par/<article.name>
 ... reference the article fragment.
 jcr:content/par/<article.name>/fileReference
Page on demand

Hands on ...
Auto-create article page
com.adobe.immerse2016.cfm_ep.workflow.CreateOnDemandProcess
33

Workflow process:
Publishing the article
page

 Publish
 Content Fragment
 Page
 Article Image
 In a clean implementation …
 … publish references (Tags, ...)
 … replicate only if modified
Publishing

Hands on ...
Publish article process
com.adobe.immerse2016.cfm_ep.workflow.PublishArticleProcess
36

And … Action!
The new, effective publishing
process
37

Recap
 Article image
 Part of a collection
 Identified by tag
 Resolve collection/tag to image path for publish instance
 Publishing workflow
 Triggered by workflow launcher
 Processes check for “save” event by comparing save/publish timestamps
 Page created on demand using a fixed/hardcoded pattern
 Fragment & collaterals published programmatically

Epilogue

Not mentioned in this session …
 Dispatcher invalidation
 No easy OOTB solution for invalidating referencing pages
 Can be solved using path-based dispatcher rules

Resources
 Content Package with example code
 available from the “Resources” pod in Adobe Connect
 Documentation
 Overview/Authoring
 Editor - https://docs.adobe.com/docs/en/aem/6-2/author/assets/content-fragments.html
 Page Authoring - https://docs.adobe.com/docs/en/aem/6-2/author/page-authoring/content-
fragments.html
 Development
 Templates - https://docs.adobe.com/docs/en/aem/6-2/develop/templates/content-fragment-
templates.html
 Extending (WIP) - https://docs.adobe.com/docs/en/aem/6-2/develop/extending/content-fragments.html

Q&A
42
Stefan Grimm
sgrimm@adobe.com

Immerse 2016 Efficient publishing with content fragments

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (19)

Andere mochten auch

Andere mochten auch (7)

Ähnlich wie Immerse 2016 Efficient publishing with content fragments

Ähnlich wie Immerse 2016 Efficient publishing with content fragments (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Immerse 2016 Efficient publishing with content fragments