So I recently came across ghost-atproto.
..and subsequently started a convo about how this integration might be more manage now that we have standard.site
For those who feel a bit uneasy about the (relatively) big Ghost as a ‘player’ in the Atmosphere, I don’t think you need to worry about a rapid adoption of atproto into the whole Ghost network; Ghost.org has made it pretty clear they are leaning into a mono-protocol strategy with the fediverse (aka the social web, aka ActivityPub) as their protocol pick.
I expect that stance to change with time, and if ghost-atproto works really well they might get there sooner rather than later (and hopefully the people hacking together the PoC/MVP for this integration would not be squeezed out of the growth sector they helped create).
I’m used to the maximum extensibility of WordPress, so I wasn’t expecting the lack thereof in Ghost apparently. I guess part of their ‘not like WP’ appeal was that they were a complete bundle for blogging, no assembly required.
Anyway, the gh issue above goes through some of the options available for ‘ghost modders’.
The goal of the MVP is to get self-hosted Ghost blogs onto the Atmosphere (on an individual, opt-in basis), so node/Ghost/atproto nerds are encouraged to share whatever advice/questions you may be sitting on 