Considerations

This site isn’t just about colour or aesthetics, it’s also a frontend project in its own right. Coming from a React-heavy background, I wanted to step outside of familiar tooling and build something with a lighter, more intentional architecture. I also wanted a chance to utilise my experience in .md from my daily PM work and expand on it by tying JS into .mdx, for a more fluid article template.

After weighing options, I chose Astro . Here’s why.

Astro vs React

While React powers many interactive experiences, it wasn’t the right fit for a site that is primarily content-first, performance-aware, and stylistically expressive.

• React assumes a JavaScript-heavy runtime by default.
• Astro, by contrast, renders HTML by default and allows hydration only where needed.
• For static editorial pages, that means faster load times and smaller payloads.
• I can still bring in React components where needed:
  • Astro grants me choice.
  • I will still probably use React when building the ‘tools’ section.

Astro vs Next.js

Next.js is often the default for React developers building production sites. I even used it for my portfolio site! But in this case:

• Next favors app-like structures, and often encourages full hydration even for static content.
• Astro’s routing and component model is simpler for a publishing-focused structure.
• Markdown and MDX are first-class citizens in Astro, not bolted on.
• No need for a sprawling API layer or client-side routing unless absolutely necessary.

Astro vs Eleventy

I also considered Eleventy , which has a strong reputation for static sites and developer friendliness. This was the hardest competitor in my opinion, as I had heard about both not too long ago, and am always interested in trying something new.

• Eleventy is flexible, but lacks the same component model Astro offers.
• Astro’s hybrid rendering model gives me more control over interactivity when needed.
• Styling with Tailwind and integrating transitions felt cleaner with Astro’s modern stack.

Why Astro Feels Right for Writ in Light

• ✦ Content-first, by design
  • Markdown, MDX, and file-based routing are treated with first-class care.
• ✦ Partial hydration
  • Interactivity is opt-in, which suits ambient, performance-sensitive visuals.
• ✦ Component composability
  • Treats SEO blocks, colour maps, and previews as composable units, in a way that feels natural.
• ✦ Creative freedom
  • Astro gets out of the way when it should. The structure fades, letting words and colour take center stage.

This is a creative dev experiment.

This project isn’t just a blog. It’s a space to test tools, try out new frontend techniques, and build a UI that feels personal. Using Astro is part of that process.

• It lets me focus on clarity, speed, and craft.
• It’s opinionated about performance, but not restrictive.
• It invites a slower, more deliberate pace of development, matching the tone of the site itself.

If you’re building something that’s less like an app and more like a journal, gallery, or thought space, Astro is worth considering.