Working with Content Fragments working-with-content-fragments

Managing Content Fragments - create your content fragments; then edit, publish and reference

Content Fragment Models - enabling, creating and defining your models

Variations - Authoring Fragment Content - author the fragment content and create variations of the Master

Markdown - using markdown syntax for your fragment

Using Associated Content - adding associated content

Metadata - Fragment Properties - viewing and editing the fragment properties

Simple fragments

• These have no predefined structure. They contain only text, and images.
• These are based on the Simple Fragment template.

Fragments that contain structured content

• These are based on a Content Fragment Model, which predefines a structure for the resulting fragment.
• These can also be used to realize Content Services using the JSON Exporter.

Stored as Assets:

• Content fragments (and their variations) can be created and maintained from the Assets console.
• Authored and edited in the Content Fragment Editor.

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, and deliver, the required content fragment in either HTML or JSON format.

Are without layout or design (some text formatting is possible in Rich Text mode).

Contain one, or more, constituent parts.

Can contain, or be connected to, images.

Can use in-between content when referenced on a page.

Are independent from the delivery mechanism (i.e. page, channel).

Insert Asset into a fragment (mixed-media fragments)

• Are an integral part of the fragment (see Constituent Parts of a Content Fragment).
• Define the position of the asset.
• See Inserting Assets into your Fragment in the Fragment Editor for more information.

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.

Fragment Elements

• Elements correlate to the data fields holding content.

• For fragments with structured content, you use a content model to create the content fragment. The elements (fields) specified in the model define the structure of the fragment. These elements (fields) can be of a variety of data-types.

• For simple fragments:

  • The content is held in one (or more) multi-line text field(s), or element(s).
  • The elements are defined in the fragment template (cannot be defined when authoring the fragment, see Content Fragment Templates).

Fragment Paragraphs

• Blocks of text, that are:

  • separated by vertical spaces (carriage return)
  • in multi-line text elements; in either simple or structured fragments

• 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 (images) inserted into the actual fragment and used as the internal content of a fragment.
• 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.
• Can only be added to multi-line text elements (any fragment type).
• Are attached to the preceding text (paragraph).

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.

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 as 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.

Content Model

• Are enabled and then created using Tools.
• Required to create a structured fragment.
• Defines the structure of a fragment (title, content elements, tag definitions).
• Content models definitions require a title and one data element; everything else is optional. The model defines a minimal scope of the fragment and default content if applicable. Authors cannot change the defined structure when authoring fragment content.

Fragment Template

• Required to create a simple fragment.
• Usually developed during project implementation; cannot be created when authoring.
• Defines the basics properties of a simple fragment (title, number of text elements, tag definitions).
• Template definitions require a title and one text element; everything else is optional. The template defines a minimal scope of the fragment and default content if applicable. Authors can later extend a fragment beyond what is defined in the template.

Content Fragment Component

• Instrumental to delivering the fragment in HTML and/or JSON format.
• 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.