How to write a book for (and with) an open source community
summary
A community book claims to grow international adoption and funnels proceeds back into the Typo3 association and it uses Google Docs for authoring, hands off to Apress for publishing, and stores runnable examples in a GitHub repo contributed by three people. A companion site typenbook.com exists, print sales still outpace ebooks, and the project records three mistakes (errata) so fixes are tracked. The guides are procedural and the core chapters stay high level so the book remains useful across major versions.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:20Gratitude Statement
- 7:51Why Did They Want To Write the Book
- 13:26Process
- 17:35Tools
- 20:09The Design Team
- 27:46Things That Were New to Me as a Tech Writer
- 30:43Questions
- 32:55Positivity Pass
- 33:44How Do You Balance Giving Room to Contributors with Keeping a Consistently Good Quality of Style and Format and
- 35:29Did You Use Google Docs for the Whole Book
related talks
33mToward the broader globalization of Open Source
26mUnlocking Open Source Communities Potential: Community Handbook Best Practices to Foster Inclusivity
53mVirtual Book Signing – VM Brasseur
56mEffective Documentation: The Key to Open Source Growth
19mThe community wrote my docs!
37mPeer writing and beyond: An experimental approach to sustainable open-source projects
50mOpen Source Survival Guide
30mHow you write matters in open source