Managing Content Fragments

You're viewing help content for version:

Note:

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.

Content Fragments are stored as Assets, so are primarily managed from the Assets console.

Note:

Content fragments are then used with authoring pages; see Page Authoring with Content Fragments.

Note:

See Developing Content Fragments for further information on templates.

At the top level of the Assets console, select Files and navigate to (and/or create) the required folder.

Select Create, then Content Fragment to open the wizard.

Select the appropriate Template for your fragment type, then proceed with Next.

In the Properties step specify:

Basic
- Title
  The fragment title.
  Mandatory.
- Description
- Tags
Advanced
- Name
  The name; will be used to form the URL.
  Mandatory; will be automatically derived from the title, but can be updated.

Select Create to complete the action, then either Open the fragment for editing or return to the console with Done.

In the Assets console a range of actions are available for your content fragments, either:

From the toolbar; after selection of your fragment all appropriate actions are available.
As quick actions; a subset of actions available for the individual fragment cards.

Select the fragment to reveal the toolbar with applicable actions:

Create
Checkout
Properties
- Allows you to view and/or edit the fragment's metadata.
Edit
- Allows you to open the fragment for editing content together with its elements, variations, associated content and metadata.
Manage Tags
To Collection
- Add the fragment to a collection.
- This can also be done when associating a collection with the fragment.
Copy/Paste
Move
Publish/Unpublish
Relate/Unrelate
Delete
Download
- Save the fragment as a ZIP file; you can define whether to include Elements, Variations, Metadata. The zip package will:
  - Include any text content; eg *.txt
  - Include any referenced mixed-media; eg *.png
  - Not include associated Asset collections.

Note:

Many of these are standard actions for Assets and/or the Desktop App.

Content Fragments must be published for use in the publish enviroment. They can be published:

After creation; from the Assets console.
When you publish a page that uses the fragment; the fragment will be listed in the page references.

Caution:

After a fragment has been published and/or referenced, AEM will display a warning when an author opens the fragment for editing again. This is to warn that changes to the fragment will affect the referenced pages as well.

To delete a fragment:

In the Assets console navigate to the location of the content fragment.

Select the fragment.

Note:

The Delete action is not available as a quick action.

Select Delete from the toolbar.

Confirm the Delete action.

Caution:

If the fragment is already referenced in a page you will then see a warning message and be required to confirm that you want to proceed with a Force Delete. The fragment, together with its content fragment component, will be deleted from any content pages.

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices | Online Privacy Policy

Managing Content Fragments

Creating a New Content Fragment

Actions for a Content Fragment

Publishing and Referencing a Fragment

Deleting a Fragment

Ask the Community

Contact Us