On this page 13 sections

A CMS, or content management system, is software that lets you add and change the content on your website, such as text, images and pages, without writing code. You log in, edit in a dashboard and press publish.
MDN, the web developers' reference, defines it as software that lets users publish, organise, change or remove content (opens in a new window), including text, images, video and audio.
Short answer
- A CMS is the editing tool behind your site. You change content without calling a developer.
- It stores content separately from the design, so changing the words does not break the layout.
- WordPress is the best-known example. Custom and other systems exist.
- You do not always need one. A site that rarely changes can work without it.
How a CMS works
TechTarget explains that a CMS has two parts (opens in a new window): a content management application, where you create and edit, and a content delivery application, which takes that content and builds the page a visitor sees.
In plain terms:
- You write a page or a blog post in a form, a bit like a word processor.
- The CMS saves it, usually in a database.
- When someone visits, the CMS combines your content with the site's design and shows the finished page.
IBM points out that, without a CMS, each page would be hand-coded and uploaded to the server (opens in a new window) one at a time. A CMS removes that step.
What a CMS lets you do
- Edit text, images and links on your own.
- Add pages and blog posts.
- Let several people work on the site, each with their own login and permissions.
- Keep a consistent design, because layout is set once.
- Manage search settings such as page titles and descriptions.
- Schedule posts and keep older versions.
What you can do depends on how the CMS was set up. A good developer sets it up so the parts you change often are easy to reach and the parts that could break the site are protected.
Examples of a CMS
WordPress is the most widely used. W3Techs reports it on around four in ten websites (opens in a new window). Several other systems exist, including hosted site builders and platforms for online shops. Some sites use a custom-built editor made for one business. Our own site works like this, with an editor made for our blog and page text.
W3Techs also shows that many sites use no CMS at all (opens in a new window): 29% in its March 2026 snapshot. That is normal for small sites whose content rarely changes.
Do you need a CMS?
You probably need one if:
- you want to publish news, blog posts or offers regularly;
- several people will update the site;
- you have many pages with a similar layout, such as products or services;
- you do not want to wait for a developer to fix a typo.
You may not need one if:
- the site has a few pages that rarely change;
- you are happy to ask a developer for the occasional update;
- the site is a single landing page for a campaign.
Things to ask before you choose
- Who owns it? Make sure you own your content, logins and the files, and can move them. See who owns the source code.
- Who updates it? A CMS still needs updates. WordPress, for example, says only the latest version series is actively maintained (opens in a new window).
- What can you edit? Ask for a demo of the real editor, not just the front of the site.
- How are users and permissions handled? Not everyone should be able to change everything.
- What happens to backups? Ask who takes them and how often.
- Can it grow? Check that it can handle more pages, products or languages later.
CMS, plugins and custom builds
Off-the-shelf systems like WordPress add features through plugins. A custom build adds features in its own code. Both can work well. We compare them in WordPress vs a custom website.
Traditional and headless
In a traditional CMS, the editing tool and the website are one system. In a headless CMS, the content is stored in one place and sent to one or more separate front ends. That is a more advanced set-up, explained in what a headless CMS is. How the final page is produced is a separate question, covered in static vs dynamic websites.
What it costs
A CMS can be free software, but the cost lies in the set-up, design, hosting and upkeep. See how much a website costs.
Roles and permissions
A good CMS lets you give each person the right level of access. For example, a writer can draft a post, an editor can approve it and only an administrator can change settings. This protects the site from accidental damage and keeps a record of who changed what.
Common CMS problems
- Too many plugins or add-ons, which slow the site and add things to keep updated.
- No one owns the updates, so the system falls behind.
- Everyone is an administrator, so one slip can break the site.
- No tested backups, so a bad update cannot be undone.
- Pages that only work for one editor, because the content was built in a way no one else understands.
What a good hand-over includes
When a developer finishes your site, you should receive: your logins, a short guide on how to edit the main pages, a list of the plugins or components used and their purpose, details of hosting and backups, and the name of who to contact for help.
How we can help
We build WordPress sites and custom websites with editors that fit how your team works. See our web development service, or get in touch and tell us who will update the site and how often.
Facts checked on 20 November 2026. Sources: MDN Web Docs (opens in a new window), TechTarget (opens in a new window), IBM (opens in a new window), W3Techs (opens in a new window), WordPress.org (opens in a new window). WordPress is a trademark of the WordPress Foundation.