Static Site vs Traditional CMS: When Should You Switch?

After moving this site from Laravel (a custom CMS with a database) to Astro (a static site), a lot of people ask: when is it actually worth switching from a traditional CMS to a static site?

Here’s what I weighed:

How often does content change? If your content gets updated multiple times a day by many non-technical people, a traditional CMS (with an admin panel) still makes more sense. A static site fits when you (or a small team) write the content and don’t mind committing to git.

How big is the editorial team? A Markdown+git-based static site is most comfortable for 1-2 people. Once the editorial team is larger than that and needs an approval workflow, a CMS (or headless CMS) becomes more efficient.

How much does minimal maintenance matter? This was my main reason for switching. No server, no database, no security patches to keep up with. For a personal project with limited maintenance time, that matters a lot.

What kind of dynamic features do you need? If you need user login, real-time comments, or per-user content personalization, a pure static site isn’t enough — you’ll need additions (serverless functions, a third-party service, and so on).

The takeaway: a static site isn’t objectively “better” than a CMS — it’s about fit with your constraints. For a personal site with limited maintenance time and content I write myself, the static site wins decisively.