Website Design and Development
CMS and content architecture
Build a content model that lets the people who write actually publish. It is a defined piece of work rather than a retainer line item.
What is a CMS and content architecture?
Build a content model that lets the people who write actually publish. In practice that means content modelling by the shape of the content rather than by the page layout, and then the harder half: editorial workflow that matches how the team really works.
Why this work exists
It is cheap to do early and expensive to retrofit, which is the opposite of how it usually gets scheduled.
Website Design and Development holds the whole discipline. This page is one defined piece of it.
The nearest piece of work to it is keeping third-party scripts from degrading a site that was fast on launch day. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
Success looks like fewer meetings about this, not more reporting on it.
The gap between that and where most accounts start is why this is scoped as CMS and content architecture rather than as a line inside something larger. Specifying the redirect map before the build starts is the usual second step once it is in place.
When this is the right work
The signs that this is where the problem sits:
- Editors ask a developer for every content change
- Every page is a freeform block editor and no two look alike
- The content model forces square content into round templates
If none of those is true, something else is probably the constraint, and the Website Design and Development overview maps the alternatives. The usual neighbours are enforcing the performance budget in the pipeline and testing with a keyboard and a screen reader, not just a checker.
What the work covers
Concretely, this covers:
- Content modelling by the shape of the content rather than by the page layout. Skipped more often than any other part of this, and regretted more often too.
- Editorial workflow that matches how the team really works. Where the documentation and the actual behaviour part company.
- Template and component library with sensible constraints, which clients tend to want evidence for, so it is documented as it goes.
- Governance so the structure does not degrade over two years of use. Worth doing badly rather than not at all, if time is short.
How it runs
The running order, which matters more here than it does elsewhere.
Proving it in one place first
Changes get made to a small, representative slice and measured there before being applied everywhere. It is slower for three weeks and faster for the rest of the year.
Clearing the contradictions
Where two systems disagree about the same fact, that gets settled before anything is built on top of either of them.
Setting the review rhythm
How often this gets looked at again, and by whom, is agreed now rather than left to whoever notices first.
What each part runs into
Each piece has its own friction:
- Content modelling by the shape of the content rather than by the page layout, which in Chandigarh runs into a seasonal peak that arrives before the content is indexed
- Editorial workflow that matches how the team really works: the Manchester version of this has to deal with a reporting line that averages away the market in question
- Template and component library with sensible constraints, where a Chicago engagement contends with a market where buyers qualify by area rather than by city
- Governance so the structure does not degrade over two years of use – working in Vancouver this means accounting for a competitive set that changes street by street
What not to do
Modelling content around the current design. The design will change and the content model will outlive it, so model the content’s actual structure.
The reason it matters is that the failure is invisible from the report: the activity happened, the number did not move, and the conclusion drawn is usually the wrong one.
How it is measured
Editor publishing autonomy, and template consistency over time. It is reported with the existing metrics rather than replacing them, because a new number nobody recognises persuades nobody.
Reported with its own caveats attached, rather than cleaned up for the deck.
What you end up with
You are left with a content model and template library editors can work in, with workflow and governance documented.
Kept short enough that it gets read, which is the only property that matters.
How it differs by sector
Read across three sectors, the differences are clear:
- Automotive: the thing that changes the scope here is that Local inventory, model-level demand, and a buyer who arrives having already decided.
- For Healthcare and clinics, content that affects health decisions is held to a higher standard, and advertising is restricted. and that shapes how far this can go.
- Manufacturing and industrial brings its own limit: low volume, high value, and a specification sheet that decides the deal.
The industry pages carry the rest of that detail. Automotive and Healthcare and clinics are the two where this piece of work most often decides the outcome.
The rest of Website Design and Development
Common questions
How structured should a content model be?
Structured enough that content can be reused, validated and rendered differently in future, and loose enough that editors can do their job without filing tickets. The failure modes are symmetrical: a freeform editor produces inconsistency nobody can maintain, and an over-modelled one produces workarounds.
Should a site use a headless CMS?
Where content genuinely feeds several destinations, or the front end needs a framework the traditional CMS fights, it earns its complexity. For a single website with an editorial team, a conventional CMS is usually faster to build, cheaper to run and easier for editors, and the headless choice is often made for the developers’ benefit rather than the business’s.
Will we speak to the person doing the work?
Yes. The person who diagnoses CMS and content architecture is the person who does it and the person on the review call. Handing a finding to somebody else to execute is where most of the value leaks. If the brief is still open, Noindex or Robots.txt disallow and Performance Max or Standard Search are the two that change it most often.
What happens if we stop after this?
You keep everything: A content model and template library editors can work in, with workflow and governance documented. Documented so your own team can continue it, including the parts we would have done next and why. What does a technical SEO audit actually check? is the reference page for this. What is a good conversion rate? is the one with the examples.
What if we disagree with the diagnosis?
Then we look at the data together. Editor publishing autonomy, and template consistency over time is the test, and a finding that cannot survive being questioned is not a finding worth acting on. When this comes up in a pitch, Shopping ads and Site architecture are the pages that settle it.
Ask about cms and content architecture
Describe what is not working in a sentence. We will tell you whether this is the right piece of work or whether something else is binding.
Find out what is actually holding this back
We would rather tell you the work is not worth the money than take it and report on activity.