Writing Documentation with Neurodivergent Open Source Contributors In Mind
summary
The talk argues that specific documentation changes increase contributions from neurodivergent people: set a DRI ownership for each section, publish a localization checklist and glossary, and break install or demo steps into numbered one-at-a-time actions. Practical tools recommended include PR and issue templates, collaborative drafting with HackMD, and publishing with Hugo or Docusaurus (or doxy/docusource). Also audit troubleshooting, add alt text and human captions or transcripts, and prefer consistent skeletons and style so contributors actually finish work.
AI-written summary · about
chapters (13)
- 0:00Introduction and context
- 2:03Understanding neurodiversity
- 3:48Overcoming entry barriers
- 5:02Strategies for accessible docs
- 6:42Implementation best practices
- 9:11Supporting contributors
- 11:21Accessibility and maintenance
- 12:59Structuring documentation
- 15:22Skeletons and consistency
- 17:05Project planning and scope
- 19:39Drafting and publishing tools
- 22:40Summary and conclusion
- 25:34Q&A session
related talks
23mKeeping Your Open Source Project Accessible to All
33mIncluding People
10mNeurodiversity: From struggles to solutions, tips for leading a team
15mAdopting Open Source Practices To Build More Inclusive Products and Services
45mNeurodiversity and Allyship in Tech
26mUnlocking Open Source Communities Potential: Community Handbook Best Practices to Foster Inclusivity
44mTen Practical Approaches for Building Inclusive Open Source and InnerSource..
28mInclusive contribution Guidelines for Open Source Projects