Free Your Mind, and Your Docs Will Follow
summary
Claim: documentation improves when teams audit your rules and treat most style constraints as guidelines not mandates — aim for under 10% rules. Examples: a tutorials set pared to seven rules with version badges that still works years later; Zapier-style step diagrams that teach concepts. Tools and habits: drafting outside the CMS, using blogs to reconnect with readers. Verdict: practical, tool-focused changes and one measurable threshold, plus a small worked example that proved durable.
AI-written summary · about
chapters (12)
- 0:00Intro
- 3:05Why Cant You
- 6:37Audit Your Rules
- 7:56Rules Are Necessary
- 8:40Consistency
- 11:15Focus on the reader
- 12:02Talk about the user
- 12:30Address Federal Writing
- 13:00Straight Rotations
- 13:41Blog
- 14:06Dog Planning
- 14:43Implementation or Ink
related talks
37mTaking a step back: Analysing your documentation
15mWrite Less CSS
50mOne Rule to Rule Them All
29mHumanizing Your Documentation
46mTechnically Speaking: Improve your code with documentation
28mStop writing docs; start helping!
36mTo document, or not document that is the question
34mHumanizing Your Documentation