Content Fragments Vs Experience Fragment

Content Fragments Vs Experience Fragment

Content Fragment :

- Presentation Agnostic i.e. they can be used in any type of presentation layer. This is achieved using exposing the content fragments in the form of JSON.
- They're of dam:asset type
- Can have several versions like mobile version, tablet version, third party version etc
- Can be created using Content Fragment Model
- Content centric i.e. contents matter not the presentation
- They're composed of form elements like text, date, text area etc
- Can be exported as JSON
- Content fragment model has to be enabled to create content fragment for a site
- Can be created dynamically and used on any channel
- Not meant for larger sizes of content paragraphs
- Advanced version of sling reference component
- It is about reusing the contents

Create content fragment model -> Author content fragment in assets -> Define content services template using editable templates (Empty template) -> Use components like text, image, content fragment or content fragment list -> Author content service page using the content fragment page template created in previous step -> Publish -> View json page the page by putting pagename.model.json.

- Content fragment can be used by third party

Scenario :

i. When dynamic changes in the contents are required frequently. For example events page, vacations planning page, service catalog page, small scale product information catalogs
ii. Multichannel sites
iii. News websites
iv. Legal disclaimers on different channels


Experience Fragment :

- Presentation Centric  : Look and feel matters
- They're of cq:Page type
- Can have several variations based on the channel. Can also have social media specific form which can be created using social post
- Can be created using editable templates
- Can also be created using layout container on a page
- Not necessarily has to be a page, it can be collection of components inside layout container.
- They're composed of components like text component, list component, image component or combination of all
- Can be exported as HTML
- Can be different variation on different channels
- Live copies can be created
- Building blocks
- Experience fragment is about reusing the whole experience across different channels

Create experience fragment template using editable templates (xfpage type) -> go to sites and create experience fragment and select the template -> Ensure experience template policy allows the components you want to use on experience template -> define experience fragment -> Publish

- Experience fragment can be used by third party as simple html pages.

Scenario :
i. Emails
ii. Omnichannel experience
iii. Sites with personalized experiences (by integrating with target)
iv. Embedded on different sites as web component like RSS feed (like detached experiences)