Its ppt for Content and Experience Fragment features of AEM. I will upload video of demo soon.

1. E X P E R I E N C E F R A G M E N T S
A N D
C O N T E N T F R A G M E N T S

2. WHAT IS CONTENT FRAGMENT?
• Content Fragments are editorial content, primarily text and related images.
• They are pure content, without design and layout.
• Adobe Experience Manager (AEM) Content Fragments allow you to design, create, curate and use
page-independent content.
• They allow you to prepare content ready for use in multiple locations/over multiple channels.

3. CONTENT FRAGMENTS ALLOW YOU TO:
• Consider how to reach target audiences efficiently across channels.
• Create and manage channel-neutral editorial content.
• Build content pools for a range of channels.
• Design content variations for specific channels.
• Add images to your text by inserting assets (mixed-media fragments).

4. CONTENT TYPE
• Content Fragments are a content type that:
• Are without layout or design (some text formatting is possible in Rich Text mode).
• Contains one or more:
– Text elements
– Assets that have been inserted; i.e. images
– References to associated assets (for example, images, fragments)
• Are independent from the delivery mechanism (i.e. page, channel).
• Can contain variations of content; this allows you to adjust the fragment text according to the specific editorial or channel
requirements.
• Are defined by a Fragment Template.

5. • Stored as Assets:
– Content fragments (and their variations) can be created and maintained from
the Assets console.
• Used in the page editor by means of the Content Fragment component (referencing
component):
– The Content Fragment component is available to page authors. It allows them to reference
the required content fragment.

6. CONSTITUENT PARTS OF A CONTENT
FRAGMENT
Fragment Elements Fragment Metadata Master Variations
Fragment
Paragraphs
Assets Inserted into
a Fragment (Mixed-
Media Fragments)
Associated Content

7. CONTENT FRAGMENTS AND CONTENT SERVICES
AEM Content Services are
designed to generalize the
description and delivery of
content in/from AEM
beyond a focus on web
pages.
They provide the delivery
of content to channels that
are not traditional AEM
web pages, using
standardized methods that
can be consumed by any
client. These channels can
include:
Single Page Applications
Native Mobile Applications
other channels and touch-points
Delivery is made in JSON
format.
AEM Content Fragments
can be used to describe
and manage structured
content. Structured
content is defined in
models that can contain a
variety of content types;
including text, numerical
data, boolean, date and
time, and more.

8. DEMO

9. EXPERIENCE
FRAGMENT

10. EXPERIENCE FRAGMENT
• An Experience Fragment is a group of one or more components including content and
layout that can be referenced within pages. They can contain any component.
• An Experience Fragment is a set of content that grouped forms an experience that
should make sense on its own.

11. EXPERIENCE FRAGMENT:
Is a part of an
experience (page).
Can be used across
multiple pages.
Is based on a
template (editable
only) to define
structure and
components.Is made up of one
or more
components, with
layout, in a
paragraph system.
Can contain other
experience
fragments.
Can be combined
with other
components
(including other
Experience
Fragments) to form
a complete page
Can have different
variations, which
may share content
and/or
components.
Can be broken
down into building
blocks that can be
used across
multiple variations

12. WITH EXPERIENCE FRAGMENTS
MARKETERS CAN:
– Reuse an experience across channels (both owned channels and 3rd party touch-points)
– Create variations of an experience for specific use-cases.
– Keep variations in sync with the use of Live Copy.
– Social Post experiences to Facebook and Pinterest out of the box.

13. YOU CAN USE EXPERIENCE FRAGMENTS:
If an author wants to re-use parts (a fragment of an experience) of a
page, they need to copy and paste that fragment. Creating and
maintaining these copy/paste experiences is time-consuming and
prone to user errors. Experience Fragments eliminate the need for
copy/paste.
To support the headless CMS use-case. Authors want to use AEM only for authoring
but not for delivering to the customer. A third party system/touchpoint would
consume that experience and then deliver to the end user.

14. BUILDING BLOCKS WITH EXPERIENCE FRAGMENTS
EDITABLE TEMPLATES USED FOR
CREATING EXPERIENCE
FRAGMENTS SHOULD HAVE
THE BUILDING BLOCK
COMPONENT ADDED TO ITS
POLICIES.
IT LETS CONTENT AUTHORS CREATE A
BUILDING BLOCK CONSISTING OF
COMPONENTS THAT COULD BE RE-USED
TO CREATE CONTENT ACROSS DIFFERENT
VARIATIONS AND ACROSS DIFFERENT
TEMPLATES.

15. WHEN SHOULD YOU USE EXPERIENCE FRAGMENTS?
Whenever you want to reuse experiences.
• Experiences that
will be reused with
When you use AEM as a content delivery platform for third parties.
• Any solution that
wants to use AEM
If you have an Experience with different variations or renditions.
• Channel or
context-specific
When you use Omnichannel Commerce.
• Sharing
commerce-related

16. DEMO

17. C O N T E N T F R A G M E N T S A N D
E X P E R I E N C E F R A G M E N T S
C O M P A R I S O N

18. Content Fragments (CF) Experience Fragments (XF)
Definition Re-usable, presentation-
agnostic content , composed of
structured data elements (text,
dates, references, etc.)
A re-usable, composite of one
or more AEM Components
defining content and
presentation that forms
an experience which makes
sense on its own
Core Content-centric Presentation-centric
Design and layout agnostic. Defines design and layout of
content
The channel owns the
presentation of the Content
Fragment’s content (layout and
design)
•Used "as is" in channels

19. Content Fragments (CF) Experience Fragments (XF)
Features • Variations
• Versions
• Synchronization of content across
variations
• Visual diff of Content Fragment
versions
• Annotations of multi-line text
elements
• Intelligent summarization of multi-
line text elements.
• Translation/localization
•Variations
•Variations as Live Copies
•Versions
•Building blocks
•Annotations
•Responsive layout and preview
•Translation/localization

20. Content Fragments (CF) Experience Fragments (XF)
Technical details Implemented as a dam:Asset Implemented as a cq:Page
Defined by a Content
Fragment Model
•Defined by Editable
Templates
•Native HTML rendition
Variations The Master variation is the
canonical variation
Variations are channel or
context specific
Variations are use-case
specific, which may align with
channels.
Building blocks allow content
re-use across variations
Use AEM Core Components
Content Fragment
component for use in AEM
Sites, AEM Screens or in
Experience Fragments.
AEM Experience Fragment
component for use in AEM
Sites, AEM Screens or other
Experience Fragments.

21. Content Fragments (CF) Experience Fragments (XF)
JSON export via AEM Content
Services for 3rd party
consumption
Export as Plain HTML for use by
3rd party systems
Building blocks allow content re-
use across variationsJSON via
AEM HTTP Assets APIs for 3rd
party consumption.
•HTML export to Adobe
Target for targeted offers
•JSON export to Adobe Target
for targeted offers
Common Use Cases Long-form editorial content
(multi-line element)
Content managed outside the
life cycle of the channels
delivering it
Content re-used across multiple
pages in a Web site.
Web site chrome (ex. header and
footer)