Introduction to Content Modelling

Correctly modelling the structure of your content is one of the most important aspects of successfully integrating with a headless CMS. If you’re not sure what a content model is, please see the core concepts section.

Defining a Content Model

Each space has its own content model which can be found in the space’s “Content Model” section.

The default and recommended way to manage your space’s content model is using the visual editor, though users who wish to do so can edit the model manually using the YAML editor.

To enter the YAML editor, navigate to the “Content Model” section of your space, and click on the “Switch to YAML Editor” button.

Content Types

Most content models will consist mainly of content type definitions. As explained in the core concepts section, content types are the main building blocks for your content.

The table below shows what a content type configuration looks like:

Content Fields

Content fields are the pieces that define the data which can be stored in a particular content type. Each content field can be any one of the supported field types.

The table below shows what a content field configuration looks like:

Content Field / L10n

The table below shows what the configuration of a content fields l10n attribute looks like:

Content Field / Config

The table below shows what the configuration of a content fields config attribute looks like. In addition to the below options, you can also provide further options which are specific to the particular type of field that is being defined.

Details of these additional options can be found on the supported field types page.

Locales

As described in the core concepts section, locales allow you to define the languages that your content can be translated into.

When defining a locale you can also specify a fallback. This allows you to define an alternative locale which should be used in the event that a piece of content is not available in this locale. For example, you could specify that the French locale should fallback to using the English locales content in the event that no French translation has been provided for a piece of content.

The table below shows what a locale configuration looks like:

Example Content Model

Below is an example of a simple content model which defines a single locale and a single content type.

l10n:
  defaultLocale: en-GB
  locales:
    - { code: en-GB, name: English }

contentTypes:
  - id: article
    name: Article
    fields:
      - id: title
        name: Title
        config: { type: text }
      - id: body
        name: Body
        config: { type: textLong }