Writing the Docs when the Protocol is the Product
summary
A docs site rewrite launches as appproto.com, aiming to subsume the Bluesky docs by surfacing lexicons as an app catalog rather than an intimidating reference. Search and multilingual help come from Kappa AI (60/40 Japanese/English usage), moderation triage uses the LLM engine Osprey with humans making final calls, and a live-badge integration proves cross-app wiring (Streamplace, Bluecast). Traffic and ecosystem numbers show 1.5 million weekly posting users with ~25k (1–2%) posting from non‑BlueSky infrastructure. Deploys run on Next.js and Render.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:07Protocol is Blue Sky’s product
- 3:11From archivist to DevRel
- 5:41Docs and DevRel combo
- 6:22AT Protocol docs structure
- 8:28Moderation challenges
- 11:36AI for moderation
- 13:40Custom docs with Next.js
- 14:42Kappa AI multilingual docs
- 17:07Third-party apps and moderation
- 18:11Open protocol pros and cons
- 19:57Feeds as protocol category
- 21:01Rescoping Blue Sky docs
- 23:10Lexicons and data models
- 25:17Interoperable internet with AT
- 26:41User stats and decentralization
- 27:46Why build on AT Protocol
- 28:27Q&A: Custom docs framework
- 29:52Q&A: Translated docs and Kappa AI
- 30:56Q&A: Chicken sandwich domain
- 31:58Q&A: Protocol vs app effort
- 33:23Q&A: Funding and sustainability
- 35:11Q&A: Fetch with AT Protocol
related talks
30mThe Blue Side of Documentation
30mBuilding technical documentation as a product at scale
59mTransforming your Documentation Process
30mBuilding Developer Documentation with a Fully Remote Team and Community
21mWriting documentations that don't suck!
23mDocumentation in the Age of AI: Why Docs Are a Product
25mGraphQL Docs: Beyond the Schema
32mBridge the Gap To OSS Adoption With Documentation: A Kubernetes Story