The stack behind this site

Everything olavarria.work runs on, and why. The constraint that shaped it all: Cloudflare free tier only, green Core Web Vitals, zero visual clutter.

Framework & rendering

Astro 6 — static HTML by default, server routes only where state lives (admin, APIs). TailwindCSS for styling with a custom design-token layer; dark mode via a .dark class, defaulting dark. View transitions via Astro's client router. No client-side framework on public pages — the JavaScript budget goes to the tools, which do real work in your browser.

Infrastructure

Everything on Cloudflare: a single Worker serves the site, D1 (SQLite at the edge) holds comments, submissions, and agent telemetry, KV caches hot reads, R2 stores blog images. Drizzle ORM for type-safe schema and forward-only migrations. Wrangler for local dev and deploys.

Quality gates

Biome for lint + format (fast, one tool), Vitest for unit tests, Playwright for end-to-end suites across every tool page at three viewports, pa11y for accessibility, Lighthouse CI for the performance budget. The omnibus npm run ci runs the lot.

Content & email

Posts are markdown in git — Astro Content Collections with Zod-validated frontmatter. Version history, portability, and backups come free with the repo. Transactional email via Resend's HTTP API (Workers can't SMTP), with the full SPF/DKIM/DMARC/MTA-STS stack configured and verified.

Workflow

Development is AI-assisted (Claude) with a phase-gated planning system — research, plan, execute, verify — and the planning artifacts live in the repo alongside the code. Every shipped phase lands in the changelog.