Building Trust Across Teams Through Documentation
summary
High‑quality repo docs cut recurring questions, speed onboarding, and convert casual readers into contributors by making code discoverable and maintainable. Use base files like README, CONTRIBUTING.md and COMMUNICATIONS.md, add metadata such as verified-by date and name plus statuses (draft/final/archived), require quarterly verification, accept doc changes via pull requests, and provide templates and searchability. These concrete steps reduce interruptions, surface issues earlier, and help recruit and retain trusted committers.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:20Why trust matters
- 5:52Core documentation types
- 9:03Making docs discoverable
- 11:35Who drives change
- 13:46Overcoming pushback
- 17:02Culture change starts here
related talks
56mEffective Documentation: The Key to Open Source Growth
35mBuilding Docs like Code: Continuous Integration for Documentation
25mBuilding Docs like Code: Continuous Integration for Documentation
45mEnsuring that Documentation is a First-class Citizen in OS Projects
44mUseful and Beautiful Developer Docs and How to Create Them
18mTechnical Documentation - How Can I Write Them Better and Why Should I Care?
44mCreating a Culture of Documentation
14mdocs docs docs