Short definition
CMS — software for creating, managing and publishing website content without editing source code for every change.
Also known as: content management system.
A CMS provides an admin area for your website’s content. You don’t have to open the source code for every new piece of text, image or page. The web developer defines the design, components and technical rules; you manage the content within that framework.
CMS stands for Content Management System. Well-known examples include WordPress, Drupal and Storyblok. They solve the same basic problem in different ways.
What can you manage with a CMS?
What you can edit depends on the setup. A small CMS may offer only a title, text and image. A larger system can manage complete pages, navigation, multilingual content, forms, products or content for multiple channels.
Usually you can manage at least these parts:
- pages, titles, subheadings and plain text;
- images, videos and documents with descriptive alt text;
- navigation, links and calls to action;
- reusable blocks such as a hero, FAQ, pricing table or testimonial;
- SEO fields like the title tag, meta description and social media image;
- drafts, publication status and user permissions.
A good CMS shows editors only the options they need. That keeps pages consistent and reduces the chance of someone accidentally damaging the layout, accessibility or technical SEO.
How does a CMS work behind the scenes?
The admin area stores content in structured fields for titles, images, links and other content. The website combines that data with templates and styles to produce the final page.
In a classic CMS, content management and rendering usually happen within the same platform. WordPress, for example, pulls content from its database and uses a theme and plugins to build the page’s HTML.
In a headless CMS, content management is separate from the frontend. The CMS delivers content through an API, and a separate website or app determines how to display it. For example, Storyblok can manage the content while Astro builds the frontend.
The same content can appear on a website, in an app and on a digital screen. A headless setup requires more technical preparation than installing a standard theme.
Classic CMS and headless CMS compared
| Aspect | Classic CMS | Headless CMS |
|---|---|---|
| Frontend | Part of the same system | Separate frontend receiving content via an API |
| Getting started | Quick with a theme and plugins | More preparation and custom work |
| Content management | Pages and templates sit close together | Content is managed as reusable fields and components |
| Speed | Depends on theme, plugins, caching and hosting | Frontend can be fully static and published via a CDN |
| Multiple channels | Mainly aimed at the website | The same content can go to a website, app and other channels |
| Maintenance | Manage CMS, theme and plugins together | Maintain CMS and frontend separately |
A simple website with a proven theme can work well with a classic CMS. Custom integrations, multiple channels or strict performance requirements may favor a headless architecture.
Is WordPress a CMS?
Yes. WordPress is a classic content management system. It started as a blogging platform, but can manage complete websites and online stores through themes, plugins and customization.
WordPress has a large ecosystem, so a plugin or theme already exists for many common needs. That can speed up a first launch, but each plugin adds code that must be updated and may introduce conflicts or security work.
The themes, plugins and hosting still need to suit the website’s speed, security and expected lifespan.
What is a headless CMS?
A headless CMS manages only the content layer. The “head” — the visible website or app — is built separately, and the two connect through an API.
Editors can still use a visual editor, previews and predefined content blocks. The main difference is behind the scenes: the frontend is not bound to the CMS’s templates or rendering stack.
Developers can build the frontend separately, and the content can outlast one version of the website. A redesign does not require another content migration if the underlying structure remains usable.
Do you need technical knowledge to work with a CMS?
For day-to-day content management, usually not. An editor should be able to update pages, choose images and publish changes without writing code.
Technical knowledge is still needed for the setup. Someone must determine:
- which content types and fields are needed;
- which components editors may use;
- how content is validated;
- how previews, roles and publishing work;
- how the website renders the content;
- how updates, security and backups are managed.
The CMS experience depends heavily on the implementation. A system with unclear fields is harder to use than a simpler one tailored to the team’s workflow.
CMS or website builder: what is the difference?
A website builder such as Wix, Squarespace or Webflow combines visual design, content management, hosting and publishing in one hosted service. That makes it easy to get started without a separate development environment.
A CMS is primarily intended for managing content. The design can be part of the same system, as with WordPress, or separate, as with Storyblok. The categories overlap: many website builders include a CMS, and some CMSs include visual page builders.
A website builder works well when a quick launch and the ability to design the site yourself matter more than full technical freedom. A CMS with a custom frontend may fit better when brand identity, performance, integrations and a sustainable content structure matter more.
Which CMS fits your website?
Don’t start with the best-known brand. Start with the work people need to do in the system and answer these questions:
- Who creates and approves content?
- Which page structures and content types recur?
- Does the content need to appear in multiple languages or channels?
- Does the site need integrations with an online store, CRM, form service or other systems?
- How important are previews and roles?
- Who manages updates and security?
- Should the frontend be able to change later without a content migration?
For a small informational site, a classic CMS or website builder may be enough. A headless CMS may suit custom work, a long lifespan or content shared across channels. Choose a system your team understands and that supports the website’s technical goals.
How Straffe Sites implements a CMS
At Straffe Sites, the content structure is defined alongside the design and technical implementation, so the CMS fields match what visitors actually see.
For many custom projects, Astro is combined with Storyblok. Astro builds the frontend; Storyblok provides a visual editor and structured content. Publishing is verified through schema checks, build checks and browser testing.
Read more about Storyblok websites, or see how Straffe Sites connects a new website to your content and workflow.
Sources and further reading
The Wikipedia page on content management systems describes a CMS as software used to manage digital content throughout its lifecycle. The WordPress documentation defines a CMS as software that facilitates maintaining website content. For the headless variant, Storyblok explains how content and presentation are separated via APIs.