Launching a small content site on Cloudflare Pages
A quick walkthrough of the decisions that keep a static site starter maintainable.
Small websites become expensive when the setup is harder to understand than the site itself.
This starter leans the other direction:
- the frontend is static
- content is stored in the repository
- Cloudflare Pages handles deploys from GitHub
- Decap CMS gives non-developers an editing interface without changing the underlying content model
That combination keeps the operational surface area small. Most teams can understand the whole system in one sitting, which makes handoff and maintenance much easier.
Why Astro works well here
Astro is a strong match for content-driven sites because it gives you file-based routes, static output, and a straightforward component model. You can keep pages mostly HTML-first and only add complexity when it is justified.
Why markdown still matters
Markdown remains a good default for small sites because it is:
- easy to diff in Git
- portable between tools
- easy to review in pull requests
- durable over time
Combined with Decap CMS, content editors get a friendlier UI while engineers keep a transparent repository structure.
What to add next
Once the site is live, the next sensible additions are usually:
- a custom domain
- analytics
- a Decap auth worker for production editing
- richer content types if the site proves it needs them