1. Home
  2. Blog
  3. What a CMS actually gives you

CMS

What a CMS actually gives you

A CMS is not a website. It is the login where you change the words without calling anyone. Knowing which parts it controls, and which it does not, saves you a fight later.

Most people meet the phrase "content management system" while being sold one, which is a bad place to learn what it does. So here is the plain version, written for the person who signs the invoice rather than the person who installs it.

What is a CMS, in one paragraph?

A CMS is a login where you change the words and pictures on your website without opening code and without emailing a developer. Your site's text lives in a database or a set of content files. The CMS is the screen that lets you edit them, and the website reads whatever is in there when it builds the page.

The short version

A CMS is the editing login for your website, not the website itself. It controls the words, the images and which pages exist. It does not control how the site is designed or how fast it loads. Those are decided in the build.

What does a CMS actually give you?

Five things. Anything else you are offered on top is a feature of one specific product, not of the category.

  1. Edit access. You change a headline at 22:00 on a Sunday and it is live in under a minute. No ticket, no developer, no invoice.
  2. Structured content. Your text is stored as fields with names: title, price, opening hours, not as one blob of formatting. That is what lets the same opening hours appear on 3 pages and be correct on all of them after one edit.
  3. Drafts and scheduling. You write the piece today, look at it tomorrow, publish it on Thursday morning.
  4. Roles. Your assistant can edit the blog but cannot delete the pricing page. On a team of 4 people this matters within about a month.
  5. A history. Every change is recorded, and you can put yesterday's version back. This is the feature nobody asks for and everybody eventually needs.

What does a CMS not give you?

A CMS does not give you a new design. It fills in the design you already have. If your page was built with a headline, an image and 3 bullet points, the CMS lets you change that headline, that image and those 3 bullets. It does not let you decide the section should now be a video carousel. That is a build change, and it is a different conversation with a different price.

A CMS also does not make your site fast, secure or found on Google. Those come from the code underneath and from how the pages are written. Plenty of slow sites have excellent CMS logins.

The CMS controls the content. The build controls the container. Confusing the two is how people end up paying for a rebuild when they wanted a new sentence.

Headless or traditional: which one do you need?

A traditional CMS such as WordPress stores your content and renders your pages, both in one system. A headless CMS such as Sanity, Storyblok or Contentful stores your content and hands it to a separate front end that renders the pages. The editing screen looks similar. What differs is what the visitor downloads.

TraditionalHeadless
Renders the pageThe CMS doesYour site's own code does
Visitor downloadsTheme, plugins, CMS runtimeThe finished page
Plugins to maintainUsually 15 to 25None
Moving away laterRebuild, content is in theme formatContent is already in a clean data format
Best forSites edited daily by many peopleSites that need to be fast and stay maintained

We ship headless. The site is hand-written code, so the browser gets a finished page, and the CMS sits behind it for editing. You get the Wix-style editing experience without the Wix-style payload.

How much of the site should be editable?

Less than you think, and the reason is honest rather than defensive. Every field you can edit is a field you can break. A site where all 40 elements are editable turns into a site nobody dares to touch.

The rule we use: make everything editable that changes more than once a year, and leave the rest fixed. In practice that is your headlines, body text, images, prices, opening hours, team members, blog posts and the questions on your FAQ page. It is not your navigation structure, your colour tokens or your section order.

What to ask for before your site is built

  1. Which exact fields on which pages can I edit myself? Ask for the list in writing.
  2. Show me the editing screen before launch, not after.
  3. Who owns the CMS account, and what happens to it if I stop working with you?
  4. What does the CMS cost per month, and at what number of users or documents does that change?
  5. Can I export everything I have written, and in what format?

Every site we ship answers those 5 questions on the handover day: you get the CMS login in your name, the content in a portable format, the repository, and 14 days of fixes while you get used to it.