Publish Content Fragments

Content Fragments are discrete pieces of content in Adobe Experience Manager. They are structured content based on a content model. Content Fragments are pure content without design or layout information. They can be authored and managed independently of the channels that Adobe Experience Manager supports. Content Fragments are modular, where content is broken down into smaller components.

Experience Manager Guides allows you to publish a topic or its elements to a content fragment.

NOTE
You can choose only those elements in a topic that have an id attribute defined.

To create a Content Fragment, perform the following steps:

  1. Create a Content Fragment model in Adobe Experience Manager Assets.

  2. Create a folder where you want to save the Content Fragments that you create based on the Content Fragment model. For example, “stock-content-fragments”.

  3. Edit the folder’s properties (for example, “stock-content-fragments”) and add the path of the folder, which contains the Content Fragment model in the cloud configuration.
    For example, add /conf/we-retail in the cloud configuration. This configuration connects all the Content Fragment models with the folder.
    add cloud configuration details in the folder properties {width="650"}
    Add the cloud configuration in the folder properties to connect it with the fragment models.

  4. To generate a Content Fragment, select New Output new output icon from the Outputs section in the File Properties of a topic.

  5. Select Content Fragment.
    file properties options tab {width="300"}

    Add a new Content Fragment from the File Properties of a topic.

  6. In the Generate Content Fragment dialog box, fill in the following details under the General and Mapping tabs.

    General tab
    Add the fragment model and mapping details in the Publish as Content Fragment dialog
    Add the path, name, title, and condition filtering to publish a topic or its elements as a Content Fragment.

    • Path: Browse and select the path of the folder where you want to publish the Content Fragment. If you select an existing Content Fragment, it overwrites the contents of the mapped fields.

    • Title: Type the title of the Content Fragment. By default, the title is populated with the title of the topic. You can edit it. This title is used to generate the name of the Content Fragment.

    • Name: Type the name of the Content Fragment. By default, the name is populated with the title of the topic, and the spaces are replaced with ‘_’. For example, sample_content_fragment. You can edit it. This name is used to generate the URL for the Content Fragment.

    • You can select different conditions to create content fragment variants. Select one of the following options:

      note note
      NOTE
      Conditions are enabled only if condition attributes are defined in the topic.
      • None: Select this option if you don’t want to apply any condition on the published output.
      • Using DITAVAL: Select the DITAVAL file to include or exclude specific content in the generated output. You can select the DITAVAL file using the browse dialog or by typing the file path.
      • Using attributes: You can define condition attributes in your DITA topics. Then, select the condition attribute to publish the relevant content.

    Mapping tab

    Add the fragment model and mapping details in the Publish as Content Fragment dialog

    Select the content fragment model, and add the mapping details to publish a topic or its elements as a Content Fragment.

    • Model: Select the Content Fragment model that you want to use to create your Content Fragment. The models are picked from the folder, which you have configured on Experience Manager Guides server.

    • Mapping: You can view the topic elements that have an id attribute applied to them. Drag the topic elements to the fields present in the content fragment model.
      The right side is populated with the published Content Fragment contents in case of an existing Content Fragment. These can be overwritten with the topic contents if necessary. You can also select Undo to revert the mapping changes.

      note note
      NOTE
      If you are using 4.4 or earlier versions, select a mapping from the drop-down. It picks the mappings from the contentFragmentMapping.json file. Your administrator can add the mappings in the contentFragmentMapping.json file. Learn more about how to create a mapping between a topic and a Content Fragment in the Installation and Configuration Guide.
  7. Click Generate to publish the Content Fragment.

  8. You can view the Content Fragments for a topic under the Outputs section in the File Properties.

    View the Content Fragments for a topic {width="300"}

    View the Content Fragments present for a topic and republish them.

Once you’ve published the Content Fragments, you can also use them in any Adobe Experience Manager Site.

Options menu for a Content Fragment

You can also perform the following actions for a Content Fragment from the Options menu:

  • Generate: Republish the Content Fragment to update it with the latest content from the DITA topic. When you regenerate the output, you can change the path, name, title, model, and mapping of the Content Fragment. You can also select different conditions while regenerating the output.

  • Duplicate: Duplicate a Content Fragment. You can change the path, name, title, model, and the mapping. You can also select different conditions when you duplicate a Content Fragment to create a Content Fragment variant.

  • Remove: Remove a Content Fragment from the outputs list. A confirmation prompt appears. Once you confirm, the Content Fragment is removed from the Outputs list.

    note note
    NOTE
    No content is deleted from the Content Fragment by this action.
  • View: View the Content Fragment editor. You can also make changes and save them.

Improved Non-UUID to UUID content migration

The new UUID content migration script has been significantly optimized, making the content migration from Non-UUID to UUID 30 times faster than the earlier script. It includes features such as resuming from checkpoints, live insights, estimated completion time, and detailed reporting, ensuring a harmonious migration process. Notably, the migration process preserves asset metadata without any changes. The script has been tested and verified on a large dataset of 3 million assets, confirming its efficiency and reliability for large-scale migrations.

Learn more about Non-UUID to UUID content migration.

recommendation-more-help
11125c99-e1a1-4369-b5d7-fb3098b9b178