Websites and Tech

Content Management System (CMS)

Also called CMS

The software behind a website that lets non-developers add and edit pages, posts and images.

Quick facts: Content Management System (CMS)

Category
Websites and Tech
Also called
CMS
Level
Beginner
Affects
Publishing speed, SEO control, running costs, site security
Where to see it
WordPress, Shopify, Webflow, Squarespace, Wix and similar admin dashboards
In this article4
  1. How a content management system works
  2. Why the CMS choice matters
  3. Common mistakes with a CMS
  4. How to act on it

How a content management system works

A content management system separates what a page says from how it looks. Your words, images and settings are stored as records; the design lives in templates; and the system puts the two together whenever someone asks for a page. That is why changing a heading does not require touching code, and why a redesign can change every page at once without anyone rewriting the text.

Around that core sit the parts you actually work with day to day. An editor for writing, a media library for files, user accounts with different permissions so a writer cannot delete the shop, and some way of extending the system — plugins, apps or modules — for things the core does not do, such as forms, bookings or a product catalogue. Hosted platforms bundle all of this and run the servers for you; self-hosted systems such as WordPress give you more control and more responsibility.

Why the CMS choice matters

It decides who can publish. If updating a price or adding a page means emailing a developer and waiting, updates stop happening, and a site that stops changing slowly stops earning. The point of a content management system is that the people who know the business can put things right the same day.

It also sets the ceiling on your search work. Editing the title and description of a page, setting a clean address, adding a redirect when something moves, marking a page as not for indexing, controlling the sitemap — these are ordinary requirements, and a system that hides or omits them turns routine tasks into development jobs. Check for them before you commit, not after the content is written.

Common mistakes with a CMS

Choosing on the strength of a demo is the first. Any system looks capable when someone who built the demo is driving it; what matters is whether your own team can complete the edits they will actually make each week. Ask to try that during the sales process.

Then comes extension sprawl. Every added plugin is code you did not write, running on your site, needing updates, and occasionally conflicting with another one. Sites become slow and fragile one convenient addition at a time. The third mistake is editing live with no copy to fall back on: no staging environment, no backup, and a Friday afternoon change that takes the contact form down over a weekend.

How to act on it

Write down the jobs the site must do — publish articles, list services, take enquiries, sell products, run in more than one language — and judge candidates against that list rather than against feature counts. Include the boring requirements: user roles, backups, a staging copy, and the ability to export your content if you ever leave.

Once it is chosen, keep the installation lean, keep it updated, and give each person the smallest permission level that lets them work. Train the team on the handful of tasks they will repeat, because a system nobody understands gets used badly. If the fit is genuinely wrong, that is a case for a considered website build rather than another year of workarounds.

Do and do not

Do

  • Test the edits your team makes weekly before choosing
  • Confirm you can set titles, addresses and redirects
  • Give each user the lowest permission level needed

Do not

  • Install a plugin for every small convenience
  • Make changes on the live site without a backup
  • Pick a system on the strength of a demo

Questions people ask about this

Which content management system is best for a small business?

There is no single answer, and anyone giving one without asking about your business is guessing. The right choice depends on who will edit the site, whether you sell online, how much control you want over hosting, and what your budget looks like over several years rather than at launch. Shortlist two, try the real editing tasks in each, then decide.

Can I move my content to a different CMS later?

Usually yes, though the cost varies enormously. Text, images and page addresses can normally be exported and imported. What rarely moves cleanly is design, custom functionality and anything a plugin stored in its own format. Before choosing any system, check that it offers a genuine export, and keep your page addresses stable so a future move needs fewer redirects.

Do I still need a developer if I have a CMS?

Not for everyday content. Adding pages, publishing articles, swapping images and updating text are all meant to be self-service, and if they are not, something has been set up badly. You will still want technical help for the build itself, for custom functionality, for updates that break something, and for anything touching payments or personal data.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.