Almost every website proposal contains a version of this promise, and it is usually true on the day of handover and false within a year.
The reason is that people treat editability as a feature of the content management system, when it is mostly a consequence of how the site was built on top of it. Two sites can run on the same platform, and one is comfortably maintained by a marketing coordinator for five years while the other is untouched after month three because nobody dares. The platform is not what separates them.
The thing that actually decides it
Sites are built one of two ways, and this choice matters more than the platform.
Structured content. The site knows what a case study is: it has a title, a client type, a challenge, an outcome, an image and three tags. Someone adding one fills in fields. They cannot break the layout because they never touch it, and every case study looks right because the design was made once and applies to all of them.
Free-form layout. The site is built with a page builder, where each page is assembled from rows and columns and blocks. Someone adding a case study builds it, by copying an existing page and changing things.
The first is more work to build and dramatically cheaper to live with. The second is quicker to launch and degrades. Within a year of free-form editing you have four slightly different case study layouts, three heading sizes, spacing that varies by page, and a set of pages nobody wants to touch because it is unclear what will move.
There is an honest counterpoint. Structured content constrains: if your marketing team genuinely needs to build campaign pages with varying layouts, an entirely structured site frustrates them and they will start asking for exceptions. The workable answer is usually both, applied deliberately. Structure everything that repeats, which is most of the site, and allow free layout on a small number of page types where variety has a purpose.
The question to ask any supplier is not "does it have a CMS". It is: which parts of this site will be structured, and which will be free-form? The answer tells you what maintaining it will feel like.
The four kinds of system
| What it is | Suits | Watch for | |
|---|---|---|---|
| Traditional CMS | Content and presentation in one system, pages assembled by the platform. The most widely used category | Most business sites, content-heavy sites, teams who want one place to log in | Plugin accumulation, which degrades speed and security. Page builders, which undo structure |
| Headless CMS | Content stored separately with no opinion about presentation; the site pulls it in | Content shared across a site and an application, multiple languages or channels, teams with development support | Editors cannot see how a change will look without a preview being built, which is real work and often skipped |
| Hosted site builder | Platform, hosting, editor and templates as one subscription | Small sites where speed to launch matters more than control, teams with no technical support at all | Limits are hard limits. Export is often partial. Costs rise with features you did not choose |
| Static site with files | Pages generated in advance from files, often edited through a lightweight interface | Fast, security-conscious, low-maintenance sites; documentation; brochure sites that change rarely | Non-technical editing needs an interface layer added deliberately, or the promise is not real |
Two observations from the table.
The distinction between traditional and headless is often oversold. For a business site of moderate size, either can be excellent, and the decision usually comes down to whether the content also feeds something else. If it does not, the added moving parts of a headless setup buy little.
A hosted builder is a legitimate answer, not a compromise. If a business needs eight pages and has nobody technical, the correct advice is often a subscription and a good template, and any developer who never recommends this is not weighing the options honestly.
The questions that decide it
Who edits, and how often? One person changing a price twice a year needs almost nothing. A team publishing weekly needs a proper editorial workflow with drafts, review and scheduling. Building the second for the first is waste; the reverse is a bottleneck.
How technical are they? Not as a judgement, as a design constraint. Anything requiring familiarity with formatting syntax, image dimensions or code fragments will be used by exactly one person, and the site becomes unmaintainable the day they leave.
Does the content go anywhere else? A price list on the site and in an application, a product catalogue feeding both a site and a portal. If content has two destinations, that pushes towards a system that treats content as data rather than as pages.
More than one language? This is the question that most often overturns a choice made on other grounds. Translation handling differs enormously across systems, and retrofitting a second language into a site not planned for it is expensive. If Arabic or another right-to-left language is possible, that affects design as well as content and should be raised at the start.
Who patches it? Every system needs updates. On a self-hosted platform that is somebody's job, and an unpatched site is a security exposure that will eventually be found by an automated scan. On a hosted platform it is the vendor's job and part of what you pay for. Deciding this before launch is how you avoid the site nobody has updated in two years.
What happens if you leave? Ask specifically what a complete export contains and in what format. Content in an open format is portable. Content locked inside a proprietary page-builder structure is technically exportable and practically useless to the next site, which turns a redesign into a retyping exercise.
Training and governance, which is where sites are actually lost
Two hours of training at handover, delivered to whoever was free that afternoon, is the standard arrangement and it does not work. Three things do.
A short written guide, made from your site, not the platform's manual. Six pages: how to add each content type you actually use, image sizes, and what not to touch. Made during the build, when it costs an hour.
Two people trained, not one. Sites are routinely orphaned because the trained person changed roles.
A named owner. Somebody whose job includes the site, even at an hour a month. Without one, the site is nobody's responsibility and drifts. This is not a technical requirement and it predicts outcomes better than any technical one.
Worth adding for teams of more than about five: agree who can publish without review. The most common cause of an embarrassing page is not a technical failure but everyone having full rights and no convention about their use.
An illustrative example
A professional services firm with 40 staff wants a site their marketing coordinator can run. They are shown two proposals. One is built on a familiar platform with a page builder, and the demonstration is impressive: the coordinator drags a testimonial block onto a page and it appears instantly. The other proposal has content types for services, people, case studies and articles, and no drag-and-drop at all.
The first demonstration wins the room, because it looks like freedom. Two years on, the site has 60 pages built by three different people, four visual treatments for the same kind of content, and a coordinator who avoids older pages because their layouts are unpredictable. The second would have felt more restrictive in the demonstration and would still look consistent, because adding a case study never involved touching a layout.
That is not an argument that page builders are always wrong. It is an argument that a demonstration measures the first hour of use and you are buying the third year. Hypothetical, but the pattern is the most reliable one in this subject.
Common questions
Is a particular platform better than the others? For most business sites, several are perfectly good, and how the site is built on top matters more than which one. Be sceptical of both strong advocacy and strong dismissal; both usually reflect what the speaker is set up to deliver.
Can we add a CMS to our existing site? It depends entirely on how that site was built. Sometimes it is a contained piece of work. Often the site's pages are fixed files, and making them editable means rebuilding the parts you want to edit. Worth having assessed specifically before it is assumed either way.
How much should content management add to a project? It is not a line item so much as a way of building, and structured content adds real time at the start. The comparison to make is against paying for edits over three years, plus the cost of a site that goes stale because editing is awkward. That comparison usually favours doing it properly, which is why it is worth asking for it explicitly rather than hoping it is included.
What about editing with AI assistance? Tools that draft or adjust content are improving quickly and change what a small team can maintain. Two cautions that hold regardless of the tool. Published pages still need a person accountable for accuracy, because a plausible sentence about your prices or your services can be wrong in a way that costs you. And the structural question in this article does not change: generated content still has to go somewhere, and a site that degrades when edited will degrade faster when edited more.
The short version
- Editability is not a platform feature. It is a consequence of whether content is structured or free-form.
- Structure everything that repeats. Allow free layout only on the few page types where variety earns its cost.
- Ask a supplier which parts will be structured and which free-form. That answer describes what maintaining the site will feel like.
- Four categories: traditional, headless, hosted builder, static with files. Several are usually acceptable; a hosted builder is a legitimate answer for a small site.
- Decide who patches it and what a full export contains, before launch rather than after.
- Train two people, write a short guide from your own site, and name an owner. Sites are lost to governance more often than to technology.
Where to take this next
If the reason you are reading this is that your current site cannot be edited without a developer, that is one of the four signals that points at structure rather than appearance: redesign or rebuild covers how to tell which you need.
If you are earlier than that and still working out what the site should achieve, start with what a business website should actually do.
If you want a straight answer about whether your existing site can be made editable, or whether that means rebuilding, it is usually possible to tell fairly quickly. Discuss your idea, or say hi on WhatsApp.
# Visual recommendations
Concepts only. Hairline drawing, ink and brass.
Hero visual — structured against free-form, after two years
Concept. Two columns of six page thumbnails each, drawn as hairline wireframes. The left column, structured, shows six pages with identical proportions and alignment. The right column, free-form, shows six pages that begin identically at the top and diverge as they descend: heading sizes vary, spacing drifts, one page has an extra column. A quiet time axis runs down the side.
Purpose. Shows the article's argument as a consequence over time, which is the part a demonstration cannot show.
Composition. Vertical, two columns, no colour except a brass marker on the first row where both still match.
Alt text. Six structured pages stay consistent over time while six free-form pages drift apart in heading size, spacing and layout.
Supporting visual — where the four systems sit
Concept. A two-axis diagram. Horizontal: editor independence, from needs a developer to fully self-service. Vertical: presentation control, from fixed to fully free. The four system types placed as labelled regions rather than points, since each covers a range. A brass region marks the area most business sites should aim for, in the upper middle: self-service editing with controlled presentation.
Purpose. Replaces a comparison table's row-by-row reading with one glance at the trade-off being made.
Placement. Above or beside the four-kinds table.
Alt text. Four content management approaches placed against editor independence and presentation control, with the recommended area being self-service editing combined with controlled presentation.