GREAT BIG ENGINEERING ORG; itty bitty docs team
summary
Tells how a 12-person docs team keeps up with a 2,000+ engineer org: content lives as code in GitHub and markdown, generated by a static-site build, with linting, broken-link alerts and an edit button for quick PRs; team maintains ~5,000 pages and ~4,000 images, funnels requests into Jira or GitHub, runs a daily on-call to disposition 12–40 PRs, uses an embed hiring pipeline from support, keeps lightweight standards as guardrails, and measures success by whether support stops creating a shadow knowledge base.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:05How we build productivity
- 7:30Docs As Code
- 8:08What's the docs site made of?
- 9:27Focus for writers
- 12:40Standards
- 13:12The nature of documentation
- 14:06"Docs matter" mindset
- 16:57Building a strong, resilient team
related talks
40mThe Knowledge: Towards a Culture of Engineering Documentation
42mEngineering Documentation
47mEngineering Documentation
30mBuilding technical documentation as a product at scale
21mTechDocs: Unlocking the Potential of Engineers' Collective Knowledge
26mWhat you get when you invest Non-Docs time in Docs tools
39mThe Documentation Dream: One Team, No Silos, Shared Goal
40mAll together now: Turning technologists into documentarians