Post

back in june I migrated my own site to use an 'atproto cms', and I've been thinking how to make this usable for everyone, without requiring special atproto knowledge 👉 this hopefully fixes the rough edges + bugs it also adds support for private data + drafts via the experimental 'spaces' proposal

by this, I mean: I've been using a cms for a long time to store things like: ⚪ #ama questions people ask ⚪ talks I'm planning to give (or have given!) ⚪ my current location (which I track and expose publicly 👀) ...and so on 👉 but atproto means your pds = your data so … why not use it as a cms?

a few more details: ⚪ airspace core is 9.2 kB in production ⚪ includes automatic validators + migration utils ⚪ no need for typegen ⚪ ships with a minimal read-only live client ⚪ runs on workers and deno ... and the name is credit to @mkrl.xyz, who made an amazing brainstorming partner 🙌

0 reposts30 likes

No, I wish! But: 1. I finally migrated/rebuilt my ancient Wordpress site and picking a CMS was the biggest pain (went for Emdash as I was intrigued by the idea + never played with Astro before); 2. I decided to experiment with standard dot site and rolled a custom vibe coded implementation 🥲

I first thought it was ATProto Airtable but If I understood correctly it's more like a source generator. You feed it some lexicons you want and it handles the grunt work of setting them up in your PDS and then provides nice APIs to query data from.