Post

@michaelaufreiter.com feels like this is a perfect fit for editable.website.

Yes !!!

And then you can go like `sv create . --add atproto editable` and have codebase ready to go! I need to more time to help make this happen!

The atproto community is very motivated to make basic websites fully open source. It looks like editable website wants a per site fee?

Editable might not be an ideal match for that (various reasons), but there could be something similar like it built on svedit and dedicated to atproto as a backend. @danielroe.dev Would an airspace-powered website serve data dynamically from the PDS directly? Or each change triggers a static build?

it could do either. my own is dynamic.

I'm a fan of dynamic! No cache needed and less moving pieces. :) Wondering how an SSR route that live-fetches from a PDS compares to SvelteKit/Nuxt via Node + SQlite performance-wise?

With Svedit you manipulate a POJO in-memory (see debug output at the bottom of the svedit.dev demo). Wonder how much of a hassle it is to convert that format from and to atproto lexica used for storage. Maybe something like Svedit could work on atproto schema/lexica directly, avoiding conversion

airspace makes it easy to convert to/from an arbitrary format with a plugin - you can then just write/read as needed

Good to know! Really need to dig deeper into atproto — hope I get to it soon.

i’ve also added a browser oauth endpoint to airspace (from the next release!)

Good to know! @jyc.dev and I are already on it, doing experiments with Svedit/Editable on airspace (: