What is a CMS and how to choose one: 6 steps

Writing down who will edit the site and how often, the four kinds of CMS, the upkeep and security load, export and domain ownership, choosing a kind, and the questions to put to whoever builds it.

· 11 min readSoftware

Short answer

A CMS is software that lets you add and update a site’s content from a panel without writing code. Before you look at product names, decide who will edit and how often and who will do the upkeep; the kinds are the all-in-one site builder, the self-hosted CMS, the headless CMS and the static site.

Picture this scene: the owner of a café wants to change the opening hours on a Friday evening. The person who built the site is on holiday, and the panel password sits in the builder’s inbox. For three days the site shows the old hours. The scene shows why “what is a CMS?” is not really a software question: what matters is who can update the site and whose job the updating is. A CMS, or content management system, is software that lets you add and change pages, articles and images from a panel without writing code (CMS in the glossary). Which content management system to choose is settled by working through the six steps below, not by reading a product list. We do not rank products here; we describe kinds, and product names appear only as examples.

We covered which pages a site needs in what a company website needs, and the buyer’s side of the build in how to commission a website. This guide is only about choosing the platform underneath.

Step 1: Write down who will edit the site and how often

Before comparing kinds, answer these questions on a sheet of paper:

  • Who on your team will edit the site: one person or several?
  • How many times a month: almost never, a few times, every week?
  • What will they edit: small texts such as a phone number, regular blog posts, or products?
  • Should everyone have the same rights, or should one person prepare and another publish?
  • How many languages will the site be published in?

The glossary definition points the same way: who updates the content, how often, and in which languages decide which system is right. A firm that changes a phone number once a month and a publisher that posts daily do not need the same thing.

Step 2: Learn the four kinds

Hundreds of products fall into a few kinds. The table below shows four kinds, what you take on in each, and one product as an example.

Kind Example What you take on Who usually edits
All-in-one site builder (hosting included) WordPress.com Working within the limits of the service you pick You or your team, in the panel
Self-hosted open-source CMS WordPress (wordpress.org) Hosting, updates, backups, security You or your team, in the panel
Headless CMS with a separate front end Strapi, Sanity, Contentful Two separate parts: the panel and the site The team enters content in the panel; a developer runs the front end
Static site Markdown files with Astro Managing the files and the publishing process Usually someone technical, from the files

In short:

All-in-one site builder. The panel, the hosting and the upkeep of the software usually sit inside one service. Starting is easy; in return you work within what the service allows. Our service page says the same from the other side: if the job is to put a ready-made template live in a few days, going ahead yourself with a site builder makes more sense.

Self-hosted open-source CMS. You install the software on a server; the panel, plugins and theme are yours, and so is the upkeep. WordPress is an example of this kind. It is flexible, but the update load you will see in step 3 is real.

Headless CMS. The panel where content is written is separated from the front end that shows it. The Astro documentation puts it this way: the CMS helps you write content but does not generate a site that displays it; you fetch the content as data and use it in your own project. The front end can be designed freely, but a development team builds and maintains both parts (headless CMS in the glossary). Our service page lists Shopify and headless stores under e-commerce.

Static site. The content lives in files and the site is built from them. The Astro documentation says it has built-in Markdown support and that you can work without a CMS (static site in the glossary). There is no panel; adding a post means touching a file. That suits sites whose content rarely changes and whose editor is technical. If a panel becomes necessary later, a static site can still be connected to a headless CMS.

Step 3: Decide who carries the upkeep and security load

Every kind needs upkeep; the difference is who does it. Here is what WordPress’s own developer documentation says, as an example for the self-hosted kind:

  • WordPress is updated regularly for new security issues, and you should always run the latest version; older versions are not maintained with security updates.
  • Once a flaw is fixed, the information needed to exploit it is almost certainly public, which is why the documentation calls old versions more open to attack.
  • On a shared server, if another site on the same server is compromised, yours can be at risk too; the documentation suggests asking your host what precautions it takes.
  • It recommends backing up your data regularly, databases included.

So with a self-hosted CMS there is no moment when you can say “the site is built, done.” With an all-in-one builder the provider carries most of this load, but read in its documentation what exactly it carries. With headless and static sites the admin panel and the site visitors see are separate parts; write down which of them gets updated and who does it. Our maintenance and performance service covers updates, security patches and Core Web Vitals monitoring, and we write its scope in a separate proposal.

Step 4: Write down what must stay with you

You are choosing the platform today, but in three years you may want to change it. Three things must stay in your hands.

