The community wrote my docs!
summary
Claim: community docs can become product docs but only with tooling and guardrails. Uses Confluence→DocBook converters (homemade plugin, Scroll DocBook Exporter, pandoc) to import about 1,000 pages out of 6,000 total, stores snapshots in VCS, and applies automated diffs plus manual merges. Outcome: import works — a 3–4 day effort per 1,000 pages — but divergence, versioning, style, licensing and competitor edits make single‑sourcing fragile without topic tagging and conditional visibility.
AI-written summary · about
chapters (5)
related talks
39mOpen Docs, Open Collaboration: Building Better Documentation with Community PRs
45mDocs That Scale: Strategies for Sustainable Documentation in Open Source Projects
40mHow to write a book for (and with) an open source community
40mDocs Tools for OSS Maintainers
50mOpen Source Survival Guide
56mEffective Documentation: The Key to Open Source Growth
35mHelping Your Community Contribute to Developer Documentation
05mMy Open Source Docs Addiction