Sociological considerations in designing an internal documentation platform
summary
Engineers report 25 different platforms causing fragmentation, so an internal platform called Trailhead is built as the coordination point. Trailhead enforces team ownership tied to a project primitive, CI validations, and a visible vetted badge with a six-month cycle for re‑verification. Information architecture uses ~900 small spaces averaging ~18,000 docs total, flat structure with one allowed nesting level, federated search (excluding some Google Drive content), and ongoing migrations that have retired about five legacy platforms so far.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:15Context
- 5:45Fragmentation
- 11:32Freshness
- 18:43Discoverability
- 23:21Doc quality
- 27:22Interview
- 29:49Questions
related talks
27mThe hidden power of information assets The role of documentation in product success
40mThe Knowledge: Towards a Culture of Engineering Documentation
36mTo document, or not document that is the question
26mBuilding Internal Platforms to Enhance Developer Experience
42mPlatform Engineering 101: Building Internal Developer Platforms
47mBeyond Boring Text: Treating Your Architecture Documentation Like a Product
40mDocumentation Communities: Sound Strategy or Documentarian's Gambit?
40mInternal platforms in practice