A new website often starts with the same question: "Which CMS should we use?"

That makes sense. For years, a CMS has been the default answer for almost every editable website. WordPress, Drupal, Joomla or another system: if content needs to change, a backend seems like the obvious choice.

But a CMS is a tool, not a starting point. For some websites it is exactly what is needed. For others, it mainly adds maintenance, complexity and cost. The better question is not: which CMS should we choose?

What does this website actually need to do, and how often does it need to change?

A CMS is useful when you actually use it

A CMS is most valuable when content changes often and several people need to manage it. It makes sense for websites with:

  • frequent news, articles or product updates
  • multiple editors, roles or approval flows
  • complex content types, media libraries or multilingual workflows

In those situations, a CMS provides structure and independence. It makes publishing easier without needing a developer every time.

But not every website works like that.

Many websites only change occasionally

A small company website, service website, portfolio or campaign landing page often needs only limited updates.

Maybe services are updated a few times per year. A case study is added. A blog post is published occasionally. A phone number, team photo or landing-page paragraph changes. You do not automatically need a large CMS for that.

A traditional CMS also brings extra work: updates, security patches, database backups, user management, plugin compatibility and more complex hosting. When a website changes only occasionally, that overhead can become larger than the benefit.

A static website is not old-fashioned

"Static" can sound like going back to a simple website from twenty years ago. In practice, it means something else.

A modern static site can be fast, responsive, accessible and visually rich. With tools such as Astro, you can still use reusable components, multilingual pages, blog posts, forms, SEO metadata and modern layouts.

The difference is mostly behind the scenes. Pages are built in advance, so visitors receive a fast, ready-to-serve version of the website. A CMS, database and server-side logic do not need to run behind every page visit.

That often means faster pages, simpler hosting, less maintenance and fewer exposed moving parts. A static site is not a limited website. It is a different technical choice. For some organisations, a new website without a CMS is the most practical version of that choice.

Start with the content workflow

The choice between a CMS and a lighter website mostly comes down to how content is updated. Ask:

  • Who needs to update content, and how often?
  • Do editors need to publish immediately without help?
  • Is there a lot of structured content, media or approval flow?
  • Would a simple review-based update process be enough?

When one or two people make changes a few times per month or per year, there are often simpler options: Markdown or structured files, a lightweight headless CMS, a small custom admin for one task, Git-based publishing with support, or updates through a development partner.

Not every organisation needs to manage every technical detail. What matters is that updates are simple, reliable and suited to the team.

A CMS does not make content good by itself

A CMS gives people fields to fill in. It does not automatically make pages clear, useful or consistent.

Heading levels can still be wrong. Meta descriptions can still be empty. Calls to action can still be vague. Old pages can still stay online because nobody knows what to do with them.

Those are content and process problems, not CMS problems. A lighter website with clear templates, one H1 per page, logical headings, specific metadata and a simple review step can sometimes create better quality than a large backend nobody really uses.

When AI can be useful

For smaller websites, AI can make content updates easier without adding a heavy CMS. Tools such as ChatGPT, Claude, Claude Code and Codex can help draft a page, shorten text, write SEO titles, check heading structure, suggest internal links or translate a page while preserving its layout.

That does not mean AI should publish everything automatically. Good project rules and human review still matter. But for a website that does not change every day, this can be a practical middle ground: the benefits of a lightweight static site combined with help for content and structure. That idea is explored further in our article about AI-assisted static websites.

When a CMS is still the better choice

A CMS is often still the best choice when many people need to edit content, information changes daily or weekly, complex permissions are needed, editorial approval flows exist, or editors must publish immediately without technical support.

The goal is not to avoid a CMS. The goal is to use one when it genuinely adds value.

Conclusion

You do not automatically need a CMS just because your website contains content that may need to be updated. A CMS is probably useful when your website involves substantial editorial work, many users, a lot of structure or frequent change. A lightweight static site may fit better when the website mainly informs, changes occasionally and you want less technical overhead.

At Colabs, we do not start from one default platform. We first look at what your website actually needs to do. Sometimes that is a CMS. Sometimes a static site with Astro, structured content and a practical update workflow is a better solution.