Skip to content

Web & Digital Experience

Content platforms: store the pieces, and pages become views

A long web page tangles together a service's name, the towns it covers, its warranty terms and its common questions. Change the warranty and someone edits page after page, missing one. A content platform stores each of those as a typed piece, written once. Pages are built from the pieces, so a fact changed in one place changes everywhere it appears.
Discuss your contentSee the content types ↓
one long pagetyped pieceswhere they showserviceFurnace repairareasNorthside · Eastside · Riversidewarrantysharedlabour guaranteed 1 yearFAQ3 questionsservice pageserviceareaswarrantyFAQEastside area pageserviceareaswarrantyFAQ pageFAQbooking formserviceareas

Five types of content, each written once

For a home-services site. Your types will differ; the principle won't.
Servicename, areas, warranty, FAQs, photosservice pages, area pages, the booking form
Service areatown, services offered, travel notesarea pages, the “do you serve” check
Job storyservice, town, photos, what was doneservice pages, area pages, reviews and work
FAQquestion, answer, which services it's aboutservice pages, the FAQ page, search
Shared blockwarranty terms, licence detailseverywhere it's used, changed once

One change, from draft to published

The labour guarantee goes from one year to two. One edit, and every page that shows it.

Step 1 of 5: Edited

Edited

Who
office manager
What happens
The labour guarantee changes from one year to two, in the shared warranty block.

What a content platform is made of

  1. 01

    The content model

    Types and fields before pages

    Services, areas, job stories, FAQs: each a type with fields, so content can be reused and checked.

  2. 02

    Taxonomy

    How content is grouped and linked

    Services and towns tag every piece, so area pages and related links build themselves.

  3. 03

    Editorial workflow

    Draft, review, scheduled, published

    Who can publish what is set per type; some changes wait for a second person.

  4. 04

    Search

    Find it by what people type

    Visitors search by problem (“no hot water”), so FAQs and job stories are searched too.

  5. 05

    Page families

    Templates fed by the model

    Every area page comes from one template, filled with that town's own content, never thin copies.

What a content platform hands off

In

Editors
drafts and changes
The model
types, fields, tags
Rules
who publishes what
Content platform
store once, show everywhere

Out

Pages
built from the pieces
Search
across every type
History
every version kept

Worth building when the same facts appear on many pages

Good fit

  • You publish more than a few dozen pages, and they share facts.
  • A change today means editing page after page.
  • Several people write, and someone should approve.

Not the right fit

  • A small site with a handful of pages. A site builder will do.
  • Nobody will keep the content up to date.

Where this capability is used

Next to content platforms

Questions about content platforms

Do we need a headless CMS?

Sometimes. What matters is the model: typed content that can be reused. That can live in a hosted CMS or in the site's own content files, depending on who edits and how often.

Can our team still edit pages visually?

Yes, with a preview of every page a change touches. The structure underneath stays, so pages stay consistent.

What happens to our existing content?

It's inventoried and moved into the model: each page split into its pieces, duplicates merged, gaps listed. Old addresses redirect to the new ones.

Can AI write the content?

It can draft, and every draft is reviewed before it's published. Facts like warranty terms come from the model, not from the draft.