I love atproto bc wdym I can post my @leaflet.pub posts to my @bsky.app and then those can show up immediately on my @blento.app AND people can read these posts from any other compatible atproto blogging site like @pckt.blog ???

atproto'd my website a bit further (beyond the @standard.site integration): 1) added a "Right now" box on the homage that pulls in all kinds of atproto activity like @bsky.app posts, @popfeed.social film ratings, @bookhive.buzz reads, @tangled.org repo's etc.

My website is now on the Atmosphere! I've been building atproto apps for a while (@skyreader.app, Skyboard, SembleIt). Now my website is one too. Blog posts are @standard.site records on my PDS, rendered by a SvelteKit app. But also... 1/2 disnetdev.com/blog/an-atmospheric-website

My blog is all ATProto-powered -- you can click most records to see where they're hosted on my PDS. My website (cameron.stream) now: - Shows my @leaflet.pub articles - @at.fund endorsements - @margin.at annotations - @semble.so collections fuckin love atproto dude

My website is now on the Atmosphere! I've been building atproto apps for a while (@skyreader.app, Skyboard, SembleIt). Now my website is one too. Blog posts are @standard.site records on my PDS, rendered by a SvelteKit app. But also... 1/2 disnetdev.com/blog/an-atmospheric-website

we’re rolling out the first phase of the Bluesky + standard.site integration today! now, when you share an article from writing platforms that support standard.site (like @leaflet.pub, @pckt.blog, @offprint.app), you’ll notice the link card has more to it than a typical link card.

I’m a bit of a CMS junkie. As such, I’ve been following the development of a new crop of tools, including @leaflet.pub, @offprint.app, and @pckt.blog, that enable longform blogging on @atproto.com and integrate with @bsky.app.

The blog's standard.site records now carry cover images, a publication icon and theme, and the strongRefs Bluesky uses for enhanced link cards.

Added support for Standard.site to cross-posted Bluesky posts. This is a new convention for long-form blogging using the AT Protocol. Initially, you can think of it as extra metadata for your blog posts on Bluesky, with more interoperability between platforms possible later.

The reason I've become such a @standard.site stan is because it's forming into the first real multi-service parallel ecosystem on atproto that can survive on it's own without the need of the @bsky.app lexicons and infra

This is what “everything ecosystem” means. Bluesky isn’t going to build a longform blogging service. What they can do with longform (and many other atproto apps) is use the shared formats of the atmosphere to enhance the experience and interaction with your content, wherever you like to post.

has anyone thought about the multi repo feed yet or are we still in the era of "this is a <app.bsky.*> viewer" and "this is a <site.standard.*> viewer"

it's easier than ever to turn your standard.site writing into your own website! your posts are atproto records you own. fetch & render them anywhere, in any framework, with your own styles. live demo, try any handle 👇 standard-publication-viewer.wisp.place?handle=erlend.sh

Would you look at that. We’ve partnered with @leaflet.pub, @pckt.blog , and @offprint.app to bring you a Summer of @standard.site. Sign up for any annual paid plan, get 25% off bsky.social/about/blog/06-22-2026-summer-…