Launching tompscanlan.me on AT Protocol

This is the first post on a site that doesn't store its content in a repo. Every page you read here — the resume, this blog post, the site config itself — is a record in my AT Protocol PDS, fetched at build time and rendered to static HTML. Why I've been building OpenMeet on AT Protocol for two years. When I sat down to put up a personal site, the markdown-files-in-a-repo pattern felt wrong — I should be dogfooding the stack I'm building on. So content lives in two collections: - — site metadata (one record) - — every page, including this one Both are standard.site lexicons, used in production by Leaflet.pub and others. The bet is that "long-form content as an atproto record" becomes a primitive that survives any one site or reader app. How The site is Astro. The interesting part is one file — — which calls against my PDS at build time and returns typed records. The pages are dumb: they ask for a document by path, get back a record, and render its field. Publishing is a tiny CLI: The script reads frontmatter for metadata, takes the markdown body, and calls with an content union. Idempotent on path — re-publishing updates the same record. Next The natural next step is killing the build step. A Cloudflare Worker subscribed to the atproto jetstream, filtered to my DID, that fires the Pages deploy hook on every relevant record change. Publish from anywhere, site updates within seconds, no git commit.