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?

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

yeah, I actually (with the help of Orange Boy) drafted a very high level portable text thing, but the editor wasn't super great and I didn't love the user experience. i may end up revisiting it once we have spaces in production