Content modelling
Types, fields, relationships and validation designed around your editorial reality, not around a page builder.
Service 05 — CMS
Ease of
management,
without compromise.
We customise your CMS to suit you — Drupal, WordPress or fully headless. Editors get an interface that matches how they actually publish, and developers get a codebase that does not fight the platform.
What is included
- Content modelling
- An editor interface people like
- Roles and workflow
- Migration with URLs intact
- Performance and caching
- A safe upgrade path
Content management is an interface problem
Almost every CMS complaint we hear is really the same complaint: the editing interface does not match the way the team thinks about their content. Somebody built pages out of a pile of generic blocks, and now every update is an act of archaeology.
We model your content first — what a "case study" or a "product" or an "event" actually is, which fields are required, what varies and what never should. Then the editing interface follows from the model, and publishing stops being a design exercise for people who are not designers.
Traditional, headless, or somewhere in between
Traditional CMS keeps everything in one place and is the right answer more often than the industry admits. Headless separates content from presentation, which pays off when the same content feeds a site, an app and a partner feed. We will tell you which one your situation warrants and what it costs to change your mind later.
Deliverables
What you
actually get.
An editor interface people like
Previews, sensible defaults, guard rails and help text where the mistakes actually happen.
Roles and workflow
Draft, review, schedule and publish, with permissions that match who is actually accountable.
Migration with URLs intact
Existing content moved with redirects mapped, so a relaunch does not cost you your search rankings.
Performance and caching
Page caching, image pipelines and query discipline, so a content-heavy site stays fast.
A safe upgrade path
Dependencies pinned, updates rehearsed on staging, and a documented routine your team can run.
Shapes of the work
Where this
usually lands.
| Approach | Best when | Watch out for |
|---|---|---|
| WordPress | Marketing sites, blogs, a team that already knows it | Plugin sprawl — we keep the list short and audited |
| Drupal | Complex content models, strict permissions, multilingual | Higher build cost; worth it at real complexity |
| Headless | Content feeding a site, an app and partners at once | Editors lose easy preview unless you build it back |
| Static + Git CMS | Small teams, maximum speed and security | Editorial workflow needs deliberate design |
Stack
What we build
this with.
We work in your stack when you have one. These are our defaults when the choice is ours.
WordPressDrupalStrapiSanityPHPTwigReactGraphQLMySQLRedis
Questions
Before you
commit.
Can you fix our existing WordPress site?
Usually yes, and usually faster than rebuilding. We audit plugins, performance and security first, then give you a repair-or-replace recommendation with the reasoning attached.
Is WordPress secure enough?
Core is fine when it is kept updated. Almost every WordPress breach we have investigated came through an abandoned plugin. We audit the plugin list, remove what is not earning its place, and put updates on a rehearsed schedule.
Will editors need training?
An hour, usually, plus a short written guide we record during handover. If it needs more than that, we designed the interface badly.
Can we keep our current design?
Yes. Re-platforming without redesigning is a legitimate project and often the cheaper half of the work.
Related
Usually paired
with these.
020409
Web applications
Static, dynamic, animated, portal or progressive — we create web application solutions that fit your needs, standards…
E-commerce
Get a high-profit e-commerce website that brings in revenue like clockwork. B2B and B2C, on the platform that fits…
Hosting & cloud
VPS hosting, dedicated web hosting and cloud infrastructure — provisioned, hardened and monitored by the same team…
Ignition
Need cms?
Tell us the problem, the users and the systems already in place. We will identify the right discovery or build step.