I’d rather have a place to actually write: short notes on what I’m building, things I run into at work, projects that don’t fit neatly on a résumé bullet. So this is that place now. The front page is just me; the writing lives at /blog, newest first.
If you want new posts by email rather than checking back, there’s a subscribe box at the bottom of the blog and every post. No account, no tracking beyond the address itself — just an email when something new goes up.
]]>Add a Markdown file to _posts/ named YYYY-MM-DD-some-title.md, with front matter at the top:
---
title: Some Title
---
The rest is normal Markdown.
Commit it and push to main. GitHub Pages rebuilds the site automatically — nothing to run locally, no build step to remember. The post shows up on /blog, newest first, at /YYYY/MM/DD/some-title/.
index.md is the front-page bio (layout home); blog.md is the post list (layout blog). Both work the same way — front matter, then Markdown. Nav links live in _includes/nav.html.
The email box in the footer posts directly to a Supabase table (subscribers) using a publishable API key that’s safe to expose client-side — it’s restricted by row-level security to inserting new rows only, so it can’t be used to read or export the list. Addresses live in the Supabase dashboard for that project. Actually emailing subscribers when a new post goes up isn’t automated yet — that’d mean wiring up an email-sending service (Resend, Postmark, etc.) behind a Supabase edge function, triggered on new posts. Worth doing once there’s an audience to email.