Building technical documentation as a product at scale
summary
GO-JEK data team treats documentation as a product, shipping a Chronicle microsite that auto-pulls metadata and renders markdown so product owners update docs without code. A roughly 10-person team maps personas across 15–20 internal products, builds a Sketch UI kit for consistent architecture diagrams, and documents retention (example: 7 days mirror, 3 months warehouse). The site ships in about two-week build cycles, cuts daily support requests, and surfaces publishers, consumers, scale and case studies for each stream.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:23Background
- 1:11Agenda
- 2:04Data Engineering Landscape
- 3:16Data Engineering Approach
- 5:34Problems
- 7:03End Engineering
- 9:41Planning
- 11:34Content
- 14:10Design
- 17:59Narrative
- 19:12Development
- 21:26Delivery
- 23:11Feedback
- 24:05Lessons
related talks
27mThe hidden power of information assets The role of documentation in product success
44mPushing documentation (so it doesn't hurt anymore)
14mDeveloper Experience: Your documentation deserves more love!
40mAll together now: Turning technologists into documentarians
31mGREAT BIG ENGINEERING ORG; itty bitty docs team
47mBeyond Boring Text: Treating Your Architecture Documentation Like a Product
47mEngineering Documentation
27mBoost Your API with Effective Documentation Strategies