What Is a CMS? A Plain Guide to Content Management Systems
Published October 24, 2026 · Last updated October 24, 2026 · By the WebSolutions LLC team
If you want to update your own website without calling a developer every time, you need a content management system, or CMS. Most business websites today run on one, even if the owner never uses the term. This guide explains what a CMS is, how it works behind the scenes, the main types and examples, how a CMS compares with a hosted website builder, and the questions to ask before you choose one.
What is a CMS?
A content management system is software that lets people publish, organise, change and remove website content, including text, images, video and other media, without editing code (MDN: CMS). You log in to an admin area, edit a page in a form or visual editor, click publish, and the change appears on the live site. The design, layout and code stay in templates that a developer sets up once, so content editors cannot accidentally break the page structure.
What a CMS does
- Content editing. A text or block editor for pages, posts, products and other content types.
- Media library. A place to upload, describe and reuse images and documents, including alternative text for accessibility.
- Users and roles. Separate permissions for administrators, editors and authors, so not everyone can change settings or install software.
- Templates and themes. Layouts that control how each type of content is displayed.
- Extensions. Plugins or modules that add features such as forms, SEO fields, e-commerce, multiple languages or booking.
- Revisions and scheduling. Earlier versions of a page you can restore, and posts that publish at a set time.
How a CMS works behind the scenes
A traditional CMS stores your content in a database. When a visitor requests a page, server-side code fetches the content and inserts it into the right template to produce the HTML the browser receives. This is what MDN describes as a dynamic website: pages are created by inserting data from a database into placeholders in HTML templates (MDN: introduction to the server side). Caching can then store finished pages so they are not rebuilt for every visitor. Our guide to static vs dynamic websites explains the difference in more detail.
Types of CMS, with examples
Traditional (coupled) CMS
The admin area, the content database and the templates that produce the public site are all part of one system. This is the most common type for business websites.
- WordPress is open-source software built on PHP and MariaDB or MySQL and licensed under the GPLv2 or later (WordPress.org: about, requirements, licence). It has a very large choice of themes and plugins.
- Joomla describes itself as a free and open-source CMS for publishing web content (Joomla: about).
- Drupal is another open-source CMS, often chosen for sites with complex content structures, many user roles or detailed permissions.
Headless CMS
A headless CMS manages content but does not produce the public pages itself. It delivers content through an API, and a separate front end, a mobile app or several channels at once display it. This gives developers freedom over the front end, but you need development work for the parts a traditional CMS gives you out of the box, such as previews, page templates and forms.
Hosted website builders
Website builders combine hosting, templates and an editor in one subscription. They work like a CMS for the person editing, but you cannot move the site's code to another host and you are limited to the features and plans the provider offers.
Flat-file CMS
Some smaller systems store content in files instead of a database. They are simple to host and back up, and suit small sites that change rarely.
Is WordPress a CMS?
Yes. WordPress is a CMS. It started as blogging software but is now used for every kind of website, from brochure sites to shops. Note the difference between the free WordPress software, which you install on hosting you choose, and hosted services that run WordPress for you on their own plans. With the self-hosted software you control the hosting, plugins and data; with a hosted service you trade some control for less maintenance.
CMS vs website builder vs custom code
| Factor | Traditional CMS | Hosted website builder | Custom code (no CMS) |
|---|---|---|---|
| Who can edit content | Anyone with a login | Anyone with a login | Usually a developer |
| Flexibility | High, through themes, plugins and custom code | Limited to the builder's features | Unlimited, but everything is built by hand |
| Hosting | Your choice of host | Included, cannot be moved | Your choice of host |
| Maintenance | Core, theme and plugin updates are your responsibility | Handled by the provider | Code and server updates by your developer |
| Good fit | Sites that change often and need features | Small sites that need to launch quickly | Small, stable sites or very specific applications |
The right choice depends on who will edit the site, how often and which features you need. Our guide on how much a website costs explains how the platform choice affects the build and running costs.
How to choose a CMS
- Who will edit the site? Ask for a demo of the editing screens and let the person who will update the site try it.
- Which content types do you need? Services, team profiles, locations, products, events or case studies each need a structure the CMS can handle.
- Which features are essential? Forms, e-commerce, booking, multiple languages or member areas. Check whether they are built in, need a plugin or need custom development.
- Where will it be hosted? Check that the CMS runs on a supported PHP or server version on your plan. See our types of web hosting guide.
- Who will maintain it? Updates, backups and security monitoring need an owner from day one.
- Can you leave? Make sure you can export your content and that the domain and hosting stay in your business's name.
Keeping a CMS secure and up to date
A CMS is software, and software needs updates. WordPress, for example, installs minor core updates such as maintenance and security releases automatically by default, while major releases, themes and plugins need your attention depending on your settings (WordPress: automatic background updates). The server's PHP version also needs to stay within its supported period (PHP: supported versions).
- Install only the plugins you need, from reputable sources, and remove the ones you no longer use.
- Give each person their own login with the lowest role that lets them do their job, and use multi-factor authentication for administrators.
- Take backups before every major update and test that you can restore them.
- Watch for abandoned plugins and themes that no longer receive updates.
Our website maintenance checklist turns this into a weekly and monthly routine, and our small business website security checklist covers logins, updates and backups in more depth. A CMS that is heavy with plugins can also become slow; our website speed optimization guide shows how to find the cause.
Do you always need a CMS?
Not always. A very small site that changes a few times a year can be built as static pages or simple templates, which are fast and have little software to update. The trade-off is that every change needs someone who can edit code. If several people will publish content regularly, a CMS usually pays for itself in saved time.
We build and maintain sites on WordPress, Joomla and Drupal, as well as custom PHP sites, as part of our website development services. If you are choosing a platform, tell us how you plan to use the site and we will suggest an option.
CMS FAQs
Short answers to common questions about content management systems.
What is a CMS in web design?
A CMS, or content management system, is software that lets you create and edit website content through an admin area instead of editing code. Designers and developers set up the templates once, and editors then add and update pages, posts, images and other content themselves.
Is WordPress a CMS?
Yes. WordPress is an open-source CMS built on PHP and MariaDB or MySQL and licensed under the GPLv2 or later. It started as blogging software and is now used for many kinds of websites, from small brochure sites to online shops.
What is a headless CMS?
A headless CMS stores and manages content but does not create the public web pages itself. It delivers content through an API to a separate front end, app or other channel, which gives developers more freedom but needs more development work.
Is a CMS better than a website builder?
It depends on your needs. A website builder is quick to set up and the provider handles hosting and updates, but you are limited to its features and cannot move the site. A self-hosted CMS gives more flexibility and control, with more maintenance responsibility.
Do I need a CMS for a small website?
Not necessarily. If the site has only a few pages and changes rarely, static pages can be faster and simpler to maintain. If several people need to update content regularly without a developer, a CMS is usually worth it.