As you might imagine, we've been pretty busy this week, between being front page news in parts of the tech press and prepping for our upcoming conference! I also spoke at SCaLE last Saturday — great turnout, really engaged audience, nice questions afterward, love our community — so I've once again been cooking for a little longer than usual. That means this is going to be a short update :)

Most of the new news I have in the run-up to AtmosphereConf is about some new website features. For one thing: I have added a new "AI" button to the top bar of our docs, which pops up a Kapa.ai query interface:

At the moment, it's completely separate from our existing site search, which only indexes atproto.com. Kapa, on the other hand, indexes the community forum, Github discussions, and various READMEs that have other data that's otherwise hard to surface in docs.

I expect people will have opinions about this! What I'll say is that I really like Kapa as an AI product. For one thing, it cites its sources:

This helps a) drive hallucinations to zero and b) drive traffic (and, even more importantly, context) back to the content that it's indexed. It also gives us some insight into how often it's drawing on each of these sources for different questions:

This, imo, is a goldmine, because it lets us find coverage gaps, and helps us understand how different parts of the ecosystem are contributing to understanding atproto. I'd like to add one of the community Discord instances as a source too, but since that resource isn't technically public already, I want to give everyone a chance to try out Kapa and weigh in before we do that.

If you're really curious, I did a whole talk about how we used Kapa at my former workplace for last year's Write the Docs conference:

Honestly, I can't often bear to watch recordings of myself unless I absolutely have to, but this is one I'm genuinely proud of. Please do give Kapa a try and let us know what you think; this is a trial period, and I've made it pretty aggressively subtle on the page, since I want to make sure it complements rather than competing with our fixed attention resources.

Other than that, we got a great big Korean translation merged from community member huketo. This is great, and complements the English and Japanese translations that we relaunched the site with next month. It also made me realize that our translation UX could be improved considerably, so I'm in the middle of prepping another PR that does two things:

  1. 1.

    Integrates with https://weblate.org/ so our potential translators don't need to know how to work within our Github project structure, and

  2. 2.

    Pulls our inline code snippets out into standalone files to avoid drift or duplication in translations.

Both of these were overdue — as mentioned, I'm really finding myself thinking about docs differently when not using a framework for this site, and it was nice to channel the energy from a great contribution into some better devex. I'm hoping to have this merged soonish, but I really need to get back to working on our conference workshops!!!

Also, big thanks to for all the work they've done on organizing our upcoming LA meetup! I'm pumped to see a bunch of you before heading up to Vancouver.

Until then!