Experience Fragments and Content Fragments - High level differences

For reusing content, we have two great implementations available in AEM - Experience Fragments(XF) and Content Fragments(CF).
It is important to understand the differences between the two which will help us arrive at when to use what based on our project/content set up. 

Experience Fragments Content Fragments
Composed of one or more AEM components Composed of structured/form-based data elements
The content part of XF is any AEM components as such - Text, Image or any custom component part of our project.
ie. Presentation-centric 		 The content part of CF is text/image content in the form of direct text type/RTE/Date type/Dropdown/Reference type for referencing any asset
ie. Content-centric
Created using Editable templates, implemented/treated as an AEM Page Created using Content Fragment Model, implemented/treated as an AEM Asset
List of allowed components in XF can be controlled via policies in Editable templates Content in CF can be configured as different elements in Content Fragment Model.
Different elements refer to -> Textfield, Multiline text/RTE, Date field, Dropdown field, reference field, etc.
Eg: Header/Footer of a page can be designed as XF page where the logo/image component + Navigation component can be part of it.  Eg: Event details content can be designed as CF where we can configure Event Title(Textfield), Event Description(RTE), Event Date(Datefield), Any asset related to Event(reference field), Event Venue (Dropdown field)
Variations can be created out of Master XF -
  • Standalone variation by associating different Editable template.
  • Variation as a Live Copy 
 Variations can be created out of Master CF.
No Live copy action. However, there exists a Synchronization option for variation to sync the master content -
  • This will work only for Multiline text type element/RTE + 
  • Changes will flow from Master -> Variation only
Usage: 
  • Can be used in site pages via AEM core XF component
  • Can be exposed as a plain HTML using ".plain" selector in XF URL
  • Can be exported to Adobe Target as an HTML/JSON
 Usage: 
  • Can be used in site pages via AEM core CF component
  • Can be used in XF page if content fragment component is allowed via policies in the respective editable template
  • Can be exposed as a JSON via AEM content services for 3rd party consumption.

Reference: Adobe helpx links.

Comments

Post a Comment

Popular posts from this blog

Embedding Third party dependency/OSGi bundle in AEM application hosted in AEMasCS

Image
This post illustrate the ways of embedding third party dependency in AEM maven project. Steps are mentioned considering the project structure to be followed for AEMasCS while the same can be followed for classic versions too.  Before we begin, I would like to explain the scenario of including a dependency in our AEM maven project.  When we would like to make use of an API that is not already available in our project, we look for that in maven-central repository and specify the dependency in main pom.xml and desired module's pom.xml file. (Lets say, AWS S3 Java SDK V2 dependency) Upon updating the project in the IDE, we would see our class files (making use of those APIs) are compiled/build successfully without any errors.  Now, in the context of AEM/OSGi environment, when the same package and hence the bundle is deployed to AEM instance, dependencies that we added new might not be resolved/available in the OSGi as a bundle. Something like the below This indicates that the added dep
Read more

OSGI Factory Configuration implementation

OSGI Factory configuration is used to have many instances of an OSGI config (represented/identified via an identifier) for the single OSGI service/PID. Most often used OOB Factory configurations for example: Logger Factory/writer configuration (for log statements) Service user Mapper service Amendment (for using service resource resolver in projects) Few sample real time use case for the need of OSGI factory config: For multi tenant projects, if we have generic service used across tenants with properties/attributes specific to tenant. For single tenant, generic service targeting all locales with properties/attributes specific to locale. (where generic service -> holds logic in the lines of calling third party service for retrieving/updating information.) Implementation: ( In terms of OSGI R6 annotations ): Create Object Class Definition(OCD) defining desired properties for the OSGI service. - OSGIFactoryConfigOCD.java OSGI Service/Factory service to retrieve
Read more

Creation of Template Types for Editable templates

Image
In this post, we will create templates types which is the base for creating editable templates. Before getting to the subject directly, have added an introduction about templates in general. Template is the base for creating pages. Starting AEM 6.2, we have categorisation for templates - Static and Editable templates. Static templates :  This has been available for several versions of AEM/CQ Created using "Create Template" option with base page component as resourceType (which is responsible for rendering the page structure).  Template ( base page component as resourceType ) -> Page This cannot be edited as such. Since it just holds a reference to base page component, any changes to the page (other than authorable components), would need a change in base page component which is ultimately a work of developer. (calls for a code change) Allowed components are configured using Design mode (list being saved to etc/designs/projectfolder/templatename/jcr:content)
Read more