Personal portfolio site — Porsche-inspired dark design.
- Astro — static site framework
- Tailwind CSS — utility-first styling
- Inter — heading font
- JetBrains Mono — monospace labels
npm install
npm run devOpen http://localhost:4321.
All content lives directly in the component files — no CMS, no config files to hunt down.
| Section | File |
|---|---|
| Hero | src/components/Hero.astro |
| Projects | src/components/Projects.astro |
| Experience | src/components/Experience.astro |
| Club Work | src/components/ClubWork.astro |
| Contact | src/components/Contact.astro |
| Nav | src/components/Nav.astro |
Each file has a clearly marked data block at the top — just replace the placeholder strings.
| Token | Value | Usage |
|---|---|---|
| Background | #0f0f0f |
Page background |
| Surface | #1a1a1a |
Cards, panels |
| Guards Red | #B00000 |
Accents, CTAs, active states |
| Text Primary | #f5f5f5 |
Headings, body |
| Text Secondary | #999999 |
Subtext, descriptions |
| Text Muted | #555555 |
Labels, metadata |
| Border | #2a2a2a |
Dividers, card borders |
npm run build # outputs to dist/
npm run preview # preview the production buildA couple of unlisted pages use Supabase as a backend, called directly from the browser (no server needed, so it still works on static GitHub Pages hosting). Setup notes are kept out of this public README — see local notes if you have them, or ask.
Both need PUBLIC_SUPABASE_URL / PUBLIC_SUPABASE_ANON_KEY set in .env
locally and as repository secrets for the deploy workflow (same pattern as
PUBLIC_GA_MEASUREMENT_ID), plus their respective SQL setup script run once
in the Supabase SQL editor. The supabase-keepalive.yml workflow pings the
database every 3 days so the free-tier project doesn't auto-pause.