Within Adobe Experience Manager as a Cloud Service, an Experience Fragment:
An Experience Fragment:
You can use Experience Fragments:
Content Fragments and Experience Fragments are different features within AEM:
Experience Fragments can contain content in the form of Content Fragments, but not the other way around.
For further information see also Understanding Content Fragments and Experience Fragments in AEM.
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:
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.
allocate the allowed templates at the folder level
You can use the template editor to create your own template.
The WKND project structures some Experience Fragments according to
Contributors. The structure used also illustrates how other features, such as Multi Site Management (including language copies), can be used.
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 can 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.
See Templates for Experience Fragments for further details.
Select Save and Close.
It is not recommended to change the Allowed Templates by this method, as the templates specified can 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:
See Templates for Experience Fragments for further details.
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.
Tags from the Experience Fragment template will not be merged with tags on this Experience Fragment root page.
These are completely separate.
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 the page editor.
The following example procedure illustrates how to create a teaser for a product:
Drag and drop the required component from the Components Browser.
Depending on the component:
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, 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, within 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 left tab (Local), and can be selected for further action:
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.
When editing an Experience Fragment available Building Blocks are displayed in the left-hanf tab. You can filter according to:
Personalization on your Experience Fragment allows you, as a marketer, to define target audiences for the Experience Fragment just once, then re-use the fragment in any page. This:
You can create an Experience Fragment with multiple components grouped inside this single fragment. You can also create variations of the fragment for each specific audience segment, then reuse these Experience Fragments across the required channels.
Personalization is achieved by defining the Personalization properties on either the Experience Fragment or variation, or the folder containing the fragments; this means that inheritance can override personalization properties.
Configuring these properties also enables the Targeting mode in the Experience Fragment editor.
To personalize your fragment:
Navigate to the required location in the Experience Fragments console.
Select either a folder or your fragment, then Properties from the toolbar.
Personalization properties defined on a folder will be inherited by all child folders down through the sub-tree, and Experience Fragments (and variations) within that sub-tree. They can be overridden by breaking the inheritance.
Open the Personalization tab to define and save your settings. For example, on a folder:
When a fragment is embedded in a Sites page, and Personalization has been configured, then only the personalization version of the page will be used at page rendering time.
For the targeting performed on the components in a fragment to work at page rendering, the following conditions must be met:
The ContextHub Path selected in the Personalization tab must be either:
The Segments Path selected in the Personalization tab must be either:
Once the personalization properties have been configured, the Targeting mode will be available when the fragment is opened for editing.
This mode operates in the same manner as for page editing. See Targeting mode for the Page Editor for more details.
Details of your fragment can be seen:
Navigate to the location of your Experience Fragments (do not navigate further down to the variations within the fragment).
Details are shown in all views of the Experience Fragments console, with the List View including details of an export to Target:
When you open the Properties of the Experience Fragment:
The properties are available in various tabs:
These tabs are shown when you open Properties from the Experience Fragments console.
If you Open Properties when editing an Experience Fragment, the appropriate Page Properties are shown.
.plain. selector in the URL, you can access the plain HTML rendition from the browser.
Although this is directly available from the browser, the 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.
Publishing your Experience Fragment is basically the same as publishing a page (though from the Experience Fragments console or editor).
Alternatively you can also publish to Preview (again from the Experience Fragments console or editor).
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, JSON can also be used. See: