CMS (content management system)

A CMS separates content from code. Editors work with titles, text, images and settings; templates written by developers decide how that content looks. WordPress is the best-known example, alongside systems such as Drupal and Joomla, and hosted website builders also include a CMS. A headless CMS keeps the editing and storage but leaves out the page-building, handing content to a separate front end instead.

Not every site needs one. A small site that changes a few times a year can be maintained by a developer without a CMS. The value of a CMS grows with how often non-technical people need to publish: news, events, products, team pages, articles. Content that only a developer ever touches can stay in templates, which keeps the editing screen simple for everyone else.

How it works

A traditional CMS has three layers. An admin area, behind a login, where editors write and upload. A database that stores the content, users and settings. And a theme or set of templates that turns that content into pages when someone visits, usually by running code on the server for each request or serving a cached copy.

Most systems add roles and permissions, so an author can draft articles while only an editor can publish them, plus revision history, media libraries and scheduled publishing. Extensions, called plugins or modules, add features such as forms, search engine settings, translations or a shop.

Systems differ in where they run. Self-hosted open-source systems are installed on your own hosting and can be changed freely but need updates and security care. Hosted platforms handle the software and the servers in exchange for a subscription and less freedom, and moving away from them later is usually harder.

Example

A dental association publishes congress news, a speaker list and a programme that changes weekly in the run-up to the event. With a CMS, the office manager adds speakers through a form with fields for name, photo and biography, and the template lays each one out the same way. Nobody edits code, and the developer only steps in when a new page type is needed.

To find out what CMS a site runs, view the page source and look for clues such as wp-content in file paths, which indicates WordPress, or use a free technology lookup tool. For your own site, the login address and admin screen will tell you directly. A login page at /wp-admin, /user/login or /administrator is a strong hint as well, pointing to WordPress, Drupal and Joomla respectively.

Why it matters for your business

A CMS saves money and time when content changes often, because staff can publish without booking a developer for every edit. It also brings ongoing costs: updates, plugin licences, security monitoring and the risk of the site slowing down as extensions pile up. For a site that rarely changes, a simpler setup can be cheaper and safer. Choose based on who will edit, how often and what they need to change, not on what is most popular. Also ask how content gets out again: a system that can export pages, images and structured fields cleanly makes a future redesign or platform change far cheaper than one that locks content inside its own formats.

Common mistakes

• Choosing a CMS by popularity rather than by who will edit the site and what they need to change.
• Installing plugins for every small feature until the site becomes slow and fragile.
• Giving every user administrator rights instead of the minimum role they need.
• Never applying updates because the site seems to work, leaving known vulnerabilities open.

Questions people ask

Do I need a CMS for my website?

You need one if non-technical staff will update content regularly, such as news, events, products or team pages. If the site changes only a few times a year, a developer-maintained site without a CMS can be faster, cheaper to secure and perfectly adequate.

What is the difference between a CMS and a website builder?

A website builder is a hosted product that combines a CMS, design tools and hosting in one subscription. A CMS on its own is the content software, which you can install on hosting you choose. Builders are simpler to start; a self-hosted CMS offers more control and portability.

What is the easiest CMS to use?

The easiest one is the one set up well for your content. A CMS with clear fields for each type of content, sensible roles and only the plugins you need is easy for staff, whichever brand it is. Ask to try the editing screen before committing.