In short
- A CMS separates the words and pictures from the code, so an editor can change one without touching the other.
- An owner needs four things from it: edit text, swap an image, add a page, and not break the site doing any of them.
- WordPress, Shopify, Squarespace and Webflow bundle the CMS with the site. A headless CMS holds only the content and hands it to a site built separately.
- Headless is for businesses with more than one place the content appears, or a site built as software. It is not for a five-page brochure site.
- The right question for a vendor is not which CMS, but which three tasks you will do yourself and how long each takes.
The typo problem
Around 2004, changing the hours on a business website meant calling the person who built it, waiting a week, and receiving an invoice for a quarter hour. The site was a set of files with the words baked into them. To change a word you changed a file, and to change a file you needed to be the kind of person who changed files.
A content management system, or CMS, is the software that ended that. It keeps the words, pictures and pages in a database, keeps the design and code somewhere else, and gives an ordinary person a screen with a text box and a Save button. The site reads the database and shows whatever is there. Change the hours, press Save, done. No developer, no invoice.
That is the whole idea, and it is a good one. What happened next is the industry's usual habit: the simple idea grew features until it became a platform, the platforms grew marketplaces, and the marketplaces grew consultants to explain which one you need. This guide is the short version of that consultant.
The common ones, and what each actually is
Most of what gets called a CMS is really a CMS bundled with something else: a site builder, a store, a hosting plan. The bundle is what you are choosing. Here is the field.
| System | What it is | Who it fits | The catch |
|---|---|---|---|
| WordPress | Open-source software you install on a host. The CMS, the theme and dozens of plugins run together on one server. | Sites that need lots of editors and a huge plugin ecosystem | Every plugin is a maintenance job and a way in. Speed is a fight. |
| Squarespace, Wix | A hosted site builder with editing built in. You rent the whole thing. | A small site whose owner will build and edit it alone | You cannot leave with the site, and it will only ever do what the builder allows. |
| Shopify | A hosted store with a CMS attached for pages and posts. | Businesses whose site is mainly a shop | The content side is thin; the store side is the product. |
| Webflow | A hosted visual builder with a real CMS for structured content. | Design-led sites with a designer on staff | Monthly fees climb with content, and it is still a rented platform. |
| Headless (Sanity, Contentful, Payload, Strapi) | A CMS with no front end. It stores content and serves it through an API to whatever site or app asks. | Sites built as software; businesses with several fronts | Needs a developer to build the front. Not a weekend project. |
| No CMS | Content lives in the code. A developer changes it. | Sites that change twice a year | Every change is a request to someone else. |
The business decision between these is the subject of the DIY versus professional guide, and the WordPress versus custom spoke goes deep on the most common one. This guide stays on the technical question: what a CMS is, what you need from it, and what "headless" means when a developer says it.
What an owner actually needs from a CMS
Feature lists for content systems run to hundreds of items. The list of things a business owner does with one is short, and it is worth writing down before any demo, because demos are designed to show the hundreds.
The tasks that matter
- Edit text on an existing page and see it live within a minute, without touching layout.
- Swap an image and have it resized, compressed and cropped for you, because a 6 MB phone photo uploaded raw is the top cause of slow pages.
- Add a page that looks like the other pages, appears in the menu where you want it, and gets a proper title and description for search.
- Add a review, a project, a team member as a record, not a hand-formatted block, so it shows up everywhere it should.
- Preview before publishing and undo after.
- Give a second person access that lets them edit words but not delete the site.
- Not break anything. An editor should be unable to move the phone number off the header or push the layout sideways on a phone. If the CMS allows it, someone will eventually do it.
Headless, explained without the diagram
A traditional CMS is one piece of software that does two jobs. It stores your content, and it builds the pages visitors see. WordPress is the clear example: the same installation holds the words and draws the site.
A headless CMS does only the first job. It stores the content, structured the way your business is structured (services, locations, team members, reviews, posts), and hands it out through an API to anything that asks. The "head," the part that draws the page, is missing on purpose. A developer builds that part separately, as software, and it fetches the content it needs.
Think of a commercial kitchen with no dining room. It prepares the food to a fixed standard and sends it out the back to a restaurant, a food truck and a delivery app, all from the same prep. The kitchen does not care what the front looks like. The front does not need its own kitchen. That is headless: content prepared once and served through a website, a mobile app, a lobby sign, a partner's site, and whatever comes next, without being re-typed.
Who is this for? Three kinds of business. Anyone whose content appears in more than one place. Anyone whose site is built as software, the way the WordPress versus Next.js guide describes, because a modern framework wants to fetch content, not live inside someone else's system. And stores that need the speed of a pre-built site with editing that does not require a developer, which is the case made in headless versus traditional e-commerce.
Who is it not for? A five-page brochure site that changes twice a year, where the extra moving part buys nothing. Honesty about that is one way to tell a good vendor from one who has just learned a new word.
Headless is a kitchen with no dining room. The content is prepared once and served through every front you have, and every front you add.
The trade-offs, side by side
| Traditional (WordPress and similar) | Headless with a custom front | |
|---|---|---|
| Speed | Depends on caching and plugin discipline; usually a fight | Pages pre-built and served from the edge; fast by default |
| Security | One installation runs everything; plugins are the way in | The content system is separate and the site is mostly static files; far less to attack |
| Editing | Familiar; everything in one dashboard | Clean and structured, but the editing screen is a separate tool from the site |
| Who can build it | Almost anyone; huge labor pool | A developer who works in a modern framework |
| Up-front cost | Lower | Higher; the front is built, not installed |
| Monthly upkeep | Higher; updates and plugin conflicts | Lower; fewer parts, fewer patches |
| Adding a second front (app, kiosk, partner feed) | Awkward | Built for it |
The rows most owners weigh wrong are the last three. The up-front cost of a custom front is real, and the custom website cost guide lays it out. The upkeep row runs the other way, and over five years the total often favors the build that cost more on day one. The website cost guide puts the two numbers together.
Questions to ask before choosing one
- 1
"Show me how I change the hours on the contact page."
Watch the clicks. If the answer is a screen recording rather than a live demo, ask why.
- 2
"Show me how I add a service page."
It should use the same layout as the others and get a title and description without you knowing what those are.
- 3
"What can an editor break?"
The honest answer names the things they can and cannot touch. The dishonest one is "nothing."
- 4
"Where is the content if we leave?"
It should be exportable in a standard format you could hand to another developer. If the answer is "it is in the platform," you are renting your own words.
- 5
"How many things need updating each month, and who does it?"
For WordPress the answer is a number of plugins and a person. For a headless build the answer is usually a much shorter list. Either is fine if it is written down.
We build most client sites with a headless CMS behind a custom front because the speed and the upkeep numbers favor it, and we say so plainly. We also work with WordPress when the business case points there. The CMS development service covers both, and a fixed-price quote will name which one and why.
Get a number before you compare anyone else.
Tell us what you have and what you want more of. A real person looks before we quote, and the quote is a fixed price you can hold us to.
Go deeper
Want a plain-language answer to a technical question?
Tell us what you have been told, or what you are paying for, and a developer will explain it in words you can repeat to your partner. Free, no jargon, no pitch.
Which of these sounds like you? (pick any)
Questions people ask
Straight answers
A content management system is software that keeps a website's words, images and pages separate from its code, so that someone who is not a developer can log in, change the text or add a page, and press Save. WordPress is the best known. Site builders like Squarespace and store platforms like Shopify include one.
A CMS that stores and organizes content but does not build the pages visitors see. It hands the content out through an API to a website, app or other front that a developer builds separately. The advantage is one source of content for every channel and a site that can be built as fast, secure software. The cost is that the front has to be built.
Yes, the most widely used one. It stores content in a database and renders pages through a theme, with plugins adding features. It can also be run headless, with its editing screen used only to store content while a separate site fetches it, though at that point many developers prefer a CMS designed for the job.
If someone in the business will edit the site more than a few times a year, yes. If the site changes rarely and a developer is on call, a site with no CMS is simpler, faster and cheaper to keep. The honest test is whether you have edited the current site in the last six months.
Up front, usually yes, because the site's front end is built rather than installed. Over time, often no, because there are fewer plugins to update, less to secure and less to break. For a site that will exist five years, the total tends to favor the build with lower upkeep. The maintenance cost guide has the monthly ranges.
Usually, and it should be a condition of choosing one. Ask whether content can be exported in a standard format such as JSON, CSV or an XML export. Site builders are the weakest here; some let you export posts but not pages, layouts or images. A structured headless CMS is the easiest to leave, which is a point in its favor.
Where to go from here