Content export. Before you choose, read the export section of the provider’s documentation and see what comes out. The WordPress Export screen produces an XML file (WXR) containing posts, pages, custom post types, comments, custom fields, categories, tags and users. WordPress.com’s support page says its export file holds posts, pages, comments and links to images, and does not include the theme design, customisations or plugins. The lesson is plain: content travels, while design and functions mostly do not. To keep addresses intact during a move, see keeping SEO through a site rebuild.

The domain name. The domain should be registered in your name and the management account should be yours. ICANN’s transfer policy says registered name holders must be able to move their domain names between registrars. The authority to approve a transfer rests with the registered name holder and the administrative contact, so the registrant should be you. Details are in how to choose a domain name and hosting.

Code and accounts. Get in writing whose name the panel, hosting, code repository and third-party accounts are opened in. We say that if you do not continue with us after the support period, we hand over the domain name, source code and accounts, and technical documentation is part of the delivery.

Step 5: Choose the kind

Use your answers from step 1 to follow the flow below. The diagram does not choose a product; it only points to a kind.

Choosing a CMS type: first who edits and how often, then four types Who will edit the site and how often? Team edits, ready-made, low upkeep Team edits, someone owns upkeep Team edits, custom front end planned Rarely, a technical person edits All-in-one site builder Self-hosted CMS Headless CMS and front end Static site Choosing a CMS type: first who edits and how often, then four types Who will edit the site and how often? Team edits, ready-made setup will do, low upkeep All-in-one site builder Team edits, someone owns the upkeep Self-hosted CMS Team edits, custom front end planned Headless CMS and front end Rarely, a technical person edits Static site
Figure: First ask who will edit the site and how often; the answer points to one of the four kinds.

The all-in-one builder and the static site sit at the two ends: one asks for almost no technical work, the other leaves the work entirely to a technical person. The two in the middle come into play when a team edits in a panel; the difference is who takes on the upkeep and in what form, and how custom the front end will be. For a corporate site that needs several languages and a panel, the route we describe is a site built with Astro and Next.js and managed from your own panel.

Step 6: Ask whoever builds the site these questions

  • Which kind do you recommend and why that one? Why did you rule out the second option?
  • Who will do the updates and security patches, how often, and is that in this proposal?
  • What can I change in the panel, and what needs you?
  • Can I export the content? In what format, are images included, and can we try one?
  • Whose name will the domain, hosting, code and panel accounts be in?
  • Do you provide short training or a written guide for using the panel?
  • If you stop working on this tomorrow, can someone else take the site over? Which documents will be handed over for that?

Common mistakes

  • Choosing the product before the kind. Write down the need first, then choose the kind, and look at products last.
  • Ignoring the upkeep load. Whoever sets up a self-hosted CMS should put updating in the calendar as a task.
  • Leaving the panel password with one person. As in the café, when that person is away the site is stuck.
  • Registering the domain in the builder’s name. If you are not the registrant, it gets harder to use your right to transfer.
  • Never trying an export. Run a test export on day one; that is when you see what is missing from the file.

Common questions

Is a CMS the same as a site builder?

They are close but not the same. A CMS is software for managing content from a panel; a site builder is a kind of CMS that combines hosting, panel and template in one service. With other kinds you manage the software and the hosting separately.

Does a small firm’s site need a CMS?

Not necessarily. If the texts rarely change and the person changing them is technical, a static site can be enough. If several people will edit, or you will publish regularly, a kind with a panel does the job.

Can I switch to another CMS later?

Yes. Content can usually be exported, but design and plugins have to be rebuilt. Plan the addresses from the start so search results survive the move; we explain how in keeping SEO through a site rebuild.

One thing you can do today

Check today that you can log in to your site’s panel, whose name the domain is registered in, and where the panel’s export section is; if you do not hold one of the three, ask for it in writing. If you are commissioning a site, take the questions above to the proposal meeting; you can see what we cover on our web and software page.

Sources

This article is general information, not legal, financial or technical advice. Platforms, their rules and the law change over time, so some details may have changed since 11 November 2026 or contain small errors. Before you make a decision for your business, check the current official sources or write to us.

Tell us about
your project.

Fill in the form or write to us directly, and we will agree on a day to talk.

Your first meeting is with Deniz Sezer, founder of Detmore.

First meeting free · Reply within one working day · Written proposal in 2 to 3 days · NDA ready

What do you need? pick as many as you like

Name, email and phone are required.

Contact

We reply within one working day.