The rebuild starts with one simple rule: optimize for reading first.
That means no server-rendered complexity in phase one, no dependency-heavy UI framework, and no theme migration for its own sake. The new site is designed around long-form articles, short notes, projects, and curated topic pages.
Why Astro fits this publication
Astro gives the site a strong default shape for a content-heavy publication:
- static output by default
- Markdown and MDX authoring
- typed content collections
- small client-side JavaScript
- flexible layouts without dragging in React
It also keeps future expansion possible. Search, RSS, better article affordances, and migration utilities can arrive later without changing the core architecture.
The working shape
src/
content/
articles/
notes/
projects/
layouts/
pages/
data/
utils/
That structure keeps editorial content, layout composition, and site-wide logic separate enough to stay readable.
Static first on purpose
Cloudflare Pages is a strong fit because the site does not need authenticated sessions, server-side forms, or dynamic rendering in phase one.
Static delivery keeps the first release simpler in four useful ways:
- Fewer moving parts in production.
- Stronger default caching behavior.
- A tighter security surface.
- Lower long-term maintenance overhead.
What comes next
The first milestone focuses on layout, routes, content collections, and a clean design baseline. After that, the site can add deeper article features, local search, feeds, and content migration with much less risk.