# CMS *Content Management System* A CMS is the software that lets someone change a website without touching code. The word covers three separate jobs — editing, storing and displaying content — and most arguments about which CMS to use are really arguments about which of the three you need. **Canonical:** https://spoko.space/glossary/cms/ **Language:** en **Category:** Technology **Also known as:** content management system, system zarządzania treścią **Published:** 2026-09-22 **Glossary:** https://spoko.space/glossary/ --- ## What it is {#what-it-is} Three jobs, usually sold as one product: **Editing** — the screens where a person writes the text, uploads the picture and presses publish. **Storing** — the database that holds it, with its own idea of what a page, a post and a product are. **Displaying** — the templates that turn stored content into the page a visitor sees. WordPress does all three, which is why it is the default answer. A headless CMS does the first two. A static site generator reading Markdown files in a repository does the third from content that has no CMS at all. ## Why it matters if you are paying for a website {#why-it-matters-if-you-are-paying-for-a-website} Because the question "do I need a CMS" is really "which of those three do I need, and who is going to use them". Two failure modes, and I meet both regularly. **A CMS nobody uses.** A five-page company site with a full editor bolted on, because it was on the checklist. The content changes twice a year, the editing screens are logged into once, and what the site actually got was a database, an admin login on a public URL and a monthly update obligation — the entire attack surface of a CMS in exchange for nothing. **No CMS where one was needed.** The opposite, and more expensive: a site whose prices, team or offer change monthly, built as files only a developer can edit. Every correction becomes a small invoice and a wait. The honest test is not the page count. It is: who changes what, how often, and can they do it without me. ## What I build when the answer is "something else" {#what-i-build-when-the-answer-is-something-else} Sometimes the content model is the problem rather than the editor. I have built a custom admin for a catalogue whose structure had outgrown what posts and custom fields could express without a diagram, and I have left WordPress in place as the editor while replacing everything in front of it — the same content, the same login, a different site. Neither is a better answer in general. The first costs more to build and fits exactly; the second costs less and inherits both the habits and the update obligations of what it kept. ## What a CMS is not {#what-a-cms-is-not} It is not a website — it produces one, or feeds one. It is not a guarantee that a non-technical person can edit safely, either: an editor over a template that assumes a particular shape of content will let someone break the page with a heading in the wrong place, and no amount of CMS fixes a layout that only works with the words it was designed around. ## Related terms {#related-terms} - [headless CMS](https://spoko.space/glossary/headless-cms/): A headless CMS stores and edits content but does not render the website. The pages are built by something else, which reads the content over an API — so the editing tools and the front end can be changed independently of each other. — Markdown: https://spoko.space/glossary/headless-cms.md - [SSG](https://spoko.space/glossary/ssg/): Static site generation builds every page into a finished HTML file before anyone visits, so a request is answered by a file server instead of by code, a database query and a template rendered on the spot. — Markdown: https://spoko.space/glossary/ssg.md - [Astro](https://spoko.space/glossary/astro/): Astro is a web framework that renders pages to HTML at build time and ships no JavaScript unless a component asks for it. Interactive pieces are declared one by one as islands, so a page carries the code for those and nothing else. — Markdown: https://spoko.space/glossary/astro.md - [Laravel](https://spoko.space/glossary/laravel/): Laravel is a PHP framework for building web applications — the kind with accounts, permissions, a database and work that runs in the background. It supplies the parts every application needs so they are not rebuilt by hand on each project. — Markdown: https://spoko.space/glossary/laravel.md ## Where I write about this {#related-posts} - [Website and Shop for a VAG Vehicle Electronics Specialist](https://spoko.space/vwtech/) — Markdown: https://spoko.space/vwtech.md Website with admin panel and product packshots for VWTECH. Includes photo processing and a proprietary CMS adapted to client needs. - [How Much Does a Custom Website Cost in 2026?](https://spoko.space/blog/how-much-does-a-website-cost/) — Markdown: https://spoko.space/blog/how-much-does-a-website-cost.md A custom business card site costs €600–1,000, a company website with CMS from €1,200, a custom online store from €2,000. See what drives the price and what to expect in 2026. - [How to Choose the Right Web Developer](https://spoko.space/blog/how-to-choose-a-web-developer/) — Markdown: https://spoko.space/blog/how-to-choose-a-web-developer.md Check the portfolio, ask about technologies, read the reviews — but there are a few things that separate a good developer from a bad one. A practical guide for business owners. ## See also {#see-also} - [Web development](https://spoko.space/web-development/) ## Sources {#sources} - [WordPress documentation](https://wordpress.org/documentation/) — The most widely deployed example, documented by the people who build it. - [Rendering on the Web](https://web.dev/articles/rendering-on-the-web) — Where the "displaying" job sits, and why it can be separated from the other two.