You're viewing help content for version:


See also Content Fragment Updates and Content Services - Feature Packs Release Notes.

This set of Feature Packs delivers updates to Content Fragments, the JSON Exporter and Core Components.

These enable the definition of structured content for the fragments; together with the updated JSON
exporter, this structured content can then be used to deliver AEM content via
Content Services to channels other than AEM pages. 

Adobe Experience Manager (AEM) Content Fragments allow you to design, create, curate and use page-independent content. They allow you to prepare content ready for use in multiple locations/over multiple channels.


Content Fragments and Experience Fragments are different features within AEM:

  • Content Fragments are editorial content, primarily text and related images. They are pure content, without design and layout.
  • Experience Fragments are fully laid out content; a fragment of a web page.

Experience Fragments can contain content in the form of Content Fragments, but not the other way around.

This and the following pages cover the tasks for creating, configuring and maintaining your content fragments:


These pages should be read in conjunction with Page Authoring with Content Fragments.

The number of communication channels is increasing annually. Typically channels refer to the delivery mechanism, either as the:

  • Physical channel; e.g. desktop, mobile.
  • Form of delivery in a physical channel; e.g. the "product detail page", "product category page" for desktop, or "mobile web", "mobile app" for mobile. 

However, you (probably) do not want to use exactly the same content for all channels - you need to optimize your content according to the specific channel.

Content fragments allow you to:

  • Consider how to reach target audiences efficiently across channels.
  • Create and manage channel-neutral editorial content.
  • Build content pools for a range of channels.
  • Design content variations for specific channels.
  • Add images to your text by inserting assets (mixed-media fragments).

These content fragments can then be assembled to provide experiences over a variety of channels.


Content fragments are not available in the classic UI.

The Content Fragment component can be seen in the classic UI sidekick, but further functionality is not available.


AEM also supports the translation of fragment content. See Creating Translation Projects for Content Fragments for further information.

Content Type

Content fragments are:

  • Stored as Assets:
    • Content fragments (and their variations) can be created and maintained from the Assets console.
  • Used in the page editor by means of the Content Fragment component (referencing component):
    • The Content Fragment component is available to page authors. It allows them to reference the required content fragment.

Content Fragments are a content type that:

  • Are without layout or design (some text formatting is possible in Rich Text mode).
  • Contains one or more:
    • Text elements
    • Assets that have been inserted; i.e. images
    • References to associated assets (for example, images, fragments)  
  • Are independent from the delivery mechanism (i.e. page, channel).
  • Can contain variations of content; this allows you to adjust the fragment text according to the specific editorial or channel requirements.
  • Are defined by a Fragment Template.

Fragments with Visual Assets

To give authors more control of their content, visual assets (images) can be added to and/or integrated with a content fragment. 

Assets can be used with a content fragment in several ways; each with its own advantage(s):

  • Insert Asset into a fragment (mixed-media fragments)


    Visual assets inserted into the content fragment itself are attached to the preceding paragraph. When the fragment is added to a page these assets are moved in relation to that paragraph when in-between content is added.

  • Associated Content 

    • Are connected to a fragment; but not a fixed part of the fragment (see Constituent Parts of a Content Fragment).
    • Allows some flexibility for positioning.
    • Are easily available for use (as in-between content) when using the fragment on a page.
    • See Associated Content for more information.
  • Assets available from the Assets browser of the page editor

    • Allow full flexibility for selection of an asset.
    • Allows some flexibility for positioning.
    • Does not provide the concept of being approved for a specific fragment.
    • See Assets Browser for more information.

Content Fragments throughout AEM

Constituent Parts of a Content Fragment

The content fragment assets are made up of the following parts (either directly or indirectly):

  • Fragment Elements

  • Fragment Metadata

    • Use the Assets metadata schemas.
    • Tags can be created when you:
      • Create and author the fragment
      • Or later:
        • By viewing/editing the fragment Properties from the console
        • By editing the Metadata when in the fragment editor
  • Master

    • An integral part of the fragment
      • Every content fragment has one instance of Master.
      • Master cannot be deleted.
    • Master is accessible in the fragment editor under Variations.
    • Master is not a variation as such, but is the basis of all variations. 
  • Variations

    • Renditions of fragment text that are specific to editorial purpose; can be related to channel but is not compulsory, can also be for ad-hoc local modifications.
    • Are created as copies of Master, but can then be edited a required; there is usually content overlap between the variations themselves.
    • Can be defined during fragment authoring or pre-defined in fragment templates.
    • Stored in the fragment, to help avoid scattering of content copies.
    • Variations can be synchronized with Master if the Master content has been updated.
    • Can be Summarized to quickly truncate the text to a predefined length.
    • Available under the Variations tab of the fragment editor.
  • Fragment Paragraphs

    • Blocks of text, within an element or variation, that are separated by vertical spaces (carriage return).
    • In the Rich Text and Markdown modes, a paragraph can be formatted as a header, in which case it and the following paragraph belong together as one unit.
    • Enable content control during page authoring.
  • Assets Inserted into a Fragment (Mixed-Media Fragments)

    • Assets inserted into the actual fragment and used as the internal content of a fragment. Typically images.
    • Are embedded in the paragraph system of the fragment.
    • Can be formatted when the fragment is used/referenced on a page.
    • Can only be added to, deleted from, or moved within, a fragment using the fragment editor. These actions cannot be made in the page editor.
    • Can only be added to, deleted from, or moved within, a fragment using Rich Text format in the fragment editor.
    • Are attached to the preceding text (paragraph).


    Can be (inadvertently) removed from a fragment by switching to Plain Text format.


    Assets can also be added as additional (in-between) content when using a fragment on a page; using either Associated Content or assets from the Assets browser.

  • Associated Content

    • This is content external to, but with editorial relevance for, a fragment. Typically images, videos or other fragments.
    • The individual assets within the collection are available to be used with the fragment in the page editor, when it is added to a page. This means that they are optional, depending on the requirements of the specific channel.
    • The assets are associated to fragments via collections; associated collections allow the author to decide which assets to use when they are authoring the page.
      • Collections can be associated to fragments via templates, as default content, or by authors during fragment authoring.
      • Assets (DAM) Collections are the basis for the associated content of fragments.
    • Optionally you can also add the fragment itself to a collection to aid tracking. 
  • In-Between Content


    This content is not stored within the content fragment itself, but on a page that the fragment is used on.

Required by Fragments

To create, edit and use content fragments you also need:

  • Fragment Template

    • Required to create a fragment.
    • Defines the structure of a fragment (title, number of text elements, tag definitions, variations, associated collections).
    • Template definitions require a title and one text element; everything else is optional. The template defines a minimal scope of the fragment and associated default content if applicable. Authors can later extend a fragment beyond what is defined in the template.  
    • Does not define channels (at least not directly). It defines variations that can be used for channels. Channels themselves (delivery) are defined and controlled by components.
  • Content Fragment Component

    • Required to reference the fragment on a page.
    • Responsible for layout and delivery of a fragment; i.e. channels. 
    • Fragments need one or more dedicated components to define layout and deliver some or all elements/variations and associated content.
    • Dragging a fragment onto a page in authoring will automatically associate the required component.

Example Usage

A fragment, with its elements and variations, can be used to create coherent content for multiple channels. When designing your fragment you need to consider what will be used where.

We.Retail Sample