This is on standard.site? We have an internal prototype working. No ETA on when we release it.

My @standard.site plugin for @craftcms.com is live! Find it on GitHub 👇 or on Craft's plugin store. Happy to hear feedback from both the #craftcms and the #atproto side 😀 github.com/studioespres...

yoooo, hell yeah! finally part of the verified @standard.site platform gang 🫨

Check out juttu.app if you want to - add a comment section to your blog - integrate with @standard.site so that your posts appear on related feeds

Back from atmosphere conf, great time :) We loved seeing: - @standard.site working group (lots coming!) - all the ways folks in the ecosystem are publishing - Leaflet on the big screen 🤩 Excited to keep the energy going to make Leaflet even better for all the great people & communities we met!

💣

this is crazy, the standard is everywhere now

@standard.site 👀👀👀

On March 29th, we held an in-person meeting to check in with the community and discuss potential updates to the standard.site spec. A huge thank you to @cozylittle.house for putting together a detailed summary of everything we discussed. leaflet.pub/p/did:plc:ky...

uhhhhhhh.... maybe we did it already? 🫢https://github.com/emdash-cms/emdash/blob/main/packages/plugins/atproto/src/standard-site.ts cc @mk.gg

😳 Hello

Like this post if you want standard.site integrated with the Bluesky app.

You've gotta be BLOGMAXXING You've gotta be publishing one blog on @leaflet.pub and another blog on @pckt.blog and a third on @offprint.app and (you guessed it) why not *also* hook up the blog you already have with @standard.site using @sequoia.pub and sure go wild make another on @leaflet.pub and—

it's not OFFICIAL official til they implement @standard.site

On March 29th, we held an in-person meeting to check in with the community and discuss potential updates to the standard.site spec. A huge thank you to @cozylittle.house for putting together a detailed summary of everything we discussed. leaflet.pub/p/did:plc:ky...

Yes, I’ll be supporting standard.site in Micro.blog soon!

Great to meet the entire @standard.site core team, all in one place. This group is so good, we solved taxonomy *and* language interoperability in afternoon working group.

just wanted to highlight some cool people I finally got to meet. the @standard.site crew and friends. @brookie.blog, @awarm.space, @cozylittle.house, @schlage.town. great conversations with @brittanyellich.com, @hyl.st, @graham.systems and a few others I didn't connect with 😭 see you all tmrw!

Join our community on Signal to discuss Standard.site implementation and more ! signal.group#CjQKINS5Lrgq...

Just getting warmed up with @schlage.town @cozylittle.house and @awarm.space running through the history of publishing on atproto, @standard.site and what comes next

i put out some @socialde.pt, @offprint.app and @standard.site stickers at #atmosphereconf

Oh yeah, we’re at Atmosphere Conf in Vancouver by the way ! Hi 👋

Standard.site documentation is live ! We’re excited to share resources that broaden access to publishing on the social web. Explore core concepts, lexicon definitions, verification flow, and more. We can't wait to see what you'll build: standard.site/docs/introdu...

“What’s the best way to render multi-lexicon feeds?” love this. atproto content spans /many/ datasets, not just posts. what does a feed look like with @popfeed.social reviews, @standard.site articles, and @bsky.app posts about a specific piece of media?

If you host your blog or newsletter on @pckt.blog or @leaflet.pub or one of the other platforms built to use @standard.site, everything you write is 100% owned by you. It lives on a personal virtual server you own (via your Bluesky login and password) called a PDS. 3/

I need to update sKeets to render @standard.site documents so people can browse those at the same time.

Today, Bridgy Fed begins expanding beyond microblogging, starting with long-form. If your Atmosphere (Bluesky, Blacksky, Eurosky, Northsky, etc.) account is bridged, all of your @standard.site publications and documents will bridge over to the Fediverse and the web 📜↔️📃 1/4 🧵

I love exotic websites, so I rewritten my full Go + WASM (via Vecty) personal website (julien.rbrt.fr) to @standard.site lexicons and some custom rendering: tangled.org/julien.rbrt..... I have to admit it feels way more hacky, but now I can say my website lives on my PDS! #atdev #atproto

had an awesome time at atproto LA ! tysm for @chaosgreml.in for organizing this. it was so nice to meet everyone :n) also so cool to watch @zeu.dev give an awesome presentation about potatonet.app and @standard.site got to shake hands with @alex.bsky.team twice 😤🤝 thnks every1 for listening 2me

Hey @standard.site, I have just implemented your lexicons in Go! :3 tangled.org/anhgelus.wor... Lexicons, crud operations, expanding lexicons, and verifying publications are working. Permissions and verifying documents are currently missing.

just a note, lexicons CAN be standards, even if they have a branded domain. the reason @standard.site was needed was because of how complex and wide-ranging the shape of blogs are, but if blogs were as simple as images are, pckt, offprint, etc. could have just used leaflet's lexicon

@skyreader.app is pretty great for @standard.site reading btw

Toying with an idea I might try to implement later: posting on @leaflet.pub because of their editor experience, and then migrating it to my site since it's just @standard.site records

Just released v0.2.0. Now Juttu adopted @standard.site lexicon, so no custom lexicon is used.

damn, @standard.site really becoming a standard. this is crazy

Very cool to see a WordPress -> @standard.site plugin under the Automattic name! Awesome work @pfefferle.org! TBH, I think this looks a lot better than Wireservice, and I'd rather work together than duplicate the work. You should use this! github.com/Automattic/w...

The boss is publishing @standard.site lexicons from his blog now! Thank you, @pfefferle.org!!

Finally had a sec to write about the conversation component we added to the @atproto.com blog.

oops ! ‘:-)

A lexicon is a complicated piece of behind-the-scene technology. @standard.site feels cool like an exciting community action. Even the name is humorously ironic yet iconic, so it feels both cool and accessible. Branding works.

kudos for @standard.site* though. it's refreshing to see this level of interop and platforms being friendly again. super exciting stuffs! *if you're unaware, this allows various atproto-powered blogging platforms to work with each other. subscribe to something on leaflet? it'll show up on pckt!

Hello from WordPress! 👋 This post was published directly to my PDS! In the best case it show up on bsky and standard.site compatible sites! https://matthiaspfefferle.blog/2026/03/19/hello-from-wordpress-%f0%9f%91%8b/

Hey okay! How's it goingggg hmm new thread: what's on the horizon for @standard.site & the social publishing ecosystem more broadly? I'm gonna run a workshop at the conf later this month on "atmospheric publishing" & would love any ideas for fun exploratory stuff we should dig into as a community!

we have stickers 👀

Will we see you at Atmosphere Conf ?

these will be the sticker offerings from @socialde.pt and @standard.site at the #atmosconf2026

A verified standard. 😉

My blog, augment, is now not only self-hosted, but also Atmospheric thanks to @standard.site and @sequoia.pub. But, this is just the start: it will also be a space where I experiment with new ideas about what an Atmosphere-native publication can look and behave like. More in the post:

Check it out, you can now get our news from within apps like @leaflet.pub and @pckt.blog! Here's an example of our profile: leaflet.pub/p/wedistribu... Are we doing it right? 😀

First off this builds on @standard.site, which is a standard schema for sharing publications, documents, and subscriptions in a way that can be indexed by any ATProto app. For example, I can make a publication using leaflet.pub and have it be automatically discovert in the pckt.blog