Astro over Next.js
For a mostly static portfolio, Next.js ships a React runtime I don't need. Astro generates pure HTML and only hydrates what I ask (theme toggle, mobile menu). The page lands in kilobytes.
Portafolio personal
This site. Astro + Tailwind + i18n with a monochrome editorial design system.
- Myself
- Sole creator
- 2024 — 2026
- Iterating
I wanted a portfolio that didn't look like a template, that loaded instantly and forced me into deliberate design choices. The goal wasn't "look pretty" — it was "look like I decided it".
- 12
- 2
- 0 KB
One typeface (JetBrains Mono)
I tried serif + sans, then serif-only. Landed on mono for everything: titles, body, meta. It reflects my actual work (code) without dressing it up as something more "editorial". Consistency is the design.
CSS variables for theming, not classes
Switching from dark to light flips `data-theme` on `<html>` and every variable (`--bg`, `--text`, `--line`) re-resolves. Tailwind classes stay the same — they point to the variable, not the color. Theme change with zero markup edits.
AstroTypeScriptTailwind CSS v4astro-i18nextJetBrains MonoVercel
Zeitap →
AI-native legal SaaS built for Mexican law firms.