Learning by Example: Highlights from Google Season of Docs
summary
Google Season of Docs gives grants to open source projects to hire technical writers and publishes 73 case studies since 2021 that report concrete outcomes: documentation migrations double or triple effort, one project sees a 95% increase in doc viewers, another halves chat questions and another reports a 20% drop in issue noise. Projects measure visits, PRs, issues and surveys using Google Analytics or Plausible, track contributors via GitHub, pay through Open Collective, and report common hurdles: onboarding, time zones, payment friction and longer-than-expected platform moves.
AI-written summary · about
chapters (17)
- 0:00Google Season of Docs intro
- 1:06Origins vs Summer of Code
- 4:19Why docs matter for open source
- 5:42How Season of Docs works
- 8:12Documentation types and goals
- 10:39Case study highlights
- 13:34Docs energize communities
- 14:38Challenges hiring writers
- 17:47Learning from doc mistakes
- 18:48Project readiness questions
- 22:37Metrics for doc impact
- 24:26Q&A: Metrics tools
- 26:14Q&A: Past apps & device docs
- 27:40Q&A: Hiring writers
- 31:52Q&A: Writer incentives
- 33:21Q&A: AI in docs & trends
- 34:47Closing remarks
related talks
40mDocs Tools for OSS Maintainers
40mThe Knowledge: Towards a Culture of Engineering Documentation
23mDocs, Demos, and Mentors: Growing Open Source
29mThe Power of Ecosystem Thinking: Cultivating AsyncAPI Docs Community
18mRewrite the Docs!
25mLightning Talks Part 1
27mBoost Your API with Effective Documentation Strategies
26mNo Community Members Were Harmed in the Making of This Doc Sprint: How we ran a 48-hour Event to Collect Community Wisdom into a Guidebook for Newsroom Developers