Model your content, not your pages

3 min

The BetterCMS team Product

Summarize with AI

TL;DR, key takeaways

  • A content model describes the things your organisation has, not the pages it shows them on.
  • Field names should describe meaning, never position on screen.
  • Keep the model small: every field is a question someone has to answer before publishing.
  • Pages are ordered lists of typed sections, kept apart from the model they draw on.

Most content models start as a mirror of the site map. There is a page type for the homepage, a page type for the pricing page, and a long tail of one-off types for the pages nobody could classify. It works until the marketing team wants the pricing table on a second page, and then it does not work at all.

The alternative is to model the things your organisation actually has. A pricing plan is a thing. A customer story is a thing. A person on the team is a thing. Pages are arrangements of those things, and arrangements change more often than the things do.

What is a content model?

A content model is the set of types, fields and relationships that describe the content a site holds. It says that a case study has a customer, a summary, a set of quotes and a link to the product features it mentions. It does not say where any of that appears on screen.

The distinction matters because the model outlives the design. A site is redesigned every two or three years. The content is meant to survive that, and it only survives if it was never described in terms of the design it is leaving.

How do you tell a page model from a content model?

Read your field names out loud. If a field is called "hero subtitle" or "right column text" you have modelled a page. If it is called "summary" or "eligibility" you have modelled content.

  • Field names describe meaning, not position. "Summary", not "intro paragraph two".
  • A field that only exists because the layout needs something there is a layout concern, not a content field.
  • If two types have the same six fields under different names, they are one type with a variant.
  • A field nobody has filled in on any entry is a field nobody needed.

Start with the nouns

Write down every noun your team says in a planning meeting. Plan. Case study. Integration. Job. Release note. Those nouns are your first draft of the model, and they are usually more accurate than anything derived from the current site, because they describe the business rather than the last redesign.

Then ask which nouns are referenced by other nouns. A case study mentions a customer. A job mentions a team. Those references are the most valuable part of the model, because they are what lets one edit update every place a fact appears.

Keep the model smaller than you think

Every field is a question somebody has to answer before they can publish. A type with thirty fields is a form nobody fills in properly, and half-filled entries are worse than absent ones because the gaps are invisible until the page renders.

A good rule is that a required field must be one a writer can answer without asking anyone. Everything else is optional, and the template renders correctly when it is missing.

Where page composition belongs

Pages still need to be assembled, and pretending otherwise pushes the assembly into a developer ticket. The answer is not to model pages as fields. It is to model pages as ordered lists of sections, where each section is a small typed block with its own fields.

That keeps the two concerns apart. The section catalogue is a design system decision. The order of sections on a page is a marketing decision. Neither one needs the other to change.

A content model is a promise about what will still be true after the redesign.

What to do this week

  1. List your content types and count how many exist because of a layout.
  2. Rename every field whose name describes a position on screen.
  3. Find the facts that are typed into more than one place and make one of them a reference.
  4. Delete the fields with no values behind them.

None of this needs a migration to start. Renaming fields and deleting dead ones is an afternoon, and it makes the real migration a smaller decision when it comes.

More articles

View all

Your next website starts here

See BetterCMS running on your pages, not on a sample site.