Post

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

may i suggest introducing different account badges, e.g., verified badge for accounts using their own domains instead of bluesky usernames here

new homepage is nice, but all the icons in the docs sidebar are making my eyes glaze over, esp in the spec section where it's literally the same icon 20 times lol maybe de-emphasize the icons at least? tbh I don't think they're needed at all

I think the docs portion is still a little weird

Luna@shi.gg

everything is a little mixed. docs.bsky.app has the docs for all com.atproto.*.doFunc stuff that atproto.com doesn't. at the same time atproto.com explains bluesky stuff.. why..?

Erm I don't think you released the translations The button and the auto selection is working, but there is just no change to the text

looks great! congrats on launching it! and especially thanks for keeping the URL paths intact 😁

welcome! and honestly we're concerned the OAuth tutorial in particular is longer than it could be right now — if you wind up having suggestions to make it more fun while you're working through it, we'd love to hear them!

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

have definitely rewritten loads of those framings in various spots, would love to get feedback on where you think it can be improved further :)

imo, both of these are (in an interesting way) borderline — I don't see them as inherently bsky specific, and we're doing all we can to further genericize them to make adoption more credible. part of the docs launch involves deliberately pushing the envelope here!

Fair enough for Osprey and Ozone! I agree that feeds should not be Bsky specific but IMO this is very far away from the reality today to the point where this part of the docs is confusing

Fair enough include them in the docs somewhere as examples of AT infra, but including them here without distinguishing between AT and Bsky is weird IMO

You could also solve this by renaming the guide to "Bluesky's AT Stack", which makes the references to "our stack" make a bit more sense. But I also think that doc is nice as an introduction to the different pieces of the architecture too, so removing the Bsky specific parts is my preference