Why I build static-first
For an infrastructure person, a static site is the calmest thing you can run: no database to patch, no runtime to exploit, and it survives a traffic spike without blinking.
When you’ve spent years keeping servers alive, you develop a strong preference for things that simply don’t break. A static website is one of those things.
Less to attack, less to patch
A static site is just HTML, CSS, and a little JavaScript served from disk. There’s no PHP runtime, no database, no admin login sitting on the public internet waiting to be brute-forced. The attack surface shrinks to almost nothing — which, for someone who reads security advisories for a living, is a real relief.
It survives a spike
Static files behind Nginx and a CDN like Cloudflare can absorb a front-page traffic spike on a tiny VPS. There’s no per-request database query to fall over, no connection pool to exhaust. The cache does the heavy lifting.
Fast by default
With Astro shipping almost no JavaScript, pages render quickly even on slow connections and modest phones. That’s good for readers, good for SEO, and good for the Lighthouse score I quietly care about.
Content you actually own
Posts are Markdown files in Git. They’re versioned, backed up the moment I push, and portable to any host on earth. No proprietary CMS lock-in, no export headaches later.
For a personal site, static-first isn’t a limitation — it’s the feature.