Astro and Cloudflare
A website that stays understandable after launch.
Astro and Cloudflare are a good fit when your site is mostly pages, articles, and media, but it still needs proper redirects, forms, headers, and a path to change later.
How the stack works
Keep the public site simple. Add code only where it earns its place.
A CMS is useful when a team needs its editorial workflow. But a public marketing site does not always need that runtime on every request. A static-first build separates content and presentation from the few jobs that genuinely need a server-side route.
Astro builds the pages. Cloudflare serves them. Workers can handle focused tasks such as redirects, headers, and form endpoints. That makes the system easier to reason about when something needs changing.
When it fits
A business that has changed direction
The old site still has useful pages, but the current offer needs clearer language and structure.
A WordPress site with too much overhead
The site does not need comments, memberships, or a heavy editorial workflow for its next stage.
An archive with a history worth keeping
The blog matters, but its old content needs decisions rather than a blanket copy across.
A useful limit
Keep the CMS when the CMS is doing real work.
A static-first rebuild is not the right answer for every site. If several people need to publish constantly, or the site depends on memberships, complex ecommerce, or a specialised editorial workflow, the better answer may be to improve the CMS rather than replace it.