Docs or it didn't happen
summary
Argues that documentation makes or breaks open source projects and shows how WordPress handles it: migrated from Wiki to WordPress to stop spam but creates access bottlenecks, uses Google Docs Trello and Slack for drafting and triage, and adopts GitHub Issues & Projects central repo to unify reporting and track contributors. Describes a script generates PHP code reference from source, per-release doc workflows with dedicated documentarians, notes the change reduces spam but makes casual contributions harder and remains a work in progress.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:51Misconceptions
- 11:25End user docs
- 13:22Developer docs
- 18:03The perfect tool
- 21:02The transition tool
- 23:36Gutenberg
- 27:24Moving forward
related talks
30mIntegrating Communities
48mModernizing The WordPress Toolbox
48mWordPress for the Modern PHP Developer
01h 02mHacking Wordpress, a Crash Course in Writing Plugins and Widgets
28mWordPress is JavaScript
34mHow to open source a PHP package
44m"Switch your extension’s documentation to the new PHP-based rendering"
21mUsing WordPress as a Framework