CMS

What it is

Three jobs, usually sold as one product:

Editing — the screens where a person writes the text, uploads the picture and presses publish. Storing — the database that holds it, with its own idea of what a page, a post and a product are. Displaying — the templates that turn stored content into the page a visitor sees.

WordPress does all three, which is why it is the default answer. A headless CMS does the first two. A static site generator reading Markdown files in a repository does the third from content that has no CMS at all.

Why it matters if you are paying for a website

Because the question “do I need a CMS” is really “which of those three do I need, and who is going to use them”. Two failure modes, and I meet both regularly.

A CMS nobody uses. A five-page company site with a full editor bolted on, because it was on the checklist. The content changes twice a year, the editing screens are logged into once, and what the site actually got was a database, an admin login on a public URL and a monthly update obligation — the entire attack surface of a CMS in exchange for nothing.

No CMS where one was needed. The opposite, and more expensive: a site whose prices, team or offer change monthly, built as files only a developer can edit. Every correction becomes a small invoice and a wait.

The honest test is not the page count. It is: who changes what, how often, and can they do it without me.

What I build when the answer is “something else”

Sometimes the content model is the problem rather than the editor. I have built a custom admin for a catalogue whose structure had outgrown what posts and custom fields could express without a diagram, and I have left WordPress in place as the editor while replacing everything in front of it — the same content, the same login, a different site.

Neither is a better answer in general. The first costs more to build and fits exactly; the second costs less and inherits both the habits and the update obligations of what it kept.

What a CMS is not

It is not a website — it produces one, or feeds one. It is not a guarantee that a non-technical person can edit safely, either: an editor over a template that assumes a particular shape of content will let someone break the page with a heading in the wrong place, and no amount of CMS fixes a layout that only works with the words it was designed around.