// blog
Notes, SOPs & fixes.
Working notes from real projects — how I set things up, what broke, and how I fixed it. Part documentation, part field journal.
How I set up a new Astro project in 10 minutes
My standard operating procedure for spinning up an Astro project: tokens, layout, content collections, and a deploy that just works.
Read post ->
Why Astro works well for portfolio sites
Astro combines performance, Markdown content, and components without the cost of a full application when one is not needed.
Fixing Tailwind classes that vanish in Astro static builds
Classes worked in dev but disappeared in production. The cause was content-path scanning — here's the diagnosis and the fix.
Design tokens as a visual contract
Centralising colour, typography, and spacing prevents inconsistencies and speeds up visual changes on small and medium-sized sites.
Resilient forms on static websites
A static form can include a native fallback, progressive enhancement, accessible states, and configuration validation.
TIL: Fluid Compute changed how I think about edge functions
A quick note on why I stopped reaching for edge runtimes by default and what I use instead for most server work.
No posts in this category yet.