What They Don't Tell You About Creating New Style Guides
summary
Notes give specific artifacts: a Responsible Communication style guide that began as personal mistake lists and a style supplement for Python; workflow advice says to move out of a word processing tool after five pages. Three concrete problems get solved — question assumptions, bring in unheard voices, provide tooling and education — with steps: beta testers, sensitivity readers, outreach to code schools, and iterative editions. The point is whether a guide is usable, adopted, and updated, not whether the topic sounds important.
AI-written summary · about
chapters (7)
- 0:00Style guide creation intro
- 4:43Why style guides matter
- 8:59Key challenges in guides
- 15:23Ethical design in guides
- 16:08Inclusivity in style guides
- 20:38Diverse feedback for guides
- 22:27Conclusion & Q&A
related talks
16mStyling for Inclusion: How Shaping a Style Guide ...
42mDesigning Inspired Style Guides
32mBuilding a style guide from the ground up: lessons learned from a lone writer
49mHow to Create and Maintain a Visual Styleguide
37mThe ABC of Coded Style Guides
29mStyleguides are dead! Long live Styleguide-Flows!
30mThe ABC of Coded Style Guides
34mThe Dream of Styleguide Driven Development
