If an author wants to re-use parts (a fragment of an experience) of a page, he has to copy and paste that fragment. Creating and maintaining these copy/paste experiences is time-consuming and prone to user errors.
Supporting 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.
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 part of an experience that in itself makes sense.
- has one or multiple components with a layout within a paragraph system.
- can be combined with other Experience Fragments to a complete experience/page.
- can be reused, reordered and resized across pages.
- can have different variations and may share content and / or components.
- can be a set of experiences that make sense to group.
- is based on a template to define structure and components.