Skip to main content
Guides & How-To

CMS: what is it, and which type suits you?

A CMS is the program where you edit and publish content on the website yourselves. Here is the difference between a traditional and a headless CMS, and what you should ask before you choose.

Author: Agent360 editorial team
Published: 9 October 2026
Last updated: 9 October 2026
Reading time: 9 min read

In short: A CMS (content management system) is the program where you write, edit and publish content on the website and other digital channels, without a developer having to get involved in every change. There are three main types: the traditional one, where content and design are tied together in one system, the “headless” one, where the content is delivered through a technical interface (API) to website, app and screens, and a hybrid in between. For most smaller businesses, a traditional standard CMS is the right choice. Headless makes sense when the same content has to go out across several channels.

If you've ended up here, it may be because the website needs redoing, because marketing is waiting too long to get a text corrected, or because an agency has suggested a “headless CMS” and you'd like to know what that means for you. Here is a down-to-earth explanation, so that you can ask the right questions before you choose.

What is a CMS, and what does it do?

A CMS is software for creating, managing, changing and publishing digital content. It typically consists of two parts: an editing interface, where a user without a technical background can add, change and remove content, and a delivery part, which assembles the content and updates the website.

The word is also used more broadly. Internally, CMS can cover document management and archiving, and systems for images and media (DAM, Digital Asset Management) also count as a type of CMS. Here we are talking about CMS for websites and digital channels.

A CMS typically helps with:

  • Editing without code: texts, images and pages are built in templates that the business has approved.
  • Versions: changes can be tracked, so you can see who has edited what, and go back.
  • Approval and roles: content can go through fixed approval steps before publication, and permissions control who may write, edit and publish.
  • Structured content types: for example articles, products, events and authors with fixed fields, so that the same content can be reused in several places.
  • Search: content is indexed so that it can be found by date, keyword or author.
  • Publishing to several channels: especially in headless systems, where the content is fetched via API by the website, app, screens and other channels.

A CMS can be installed on your own server or bought as a cloud service. In the cloud version, the supplier takes care of servers, updates, backup and security. For orientation, W3Techs' measurements show that 31.5 per cent of all websites use none of the CMSs they measure, while WordPress, for example, is used by 40.1 per cent of all websites (accessed 6 October 2026). Simple website builders, such as Wix and Squarespace, are also CMSs in this sense.

When do you need a CMS?

Signs that it is time for a new or better CMS:

  • Small text corrections are waiting for a developer or an agency.
  • Several people write content, and you need approval before anything goes live.
  • The content has to be available in several languages.
  • The same content has to go out on the website, in an app, on screens or in newsletters.
  • You publish regularly, for example news, case studies, job postings or guides.

It may be too early to invest in a large system if you have a simple website that rarely changes. In that case a website builder can be enough.

If you sell to consumers online, build accessibility into your choice. Under the Act on accessibility requirements for products and services (Act no. 801 of 7 June 2022), webshops, shopping apps and solutions for consumers' online payment must be accessible from 28 June 2025, even if they existed before. E-commerce that sells only to businesses is not covered, and micro-enterprises (fewer than ten employees and an annual turnover or balance sheet of no more than 2 million euro) are exempt for services. If you buy a ready-made solution, it is still you, as the one providing the service to the consumer, who bears the responsibility. So ask the supplier how the system supports the requirements.

Three types of CMS

Traditional (coupled) Decoupled Headless
What it is Editing, storage and presentation in one system Editing separate from the presentation, but still with its own publishing environment Only editing and storage. The content is delivered via API, for example REST or GraphQL
Typically suits One website, one channel When the website needs more freedom in design or technology When the same content has to go out across several channels
The presentation is built With the system's own templates Partly separately Separately, by you or your developer
Needs a developer Mostly at set-up For the presentation For each channel

What does it cost?

The price depends mostly on how much is built on top of the system. Ask about these drivers:

  • Licence or subscription: what triggers a higher price: more editors, more sites or more traffic?
  • Design and set-up: templates, content types and navigation.
  • Extensions: extra modules for forms, languages, search or webshop, and who keeps them updated.
  • Operation and security: hosting, updates and backup, either with you or with the supplier.
  • Moving content from the old website.
  • Integrations with, for example, webshop, CRM, newsletter or product data.
  • Accessibility: testing and ongoing checks, if you are covered by the requirements.
  • Training of the editors.

Buy a standard system or build your own?

Building your own CMS from scratch almost never makes sense. The standard systems are mature and cover editing, versions, roles and publishing. The right question is rather which type.

A custom solution makes sense in two cases. One is a tailor-made front end on top of a headless CMS, when design, speed or several channels require it. The other is an integration layer that fetches content from the systems where it already exists, so that nobody types the same thing twice. If you have a lot of goods, product texts and images should come from a PIM system (Product Information Management, management of product data) and not be typed into the CMS.

Where does an AI layer fit in?

A CMS stores and publishes content. It doesn't write anything itself. An AI layer can take on the repetitive tasks:

  • Drafts: write a first version of a text from your notes or product data, which an editor corrects.
  • Alt texts: suggest image descriptions, so that images make sense to screen readers. A human approves.
  • Translating: produce drafts in other languages for proofreading.
  • Sorting: tag and categorise existing content and find pages that mention discontinued products or outdated information.
  • Answering: answer visitors' questions based on what actually appears on your pages.

What AI can't do: guarantee that you comply with the law, know facts that aren't in your own material, or take over editorial responsibility. Never let AI publish directly without a human in between. If you'd like to see how such workflows are tied together, read about workflow automation.

How to approach it

  1. Write down who edits, how often, and what takes too long today.
  2. Count the channels. Is it only the website, or also app, screens and newsletter? The answer points towards traditional or headless.
  3. Check the requirements, for example accessibility, if you sell to consumers and are not a micro-enterprise.
  4. Map the integrations with webshop, CRM and product data.
  5. Test the editing with the people who are going to use the system, before you choose.
  6. Plan the move of content, and clear things out along the way.

Agent360 can help you choose a CMS or build the integration layer between the CMS, webshop and your other systems, so get in touch if you'd like to talk it over.

Sources

Frequently asked questions

What is a headless CMS?

A headless CMS handles only the editing and storage of content and delivers it through a technical interface (API), for example REST or GraphQL. The presentation is built separately, by you or your developer, for each channel. It makes sense when the same content has to go out on the website, in an app, on screens and in other channels.

Is it worth building your own CMS?

No, building your own CMS from scratch almost never makes sense, because the standard systems are mature and cover editing, versions, roles and publishing. A custom solution makes sense in two cases: as a tailor-made front end on top of a headless CMS, or as an integration layer that fetches content from the systems where it already exists.

Does my website have to meet the accessibility requirements?

Yes, if you sell to consumers online: webshops, shopping apps and solutions for consumers' online payment must be accessible from 28 June 2025. E-commerce that sells only to businesses is not covered, and micro-enterprises are exempt for services. If you buy a ready-made solution, you are still responsible to the consumer yourselves.

#cms #website #headless #accessibility

What takes up your time?

Write down the task that takes up the most time. We reply whether it is worth building, and we say so if it is not.