TechDocs: Unlocking the Potential of Engineers' Collective Knowledge
summary
Spotify reports 1,600 engineers, 14,000+ software components and ~1,400 microservices and builds TechDocs into Backstage to make docs live in repos and publish automatically. Engineers get docs like code via the scaffolder that creates repo templates, a TechDocs plugin that publishes generated Markdown sites to GCS/S3/Azure Blob, and a catalog plus search to index ~4,000 internal sites. Result: documentation is created in the dev workflow and becomes discoverable without extra manual steps.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:50Emma Indal
- 1:33Spotify Engineering Organization
- 2:07Collective Knowledge
- 4:20Story
- 4:51Emmas Story
- 8:54The First Workflow
- 10:46Docslike Code
- 11:23Backstage
- 12:17Scaffolder
- 13:46Tech Talks
- 14:37Software Catalog
- 15:25Open Source
- 16:10Configurable
- 16:50Templates
- 17:25Supported Providers
- 18:07TechTalks
- 18:31Stack Overflow
- 20:00Search
- 20:46Outro
related talks
40mThe Knowledge: Towards a Culture of Engineering Documentation
42mNavigating Backstage: A Year in Developer Life
27mShifting Spotify Engineering from Spreadsheets to Backstage
26mBackstage: Shaping the Future Of Developer Experience
35mImproving Developer Experience with Backstage
05mDocs as Part of the Product: Open Source Technical Documentation at Scale
40mShaping The Future of Developer Productivity with Spotify Backstage
31mGREAT BIG ENGINEERING ORG; itty bitty docs team