What is a CMS (content management system)? A publisher's guide

A content management system is the software a publisher uses to write, organise and release articles without editing page code by hand. The term covers a wide range of products, from a single-file blog engine to a platform that feeds a website, an app and a newsletter at once. This guide gives you working definitions, sorts the main types, and lists what a publisher needs from one.

What does CMS mean?

Wikipedia defines a content management system as computer software used to create, manage, modify and publish digital content. That definition is deliberately broad. It covers the system behind a news site, a corporate intranet and a product catalogue.

For a website the more specific term is a web content management system, which Wikipedia describes as enabling the collaborative creation and maintenance of websites containing text, images, video, audio, maps and other digital media. The word collaborative matters. A CMS exists so that several people, with different skills and permissions, can work on one body of content.

The same source says a CMS typically has two major components. The content management application is the interface where people add and modify content. The content delivery application compiles that content and updates the website. Every CMS has both jobs, even if one product bundles them together and another splits them across separate services.

What does a CMS actually do for a publisher?

Strip away the product names and a CMS handles a short list of jobs. Wikipedia’s list of common features includes indexing, search and retrieval, format management and revision control, along with role-based permissions, template support, file management and audit logs.

Translate that into newsroom terms:

• Storing articles as structured content. A headline, standfirst, body, author and publication date are separate fields, not one blob of formatting.
• Controlling who can do what. A freelancer drafts, a sub-editor reviews, an editor publishes.
• Keeping history. You can see what changed in an article and who changed it, and go back if needed.
• Separating content from design. The same article can appear on a section page, in a feed and in a search result without being re-typed.
• Publishing on a schedule. Content goes live when the editors decide, not when a developer is free.

Our feature checklist turns these into questions you can ask of any product.

What are the main types of CMS?

There is no single agreed taxonomy, but four groupings cover most of what publishers meet. They overlap, and many products can be used in more than one way.

Traditional CMS

In a traditional or coupled system the editing interface, the database and the public site live together. A request for an article page makes the system fetch the content and fill in a template. WordPress and Drupal are the best-known examples of this model. It is the easiest to understand and, for one website, often the quickest to launch. The trade-off is that the front end is tied to the system’s template layer, which how themes work explains.

Headless CMS

Wikipedia says a headless architecture separates content from its delivery layer, so content can be distributed to multiple platforms through APIs rather than to a single presentation layer. Strapi’s documentation describes the product as an open-source headless CMS and says content can be queried using REST, GraphQL and lower-level APIs. Ghost’s documentation says Ghost can also be used headlessly, with its API feeding any third-party front end or custom static framework.

Headless is a good fit when several channels share content or when developers want full control of the front end. It is a poor fit for a small team with no developer, because someone has to build and maintain everything the reader sees. Our headless section lists the systems we have profiled in this group.

Static site generators

A static site generator builds every page ahead of time and publishes plain files. The Hugo website describes Hugo as one of the most popular open-source static site generators and says it renders a large site in seconds, often less. Static output is simple to host and has little to attack at request time.

For a publisher the cost is the build step. A correction goes live after a rebuild, and features that depend on live data, such as comments or search, need a separate service. Static generators are usually paired with a content editing layer rather than used bare by an editorial team.

SaaS and hosted CMS

With a hosted product the vendor runs the servers, applies updates and sets the terms. You rent access, so the questions shift from “how do we run it” to “what can we export, and what happens if the price changes”. Our licensing guide covers the contract side, and the cost guide the budget side.

How is self-hosted different from hosted?

Self-hosted software runs on infrastructure you control. You carry updates, backups and security, and you gain freedom over code, data and cost structure. Our self-hosted section lists the options, and the installation guide covers the practical steps.

Hosted products move that work to the vendor. The trade-off is dependence. Neither choice is better in general. A newsroom with a developer on staff and a need for custom workflows often prefers self-hosting, while a two-person publication that wants to write may prefer a hosted service.

What does a news or article site need from a CMS?

A publisher’s needs differ from a brochure site’s. These are the ones we would test first, in rough order.

1. A comfortable editor. The people writing every day will judge the system on this alone. See how to evaluate the editor experience.
2. Roles and review. A workflow that lets contributors submit without publishing. See contributor submissions.
3. Content structure. Sections, categories, tags and authors that match how your site is organised. See organising content.
4. Revision history. Wikipedia lists revision control as a common feature, and for editors it is how mistakes get undone.
5. Extensibility you can trust. Most sites add features through add-ons. See how plugins work.
6. Clean page output and speed. Readers meet the front end, not the admin. See news site design patterns.
7. A way out. Export of articles, images and redirects in an open format.

If you are still choosing, the CMS directory lists profiles of the products we cover and the comparison section sets them side by side.

How should you pick a type?

Start from your team, not the architecture. If you have no developer, a traditional or hosted system is almost always the practical choice. If you have developers and several delivery channels, a headless system deserves a look. If your site changes rarely and you value simple hosting, a static approach can work.

Then check the claims. Vendor pages describe the product at its best, so confirm features in the documentation and try a trial install before committing. Reading CMS reviews critically will help you weigh the rest.