Content Fragments and Experience Fragments
Adobe Experience Manager’s Content Fragments and Experience Fragments may seem similar on the surface, but each play key roles in different use cases. Learn how Content Fragments and Experience Fragments are similar, different, and when and how to use each.
Comparison
Content Fragments architecture
The following diagram illustrates the overall architecture for AEM Content Fragments
-
Content Fragment Models define the elements (or fields) that define what content the Content Fragment may capture and expose.
-
The Content Fragment is an instance of a Content Fragment Model that represents a logical content entity.
-
Content Fragment variations adhere to the Content Fragment Model, however, have variations in content.
-
Content Fragments can be exposed/consumed by:
- Using Content Fragments on AEM Sites (or AEM Screens) via the AEM WCM Core Components’ Content Fragment component.
- Consume Content Fragment from headless apps using AEM Headless GraphQL APIs.
- Exposing a Content Fragment variations content as JSON via AEM Content Services and API Pages for read-only use cases.
- Directly exposing Content Fragment content (all variations) as JSON via direct calls to AEM Assets via the AEM Assets HTTP API for CRUD use cases.
Experience Fragments architecture
-
Editable Templates, which in turn are defined by Editable Template Types and an AEM Page component implementation, define the allowed AEM Components that can be used to compose an Experience Fragment.
-
The Experience Fragment is an instance of an Editable Template that represents a logical experience.
-
Experience Fragment variations adhere to the Editable Template, however, have variations in experience (content and design).
-
Experience Fragments can be exposed/consumed by:
- Using Experience Fragments on AEM Sites (or AEM Screens) via the AEM Experience Fragment component.
- Exposing an Experience Fragment variations content as JSON (with embedded HTML) via AEM Content Services and API Pages.
- Directly exposing an Experience Fragment variation as “Plain HTML”.
- Exporting Experience Fragments to Adobe Target as either HTML or JSON offers.
- AEM Sites natively supports HTML offers, however, JSON offers require custom development.