We've been hard at work on a new website with new guides, better docs, more translations, even our very own blog. We think it looks pretty sharp, too. It's now easier than ever to just build things with AT Protocol. atproto.com
130 reposts547 likes
We've been hard at work on a new website with new guides, better docs, more translations, even our very own blog. We think it looks pretty sharp, too. It's now easier than ever to just build things with AT Protocol. atproto.com
130 reposts547 likes
new docs are a great way to do that 🙂 bsky.app/profile/geri...
We’ve been testing how machine-readable our design system documentation is. Turns out, AI agents and humans benefit from exactly the same qualities: gerireid.com/blog/ai-is-a...
For more details, check out this post by our very own @alex.bsky.team on the new atproto blog. atproto.com/blog/new-sit...
Is this intended atproto.com/llms.txt ? I was expecting markdown (like www.apptweak.com/llms.txt )
Opened an issue here, but not sure if that's right! github.com/bluesky-soci...
Awesome, thank you! And yeah, PRs very welcome: github.com/bluesky-soci...
Nice! @alex.bsky.team I think there needs to be some love put into the framing of AT vs Bluesky still in these, not sure if the content has been improved much compared to the old site but there are a few places where these two things are treated as one and the same
Some feedback here! bsky.app/profile/did:plc:…
No idea where to put feedback about the content in these new docs so I'll just dump them in this thread!
Tbh, I'd prefer if most Bsky stuff was removed from the AT docs. The worse offender I've found so far is the AT Stack doc Both "Feeds" and "Osprey & Ozone" are bsky-specific concepts, not AT.