Contentful.

Where Contentful fits on a long engagement.

Content modelling is the decision that determines whether a headless CMS helps or hinders. Types modelled around meaning — a product, an article, an author — serve every channel; types modelled around one page layout recreate the coupling headless was adopted to remove, with more steps.

The editor experience is the trade-off to manage. Editors lose the visual context of a page and work with structured fields instead, which is precise and less intuitive. Preview environments are what close that gap and they are frequently treated as optional.

What an assigned team does with Contentful.

Editorial adoption decides whether the investment returns anything. A CMS editors find difficult produces workarounds — content pasted into the wrong fields, layout forced through rich text — that undo the structure.

Designing for editors rather than only for developers is why content projects are scoped with outsource ux design capacity alongside engineering.

What we use Contentful for.

• One content set across channels Web, mobile and partner surfaces served from the same structured content.
• Types modelled on meaning Content structured by what it is rather than where it appears.
• Preview that gives editors context Seeing the result before publishing, which is what makes structure tolerable.

How Contentful capacity is assigned.

Headless content work is assigned across engineering and design, with the editing experience treated as a deliverable rather than a by-product.