This document discusses authoring content once and delivering it to multiple channels. It introduces experience fragments and content fragments in AEM that allow centrally editing reusable content and channel-specific content. It also discusses hybrid delivery that implements business logic once through Java models and renders multiple formats like HTML and JSON. The document provides examples of delivering content from AEM to different channels like websites, SPAs, mobile apps, emails, and voice/chat applications using APIs, editors, and integrations with other services.

1. #evolve19
AUTHOR ONCE -
DELIVER
EVERYWHERE
Amol Anand & Daniel Gordon
August 06 - 2019

2. #evolve19 2
KEY TAKEAWAYS
Authoring
Scale creation and
reuse of content
Delivery
Adjust to the needs of
specific channels
Hybrid CMS
How to effectively
manage omni-channel
content

3. #evolve19 3
EXPLOSION OF DIGITAL CHANNELS
Websit
e
Social
Media
Mobile
Apps
E-Mail
Digital
Signage
Wearables IOT
Challenges
|
How do I manage content for all these
channels?
How can I support all these different
technologies?

4. #evolve19 4
Traditional
CMS

5. #evolve19 5
Traditional
CMS
Headless CMS

6. #evolve19 6
Traditional CMS Headless CMS
Delivery
HTML
for traditional web pages
JSON
for traditional web pages
Editing In-Context of a Preview
for tailoring the content to the layout
Form-Based Interface
for authoring large amount of content
Content Unstructured
for text, images, videos, etc.
Structured
for semantic content types
Layout Defined by Author
for template-based layouts
Defined by Developer
for dynamic layouts
Architecture Single Application Stack
for longer-living technologies
Multiple Technologies
for shorter-living technologies
You will need both!

7. #evolve19 7
OMNI-CHANNEL AUTHORING
SCALE CREATION AND REUSE OF CONTENT

8. #evolve19 8
INDEPENDENT SYSTEMS
Cause content silos
😞 Message inconsistency
😞 Duplication of effort
😞 Wasted time and costs

9. #evolve19 9
HYBRID SYSTEM
Authors can
😍 Centrally edit reused
content
😍 Edit channel-specific
content

10. #evolve19 10
HYBRID SYSTEM
Authors can
😍 Centrally edit reused content
😍 Edit channel-specific content
AEM features to manage cross-channel content
Experience & Content Fragments

11. #evolve19 11
EXPERIENCE FRAGMENTS [XF]
An assembly of components that is stored centrally.
Experience Fragment Experience Fragment Component

12. #evolve19 12
CONTENT FRAGMENTS [CF]
A list of key-value pairs that is defined by an editable model
Content Fragment Model Content Fragment Content Fragment Component

13. #evolve19 13
Experience
Fragments
Content Fragments
Editing In-Context of a Preview Form-based Interface
Model
Composition of Existing
Models
Structured Editable Model
Content Includes Channel Layout Pure Content
Storage In XF Admin In Assets
Localization Language Copy + Live Copy Language Copy only
EXPERIENCE FRAGMENTS VS CONTENT
FRAGMENTS

14. #evolve19 14
OMNI-CHANNEL DELIVERY
OPTIMIZE FOR SPECIFIC CHANNELS

15. #evolve19 15
HYBRID DELIVERY
Implement business logic once:
Java Sling Models
Render multiple formats:
HTL templates render HTML
Jackson serialization renders
JSON

16. #evolve19 16
ASSETS HTTP API
Headless Content Management
– Create
– Read
– Update
– Delete

17. #evolve19 17
HEADLESS DELIVERY | JSON
Assets HTTP API Content Services
Purpose Interfacing systems Delivery to visitors
Operations Create, Read, Update, Delete Read only
Content Cross- Channel Channel specific
Content types Assets + CF only Any content
Customization No: fixed standard Yes: Custom Java Sling Models

18. #evolve19 18
DELIVERING TO EACH CHANNEL
websit
e
spa
mobile
email
voice / chat
content fragment
experience
fragment
HTML
Drag & Drop fragment onto AEM page and publish
/content/dam/wknd-events /events/<fragment>
/content/wknd/en/home.html
Sites Editor
end user

19. #evolve19 19
DELIVERING TO EACH CHANNEL
websit
e
spa
mobile
email
content fragment
experience
fragment
HTML
Drag & Drop fragment onto AEM page via SPA Editor and publish
/content/dam/wknd-events /events/<fragment>
/content/wknd-events/angular/home.html
SPA Editor
end user
model.jso
n
voice / chat

20. #evolve19 20
DELIVERING TO EACH CHANNEL
websit
e
spa
mobile
email
content fragment
mobile app points to AEM Content Services HTTP API endpoint
/content/wknd/en/api/events.json
mobile
app
same method for delivering JSON to any 3rd party
application
AEM
PUBLISH
TIER
1publish
fragment
2 3
AEM
AUTHOR
TIER
voice / chat
end user
experience
fragment/content/dam/wknd-events /events/<fragment>

21. #evolve19 21
DELIVERING TO EACH CHANNEL
websit
e
spa
mobile
email
content fragment
experience
fragment
Adobe I/O Runtime action triggers Adobe Campaign transactional email
AEM
PUBLISH
TIER
/api/assets/wknd-events
/events/<fragment>.json
end user
1
Adobe
Campaign
Adobe I/O
Runtime
2
kickoff I/O
runtime
sequence
3
get
fragment
details
4
trigger
transactional
email
publish
fragment
all workflow steps fully automated
voice / chat
/content/dam/wknd-events /events/<fragment>

22. #evolve19 22
DELIVERING TO EACH CHANNEL
websit
e
spa
mobile
email
voice / chat
all workflow steps fully
automated
content fragment
experience
fragment
Adobe I/O Runtime action feeds AEM content to Microsoft QnA Maker and Azure Bot
Services
AEM
PUBLISH
TIER
/content/wknd/en/api/events.json
1publish
fragment
Adobe I/O
Runtime
2
kickoff I/O
runtime
sequence
3
get all
fragments
4
update
QnA
Maker
Azure Bot
Services
QnA
Maker
chatbot
running on
AEM page
end user
/content/dam/wknd-events /events/<fragment>

23. #evolve19 23
KEY TAKEAWAYS
Authoring
Scale creation and
reuse of content
Delivery
Adjust to the needs of
specific channels
Hybrid CMS
How to effectively
manage omni-channel
content

24. #evolve19 24
ABOUT US
GitHub
/amol-anand
Twitter
twitter.com/iamolanand
Linkledin
/in/amolanand
Amol Anand
Principal Technical Architect
Adobe

25. #evolve19 25
ABOUT US
GitHub
godanny86
Twitter
twitter.com/godannyaem
Linkledin
/in/godanny
Photo placeholder
Daniel Gordon
Technical Marketing Engineer
Adobe

26. #evolve19
THANK YOU!