Skip to content

Content modelling / a shared foundation

Keep the intent.
Carry the model.

A portable format for content models
and the intent behind them.

Agree what your content needs to do. Describe its structure and relationships in CMMF. Carry those decisions into your CMS implementation.

Content Model Master Format

Structure. Relationships. Editorial intent.

01
Agree the intent

Start with the people and the content.

02
Describe the model

Make structure and relationships explicit.

03
Translate deliberately

Record decisions for your chosen CMS.

A model you can reason about

One story. Two different relationships.

A customer can appear in many stories. A quotation belongs in the context of one story. A useful model makes that distinction visible before a CMS makes it for you.

EntryCustomer Storytitle *stringstory *richTextcustomer *referencequote object
A customer can be reused across stories. Quote values belong inside one story. Selected fields shown. * Required field
customer-story.yaml · relationship excerptCMMF 1.2.0
  - id: customer
    name: Customer
    type: reference
    required: true
    list: false
    targets: [customer]
    relation:
      ownership: linked
    editorial:
      helpText: Choose the reusable customer profile behind this story.

  - id: quote
    name: Quote
    type: object
    objectType: quote
    editorial:
      helpText: Include an approved quote in its original context. Omit the quote when none is available.

This excerpt comes from the complete Customer Story tutorial model.

Explore the files and decisions

From shared intent to a working system

The model carries the meaning.
Translation records the choices.

A reference may become a CMS relationship field. An embedded object may become a nested group. CMMF describes the intended structure; your implementation records what the platform can represent and where compromises enter.

Understand translation

Choose your next step

A format, with tools around it.