Modelling content
The model decides what a document can be. It is the contract between the people writing content and the people writing components.
Modelling needs the admin role, because changing a block's fields changes every document using it.
Two things to model
Content types are kinds of document: a page, an article, a legal notice, a partial, a redirect. A content type decides how a document is addressed and which sections it may contain.
Block types are the sections themselves: a hero, a feature grid, a call to action. A block type declares the fields an editor fills in.
The division of labour
| The CMS owns | Your site owns |
|---|---|
| That a hero has an eyebrow, a title, a subtitle, an image | What a hero looks like |
| Which fields are required | How it behaves on a phone |
| Which sections an article may hold | Its animation, spacing, colour |
This is why a marketer can rewrite a page without a developer, and a developer can restyle it without asking a marketer.
It also means a block type is only half a block. The other half is a component in the site's repository, and content using a block type the site has no component for cannot be published.
Guides
- Content types — kinds of document, and how they are addressed
- Block types — sections, fields, and adding a new one
- Field types — the full list and what each gives an editor