Experience Fragment Basics in AEM 6.4
AEM 6.4 provides headless(Content as a service) CMS capabilities through Content Fragments and Experience Fragments.
What is an experience fragment?
The headless capability to create experiences can be used to deliver content to third party system/touchpoint through various methods. AEM provides experience fragments which has content and layout, and third party applications then deliver to the end user. Experience Fragments helps reuse of content.
An 'Experience Fragment' is a collection of components with its own content and layout.
Scenarios when an AEM Experience Fragment to be used?
There are times when we need to replicate same type of page section in other pages. 'Experience Fragments' can help us saving time in this case. Also cases like AEM is used as headless CMS, where AEM to be just used as content storage, not for delivery. In this case AEM Experience Fragment will be available for a third party rendering system for consuming.
Cases when we need multiple version of content, Experience Fragments are a good option.
Additional notes:
Experience Fragments allow to manage sections of experiences that can easily be reused and distributed. They are template based and allow live copy relationship. At present AEM 6.3 supports Experience fragments to html5 web templates, Pinterest and Facebook templates. Custom templates can be created if required.
AEM 6.4 provides headless(Content as a service) CMS capabilities through Content Fragments and Experience Fragments.
What is an experience fragment?
The headless capability to create experiences can be used to deliver content to third party system/touchpoint through various methods. AEM provides experience fragments which has content and layout, and third party applications then deliver to the end user. Experience Fragments helps reuse of content.
An 'Experience Fragment' is a collection of components with its own content and layout.
- Each Experience Fragment is based on a template which gives a structure.
- Each experience fragment has one/many components with its own layout.
- Each experience itself makes sense.
- Created with intention of reuse, re ordered, resized.
- Experience Fragments works on Caas model, with each fragment can be created with multiple variations.
Scenarios when an AEM Experience Fragment to be used?
There are times when we need to replicate same type of page section in other pages. 'Experience Fragments' can help us saving time in this case. Also cases like AEM is used as headless CMS, where AEM to be just used as content storage, not for delivery. In this case AEM Experience Fragment will be available for a third party rendering system for consuming.
Cases when we need multiple version of content, Experience Fragments are a good option.
Experience Fragments allow to manage sections of experiences that can easily be reused and distributed. They are template based and allow live copy relationship. At present AEM 6.3 supports Experience fragments to html5 web templates, Pinterest and Facebook templates. Custom templates can be created if required.
Can you help me with step by step guide to create a custom experience fragment template ?
ReplyDelete