Why Content Modeling Should Happen Before Template Redesign

Many redesigns start in the wrong place.

They start with components, page mocks, and template discussions before the team has agreed on what the content actually is. That usually feels productive at first, because screens are easy to react to. The problem shows up later, when the new design needs to support content that was never modeled clearly in the first place.

That is why content modeling should happen before template redesign.

A Template Can Only Express The Structure It Is Given

A template is presentation.

It can make content look better, but it cannot fix content that is still stored as one large, page-shaped blob. Contentful’s current headless CMS explanation still makes this point clearly: separating presentation from content management is useful, but the real unlock comes from structured content and a defined content model.

That matters because redesign work often assumes the new frontend will somehow make reuse easier on its own. It will not.

If the content is still mixed together as one body field with hidden assumptions, the redesign simply gives the same structural problem a nicer visual layer.

Content Modeling Defines What Can Be Reused

The important question is not only “what should the page look like?”

It is also:

1. what fields repeat across page types,
2. what content should be reusable,
3. what belongs in metadata instead of body copy,
4. what should be localized independently,
5. what should be edited once and reused everywhere.

Contentful’s structured-content guidance frames this well: break content into predictable building blocks so the same material can be reassembled for different pages, campaigns, or channels.

That is a modeling decision before it becomes a design decision.

The Redesign Usually Exposes Missing Structure

This is why redesign projects feel harder than they should.

Once the new templates are designed, the team suddenly discovers that service pages, case studies, FAQs, comparison pages, and landing pages do not actually share a consistent shape. Editors have been solving that inconsistency manually inside a WYSIWYG or an improvised CMS workflow.

Then the redesign inherits the cleanup work.

Instead of building a better frontend, the project turns into a rescue job for years of uneven content entry.

Modeling First Creates Better Editorial Rules

A good content model is not only a developer artifact.

It gives editors better rules too.

For example, a team can decide that every service page needs:

1. a plain-language summary,
2. a problem statement,
3. an outcomes section,
4. a scope section,
5. a next-step CTA.

Once those fields are explicit, the redesign has something stable to work with. The frontend can present the same structure well, and the editorial team knows what a complete page actually looks like.

Without that, the template keeps compensating for inconsistent content instead of expressing a clear system.

Headless Does Not Remove The Need To Model

Teams sometimes assume a headless CMS solves this automatically.

It does not.

Contentful’s current material is useful here because it says this directly: a headless CMS separates the presentation layer from the backend, but it does not give your content structure on its own. That structure still has to be designed.

That is the difference between “moving to headless” and building a content system.

Template Work Gets Faster After The Model Is Clear

Once the content model exists, template decisions become more precise.

The team can answer practical questions faster:

1. which fields need dedicated components,
2. which sections are optional,
3. which modules can be shared across page types,
4. which fields need localization support,
5. which content belongs in structured data, metadata, or internal search.

That is a better redesign workflow because the frontend is responding to a defined structure instead of guessing one.

A Practical Rule

If the redesign includes repeated arguments about what a page “usually contains,” the content model is probably not finished yet.

That disagreement should be resolved in the model before it gets disguised as a design problem.

Bottom Line

Content modeling should happen before template redesign because structure decides what the design can reliably express, reuse, and scale.

Once the model is clear, the redesign gets easier, the editorial rules get better, and the frontend stops carrying the burden of unclear content architecture.

References: Contentful on Headless CMS and structured content and W3C Internationalization.