This site starts from a narrow premise: content should be plain files, validated at build time, and shipped as static HTML.
Why static first
Static output keeps the system small. There is no runtime CMS call, no database, and no server route between a reader and the page.
| Decision | Launch choice |
|---|---|
| Framework | Astro |
| Content | MDX |
| Hosting | Cloudflare Workers Static Assets |
| CMS | Pages CMS |
Launch checklist
- Use typed content collections.
- Keep drafts out of production.
- Publish the first real post.
The goal is not to make the most flexible publishing stack. It is to make a durable one.1
Footnotes
-
Durable here means easy to rebuild from Git and hard to break accidentally. ↩