What you get when you invest Non-Docs time in Docs tools
summary
Rebuild of the doc site moves content into Markdown on GitHub and a Gatsby site with GitHub Actions, adds a PR-based staging preview and custom components for callouts and code samples. Work runs across a 12-week quarter using a triad model (PM, designer, engineer) and marketers and devops. Launch drives an 85% traffic spike, sustained ~15,000 monthly uniques (about +50%), and about 104 PRs after launch—a ~350% increase in contributions.
AI-written summary · about
chapters (33)
- 0:00Intro
- 0:52Welcome
- 2:47Where I work
- 4:18Not a talk about a tool chain
- 4:31Documentation focus
- 4:45What are you annoyed about
- 5:30Roadmap
- 7:03Organization
- 7:37Organizational support
- 8:53Workload management
- 9:39Serious gut check
- 10:21Define your objectives
- 10:48Measure your outcomes
- 11:28Consider who else will be impacted
- 12:31Make it easier for nondoc stakeholders
- 13:11Stage and preview changes locally
- 13:54Ship as fast as possible
- 14:30Build the team
- 14:52Who do you need
- 15:18Marketing
- 15:45Dev Ops
- 16:10Allies
- 16:34What are you doing
- 16:59This was not a job
- 17:39Time to do the thing
- 18:25Desilo yourself
- 19:25Have you planned for the unexpected
- 20:36How are you informing other stakeholders
- 21:25How long did your project take
- 21:35How successful was your project
- 22:29Community engagement
- 23:56Paper cuts
- 24:37Sharing your deck
related talks
42mEngineering Documentation
59mTransforming your Documentation Process
35mHelping Your Community Contribute to Developer Documentation
35mBuilding Docs like Code: Continuous Integration for Documentation
40mFrom resistance to adoption: navigating the challenges of docs-like-code
42mTwo years of Markdoc: what we’ve learned about balancing developer and author experience
44mPushing documentation (so it doesn't hurt anymore)
45mDocs or it didn't happen!