
Web
A content platform is what lets a marketing team publish without a developer. The right choice depends on how much content there is, how often it changes, and who edits it, not on which platform is fashionable.
Context
The platform decides who can publish. If every content change needs a developer, the site stops being updated, and a stale site is a visibility problem before it is a design one.
Choices
Every choice below has a reason attached. A stack without reasons is a logo wall.
The questions we work through before recommending anything in this area.
Recommending something everywhere is the same as having no opinion.
Architecture
Page structure as a machine reads it
An extractable page states its answer first, uses one heading level per section, and anchors its structured data to a single organisation entity. A page that buries the answer beneath a hero cannot be extracted at all.
Where we apply it
No, and it runs a large share of the web perfectly well. It becomes a problem when a purchased theme brings hundreds of kilobytes of code you did not choose and cannot easily remove, which is where most performance and structure problems on WordPress sites originate.
A content platform is what lets a marketing team publish without a developer. The right choice depends on how much content there is, how often it changes, and who edits it, not on which platform is fashionable.
The platform decides who can publish. If every content change needs a developer, the site stops being updated, and a stale site is a visibility problem before it is a design one.
A five-page site that changes twice a year: a CMS is overhead nobody will use; Teams with no capacity to publish; a platform does not create a content operation; and Migrating platform to solve a problem that is actually content strategy
How many pages, changing how often?; Who edits, and what is their technical comfort?; and Does the content have relationships, or is every page standalone?
Content stored as entities with relationships rather than as pages, so one fact updates everywhere it appears instead of being copy-pasted.
Editors get a familiar interface; crawlers get complete HTML. This combination is what makes a large content site both maintainable and discoverable.
Editors should see exactly what will publish before it publishes, without involving a developer.
Connected
Bring the existing system and the constraints around it. We will tell you where this fits, where it would be the wrong tool, and what we would leave exactly as it is.