Building Developer Documentation with a Fully Remote Team and Community
summary
Built and iterated over a working platformOS developer portal in a few months and matured it across 2.5 years, winning a UK Technical Communication Award for workflow and IA. Uses docs-as-code on GitHub with Markdown→Liquid templates, a one‑page contributor guide, automated testing with Node.js and TestCafe and CI/CD to staging and production. UX research runs in Figma and Playbook UX with Loopback.io, Optimal Workshop, UsabilityHub and Hotjar; Lighthouse/PageSpeed measure performance. Community edits land via pull requests and a bottom‑of‑page feedback widget.
AI-written summary · about
chapters (10)
- 0:00Introduction and overview
- 1:04Discovery phase and design thinking
- 4:12Audience research and personas
- 7:46Content inventory and sitemap
- 11:41Editorial workflow and docs as code
- 16:39Layouts navigation and design
- 19:52Implementation and performance
- 22:01Community contribution and tools
- 24:33Remote collaboration strategies
- 27:02Q&A
related talks
43mUseful and Beautiful Developer Docs and How to Create Them
25mBuilding Docs like Code: Continuous Integration for Documentation
47mEngineering Documentation
45mUseful and Beautiful Developer Docs and How to Create Them
30mBuilding technical documentation as a product at scale
59mTransforming your Documentation Process
39mDevelopers Documentation: your hidden strength
36mBuilding Docs like Code: Continuous Integration for Documentation