Skip to main content
TL;DR — Google Season of Docs (GSoD) was a program that paid technical writers to improve documentation for open-source projects. The program concluded after 6 years (2019–2024), but its model and resources remain valuable for anyone interested in open-source documentation work.
Program Status: Google Season of Docs officially concluded after its 2024 cycle. The information below is preserved as a reference for similar opportunities and in case Google revives the program. Check developers.google.com/season-of-docs for any updates.

​
What Was Google Season of Docs?

Google Season of Docs brought together technical writers and open-source organizations to improve project documentation. Unlike GSoC which focuses on code, GSoD focused entirely on documentation — making open-source projects more accessible through better docs. Key aspects:
  • Budget: Google provided organizations with 5,000–5,000–15,000 to hire technical writers
  • Duration: Typically 3–6 months
  • Focus: API docs, user guides, tutorials, contributor guides, information architecture
  • Format: Fully remote

​
Why Documentation Matters for Open Source

Many excellent open-source projects struggle with adoption because their documentation is poor. GSoD addressed this by:
  • Improving getting started guides so new users can onboard faster
  • Creating API references that developers can actually use
  • Building tutorials that teach real-world usage patterns
  • Restructuring information architecture so users can find what they need

​
How the Program Worked

​
For Organizations

  1. Organizations applied with a documentation improvement proposal
  2. Google selected participating organizations
  3. Organizations hired technical writers (directly or through the program)
  4. Writers worked on the documentation project
  5. Organizations submitted a final case study

​
For Technical Writers

  1. Browse participating organizations and their project proposals
  2. Contact organizations directly with a statement of interest
  3. Organizations selected their preferred writer(s)
  4. Work on the documentation project under mentorship
  5. Get paid through the organization’s budget

​
What Made a Strong Technical Writer Application

Even though the program has ended, these principles apply to any open-source documentation opportunity:

​
Statement of Interest Template

## Contact Information
- Name, email, portfolio/website, timezone

## Technical Writing Experience
- Years of experience
- Types of documentation you've written
- Tools and technologies you're familiar with
- Links to published work samples

## Understanding of the Project
- What the project does and who uses it
- Current state of documentation (what's good, what's missing)
- Specific problems you've identified

## Proposed Approach
- What you plan to improve/create
- Your methodology (user research, content audit, etc.)
- Timeline with milestones
- How you'll measure success

## Why This Project?
- What draws you to this organization
- How your skills match their needs

​
Key Qualities Organizations Looked For

  1. Portfolio of published work — Blog posts, API docs, tutorials, user guides
  2. Technical understanding — Ability to read code and understand technical concepts
  3. Empathy for users — Writing that puts the reader first
  4. Experience with docs-as-code — Markdown, Git, static site generators
  5. Proactive communication — Reaching out before the application deadline

​
Legacy & Alternative Opportunities

While GSoD has ended, the need for open-source documentation is greater than ever. Here are ways to continue this work:

​
Active Programs with Documentation Tracks

  • Outreachy — Often has documentation and design projects
  • GSoC — Some organizations accept documentation-focused proposals
  • LFX Mentorship — Occasionally has documentation projects

​
Independent Contributions

  • Open Docs — Google’s repository for open-source documentation: github.com/google/opendocs
  • Write the Docs — Community for documentation professionals: writethedocs.org
  • Good Docs Project — Templates and best practices for open-source documentation: thegooddocsproject.dev
  • Direct contributions — Many projects welcome documentation PRs year-round

​
Skills That Transfer

If you’re a technical writer looking at open-source opportunities, these skills are universally valued:
SkillWhy It Matters
Docs-as-code (Markdown, Git, CI/CD)Most OSS projects use these tools
API documentation (OpenAPI, Swagger)High demand across all technical projects
Information architectureHelps users find what they need
User research & testingValidates that docs actually help
Static site generators (Docusaurus, MkDocs, Hugo)Used by most OSS doc sites

​
Resources

ResourceLink
Official Site (archived)developers.google.com/season-of-docs
Past Participantsdevelopers.google.com/season-of-docs/docs/participants
Open Docs Repositorygithub.com/google/opendocs
Write the Docs Communitywritethedocs.org
Good Docs Projectthegooddocsproject.dev

​
Frequently Asked Questions

No. The program concluded after its 2024 cycle. Google may bring it back in the future — check the official site for updates.
Look at Outreachy (which has documentation projects), contribute to LFX Mentorship documentation projects, or apply directly to organizations that hire technical writers. The Write the Docs community is also a good place to find opportunities.
You don’t need to be an expert programmer, but you should be comfortable reading code, using the command line, and understanding technical concepts enough to explain them clearly.