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?

0 reposts36 likes

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 ๐Ÿ™Œ

now we just need to figure out what the ecosystem wants to do for storing rich text (that wasn't drafted via pckt/leaflet) and we got a stew going