Friday, November 6, 2020

Content Fragments & Experience Fragments

 

Content Fragments

 

Content Fragments allow you to design, create, curate and publish page-independent content. They allow you to prepare content ready for use in multiple locations/over multiple channels.

Structured content in Content Fragments is defined in models that can contain a variety of content types; including text, numerical data, Boolean, date and time, and more. 

Content Fragments are stored as Assets and Authored and edited in the Content Fragment Editor.

Creating Content Fragment Models

Open http://localhost:4502/aem/start.html

Go to,

Tools à Assets à Content Fragments Models à Select Project Name à Create Model

Provide Model title and description

Open created Model and there are numbers of data types available.


To create content fragment model just drag and drop Data Types to left



Once a field has been added to the model, the right panel will show the Properties that can be defined for that particular data type. Here you can define what is required for that field. For example:


Click Save to save the definitions

Creating Content Fragments

1.       Navigate to the Assets folder where you want to create the fragment.

2.       Select Create, then Content Fragment to open the wizard.

The first step of the wizard requires you to specify the basis of the new fragment.

This can be a:

i)                    Template - for example Simple Fragment.

ii)                   Model - used to create a fragment that requires structured content; for example, the Airport model created above.

3.       All available templates and models are displayed select the required.

4.       After selection, select next to proceed.

5.       Provide Title and description.

6.       Edit the newly created fragment. In addition, provide values / Author it.


Using Content Fragment on page

1.       Add content fragment component on page

 

 


 

2.       Select created Content fragment path and Display Mode.



Experience Fragments

 

Experience Fragments allows content authors to reuse content across channels including Sites pages.

An Experience Fragment is a set of content that grouped forms an experience.

With Experience Fragments, marketers can:

·         Reuse an experience across channels

·         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.

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.

Creating Experience Fragments


While creating EF, It is recommended to:

·         Create a folder

·         Configure the allowed Experience Fragment templates for that folder.

1.      Select EF from Global Navigation


2.    Navigate to the created folder and select Create



3.    Select Experience Fragment to open the Create Experience Fragment wizard.

4.    Select the required Template, then click Next :



5.    Enter the Properties for your Experience Fragment.

Title is mandatory. If the Name is left blank, it will be derived from the Title.


Editing Experience Fragment

EF can be edited/authored like a normal site page.

1.    Drag and drop Container component on to page.

2.    Add Components as per requirement.

3.    For example, creating header needs Image, Title, List, Search component.

 

Using Experience Fragment

Open any site page, onto which you need your EF

Just drag and drop Experience fragment component on your page.

Configure the component and provide path to your EF.

 

No comments:

Post a Comment