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:
You can use Experience Fragments:
Write access for experience fragments requires the user account to be registered in the group:
Please contact your system administrator if you are experiencing any issues.
Experience Fragments should be used:
Whenever you want to reuse experiences.
When you use AEM as a content delivery platform for third parties.
If you have an Experience with different variations or renditions.
When you use Omnichannel Commerce.
It is recommended to:
use folders to organize your Experience Fragments,
Creating folders allows you to:
create a meaningful structure for your Experience Fragments; for example, according to classification
It is not necessary to align the structure of your Experience Fragments with the page structure of your site.
You can use the template editor to create your own template.
The following example shows Experience Fragments structured according to
Contributors. The structure used also illustrates how other features, such as Multi Site Management (including language copies), can be used.
The following screenshot was taken from the WKND site using Adobe Experience Manager as a Cloud Service.
To create and configure a folder for your Experience Fragments it is recommended to:
It is also possible to configure the Allowed Templates for your instance, but this method is not recommended as the values may be overwritten upon upgrade.
This is the recommended method for specifying the Allowed Templates, as the values will not be overwritten upon upgrade.
Navigate to the required Experience Fragments folder.
Select the folder, and then Properties.
Specify the regular expression for retrieving the required templates in the Allowed Templates field.
Select Save and Close.
It is not recommended to change the Allowed Templates by this method, as the templates specified may be overwritten upon upgrade.
Please use this dialog for information purposes only.
Navigate to the required Experience Fragments console.
Select Configuration options:
Specify the required templates in the Configure Experience Fragments dialog:
To create an Experience Fragment:
Select Experience Fragments from the Global Navigation.
Navigate to the required folder and select Create.
Select Experience Fragment to open the Create Experience Fragment wizard.
Select the required Template, then Next:
Enter the Properties for your Experience Fragment.
A Title is mandatory. If the Name is left blank it will be derived from the Title.
A message will be displayed. Select:
The Experience Fragment Editor offers you similar capabilities to the normal page Editor. See Editing Page Content for more information on how to use it.
The following example procedure illustrates how to create a teaser for a product:
Drag and drop a Category Teaser from the Components Browser.
Select Configure from the component toolbar.
Add the Asset and define the Properties as required.
Confirm the definitions with Done (tick icon).
Add more components as required.
You can create variations of your Experience Fragment, depending on your needs:
Open your fragment for editing.
Open the Variations tab.
Create allows you to create:
Define the required properties:
Confirm with Done (tick icon), the new variation will be shown in the panel:
You can now use your Experience Fragment when authoring your pages:
Open any page for editing.
Create an instance of the Experience Fragment component, by dragging the component from the Components browser to the page paragraph system:
Add the actual Experience Fragment to the component instance; either:
Edit, in the component toolbar, operates as a shortcut to open the fragment in the fragment editor.
You can select one or more components to create a building block for recycling within your fragment:
To create a new Building Block:
In the Experience Fragment editor, select the components you want to re-use:
From the components toolbar, select Convert to building block:
Enter the name of the Building Block, and confirm with Convert:
The Building Block will be shown in the tab, and can be selected in the paragraph system:
Your building block is visible in the Building Blocks tab. For each block, the following actions are available:
You can drag your building block to the paragraph system of any fragment, as with any component.
.plain. selector in the URL, you can access the plain HTML rendition.
This is available from the browser, but its primary purpose is to allow other applications (for example, third party web apps, custom mobile implementations) to access the content of the Experience Fragment directly, using only the URL.
The plain HTML rendition adds the protocol, host and context path to paths that are:
of the type:
or end with:
Links always reference the publish instance. They are intended to be consumed by third parties, so the link will always be called from the publish instance, not the author.
By default, Experience Fragments are delivered in the HTML format. This can be used by both AEM and third party channels alike.
For export to Adobe Target, HTML is used. See Target Integration with Experience Fragments for full information.