Content management

What is a CMS?

A CMS, or content management system, is software that stores a website’s text, images and structure in one place and lets people who do not write code change what the site says. The CMS keeps content separate from the code that renders it. An editor changes a headline or a price inside the CMS, and the live site picks the change up without anyone touching a repository.

Every CMS does four things. It defines what a piece of content is made of, it gives people an interface to fill that in, it controls who is allowed to publish, and it hands the finished content to whatever draws the page. How a system does the fourth one is what separates a traditional CMS from a headless one.

A single web page, wider than the frame around it, with the parts an editor can change marked out and tagged by field type: the heading "Pricing that scales" as Text, a thumbnail row naming hero-launch.jpg as Image, and two lines of body copy as Rich text. Two faint hairlines above and below them stand for the template that lives in the code, with nothing in it to edit, and all three regions run off the right edge of the frame. ONE PAGE · WHAT AN EDITOR CHANGES TEMPLATE, IN THE CODE Pricing that scales TEXT hero-launch.jpg IMAGE Start free. Add seats when the team grows. RICH TEXT
Stands for
Content management system.
Core job
Store content once, and let people who are not developers change it.
Three kinds
Traditional, headless, and hybrid.

How does a CMS work?

A CMS has three layers. The content model says what a page or an article is made of, field by field. The store holds the values people type into those fields. The delivery layer hands those values to whatever draws the page.

The editing interface is generated from the model rather than drawn by hand. A field typed as a heading gets a single-line input. A field typed as rich text gets a writing surface. A field typed as a reference gets a picker. That is why adding a field to the model adds it to the editor.

  • Content model. The named types and fields a site is allowed to contain.
  • Editing interface. Where people write, upload, review and schedule.
  • Delivery. How finished content reaches the page, as rendered HTML or as data.

What are the three kinds of CMS?

A traditional CMS stores content and renders the website itself, from templates that live inside the same system. WordPress and Drupal work this way. One install is the database, the editor and the web server.

A headless CMS stores content and serves it over an API. A separate front end renders it. The CMS ships no templates and holds no opinion about how a page looks.

A hybrid CMS serves content over an API like a headless system and also ships a visual editing and preview layer, so the person writing the copy sees the page instead of a bare form.

What should a modern CMS do?

The bar has moved. A CMS built in 2010 had to serve pages to browsers. A CMS built now serves the same content to a browser, to an application, to a search crawler, and to a language model answering a question about the site.

That changes what good storage looks like. Content has to be structured rather than kept as one blob of HTML per page, because a blob can only be replayed while a structure can be reshaped. It also means being readable by machines on purpose: clean markdown, an index of what the site contains, and an API a program can call without scraping the pages.

  • Structured content. Fields, not page blobs, so one record can appear on three pages.
  • Drafts and review. A change is seen by someone else before it is public.
  • An API a build can call. Plus a preview that reads unpublished drafts.
  • Markdown and an llms.txt index. So an answer engine reads the content, not the layout.
  • Roles and version history. Because more than one person edits, and someone will need to undo.

When you do not need a CMS

A CMS is a cost as well as a tool. These are the cases where it pays for itself, and the cases where a folder of files is the better answer.

Not worth a CMS

4 points
  • Five static pages One developer, rare changes, no review step. Files in the repository are simpler.
  • Content that is really data Prices, stock and user records belong in the system that owns them.
  • A page that ships once A campaign page deleted in six weeks does not repay a content model.
  • Docs the engineers own Markdown beside the source keeps a doc change in the same review as the code.

Worth a CMS

4 points
  • More than one person edits The moment a second person needs to change copy, a repository becomes a queue.
  • The same content repeats A product name on nine pages should be one record, not nine strings to find.
  • Publishing has rules Drafts, an approval, and a scheduled go-live are awkward to fake with branches.
  • The content outlives the design A rebuild should not mean retyping four hundred pages into new templates.

Where BetterCMS fits

BetterCMS is a hybrid. Content is structured and served over an API, and the people who write it edit on the rendered page. That is the split most teams end up wanting, and until recently it took two products to get it.

Questions about a CMS

Short answers, in the words people search with.

  • CMS stands for content management system. A content management system is software that stores a website’s content and lets people edit and publish it without changing code.

  • Yes. WordPress is a traditional CMS, which means it both stores the content and renders the website, using themes and templates that live inside WordPress itself.

  • A website builder produces one site and keeps the content inside that site’s layout. A CMS keeps content as structured records that can be published to a website, an application, or anything else that can read the API.

  • Often not. A site of a few pages maintained by one developer is usually simpler as files in a repository. A CMS starts to pay for itself when a second person needs to publish, or when the same piece of content appears in more than one place.

  • Open source systems are free to license and cost hosting and maintenance instead. Hosted systems charge per seat, per project, or per API request, so the real number depends on how many people edit and how much traffic reads. BetterCMS charges per website, with a Free plan and paid Site plans from $18 a month, billed yearly, plus $15 a month for each Workspace member.

  • A headless or hybrid CMS can, because it serves content over HTTP and any language can make an HTTP request. A traditional CMS cannot, because its templates run inside the language the CMS itself is written in.

Your next website starts here

See BetterCMS running on your pages, not on a sample site.