Astro, Cloudflare Pages and the case for a minimal stack
Why this very site is ten megabytes, twelve dependencies and deploys in 30 seconds — and why yours probably should be too.
This site is built in Astro 5, styled with Tailwind CSS v4, and deployed to Cloudflare Pages. The source is a few dozen files. A production build takes a few seconds. A deploy takes another thirty.
That is not a design aesthetic; it is a design discipline. The simpler the stack, the fewer the opportunities for it to be the thing that breaks.
What Astro gets right
Static by default. Pages are HTML unless you explicitly ask for anything else. Most marketing sites have no business shipping a framework to the browser; Astro respects that.
Islands for interaction. When you do need a bit of JavaScript \u2014 a mobile menu, a theme toggle, a contact form \u2014 you ship exactly that island, nothing more.
Content collections. First-class, type-safe, file-based content. For a marketing site or a small documentation site, this is often all the CMS you need.
It gets out of the way. Astro doesn\u2019t impose a styling system, a routing abstraction beyond the filesystem, or opinions about where your data comes from.
What Cloudflare Pages gets right
Edge delivery by default. A static site served from 300+ locations needs no further performance optimisation for 95% of Australian visitors.
Git-integrated deployments. Push, preview, promote. No bespoke pipeline.
Forms, Workers and KV are right there. When a static site genuinely does need a bit of dynamic behaviour, you don\u2019t have to go somewhere else to get it.
It is honest about cost. Most small sites sit comfortably in the free tier, and the paid tier is still cheap enough that you can pay it out of petty cash.
The minimal-stack discipline
When we build a marketing site for a client, we actively avoid the temptation to add:
- A headless CMS they won\u2019t populate.
- A design system they won\u2019t maintain.
- A JavaScript framework they can\u2019t upgrade.
- A monitoring stack that outruns the risk profile.
Every one of those might be right for some client at some point. None of them is right by default. A plain, fast, well-structured Astro site on Cloudflare Pages beats an over-engineered site almost every time \u2014 and it\u2019s legitimately fun to work in.
What this means for you
If you\u2019re briefing a new website and your shortlist includes any combination of “headless CMS”, “micro-frontends” and “custom design system”, take a breath. Ask whether the simpler version of each of those is actually insufficient for your business.
Usually, it isn\u2019t.