Docs or it didn't happen!
summary
Argues for a 5W content strategy (why/who/what/when/where), recommends QuickStarts of ten or fewer scroll‑free steps, and shows concrete practices: keep docs in the repo but don’t force a code build, require docs with patches (Linux kernel, Django, OpenStack), and run continuous publication via Read the Docs. Demonstrates tooling: test shell code blocks with shelldoc, automate style checks with meander, use modular templates and short READMEs (Minishift) and community programs like Write the Docs and Google Season of Docs.
AI-written summary · about
chapters (4)
related talks
56mEffective Documentation: The Key to Open Source Growth
35mThe practical implementation of Documentation as Code
14mdocs docs docs
01h 01mRight the docs
45mDocs as Code Fix a poor documentation culture in your organization
39mDevelopers Documentation: your hidden strength
33mWhat The Doc?!?! How to Write and Read Documentation That Allows You To Get Sh*t Done!
25mBuilding Docs like Code: Continuous Integration for Documentation