The document discusses style guides, including what they are, how to build one for a team or client, and how to ensure it is used. A style guide establishes consistency, reduces risks and costs, and helps communicate effectively. To build one, a team should start by looking at existing guides, selecting an approach, identifying topics, and writing and reviewing the guide. To ensure use, the guide should be included in training, kept manageable and available, and reviewed regularly with a process for changes.

1. You’ve got style, darlings
Chris Hester @ TCUK
15 Sept 2016

2. Today
• What is a style guide?
• How do I build one for my team or
client?
• How do I make sure it’s used?

3. What is a style guide?

11. Core definition
The guidelines we agree to follow when developing content

12. Why we need them
• Establish consistency
• Reduce risk
• Reduce costs
• Deliver quality documents
• Reflect organizational values
• Communicate effectively with our audience
You’ve Got Style, Darlings - Chris Hester - TCUK 2016

13. How can I build one for my team?
You’ve Got Style, Darlings - Chris Hester - TCUK 2016

14. Start with your team

15. Look at existing guides
You’ve Got Style, Darlings - Chris Hester - TCUK 2016

16. Select an approach you
like

17. Develop the guide
• Select an existing guide and adopt it for your team
• Build on a guide already in use
• Develop a guide from scratch
You’ve Got Style, Darlings - Chris Hester - TCUK 2016

19. Develop the guide
• Identify the topics
• Research the topics
• Write the topics

20. Team of one?

21. How do I make sure the guide is used?

22. Start with the basics
• Involve the team in writing and reviewing
• Include the style guide in new team member training
• Tell people how to use it
• Keep it manageable and available
• Follow the research
• Keep it current
You’ve Got Style, Darlings - Chris Hester - TCUK 2016

23. Change happens
• Ownership
• Governance
• Change requests
• Review process
You’ve Got Style, Darlings - Chris Hester - TCUK 2016

24. Change request denied

25. William Faulkner
“In writing, you must kill all your darlings.”

26. About those darlings
• Keep the context of the decision (team-based, research-based)
• Look at the big picture (project, team, organization, users)
• Let go (for now)

27. Take-aways
• A style guide is a product by your team for your users, colleagues, and
organization.
• A good guide helps, a poor guide hinders.
• Let the team chart the path for the guide’s content, changes, reviews, and
growth
You’ve Got Style, Darlings - Chris Hester - TCUK 2016

28. Resources
• Website Style Guide Resources, http://styleguides.io/
• Why You Need a Style Guide, https://blog.influenceandco.com/why-you-
need-a-content-style-guide-and-how-to-get-started
• A Complete Process for Developing a Content Style Guide, https://
gathercontent.com/blog/tone-of-voice-guide
• Developing a Departmental Style Guide, http://techwhirl.com/
developing-a-departmental-style-guide/
You’ve Got Style, Darlings - Chris Hester - TCUK 2016

29. Credits
• University of Bristol Style Guides: www.bristol.ac.uk/style-guides
• MailChimp Style Guide: styleguide.mailchimp.com
• Wordpress CSS Guide: make.wordpress.org/core/handbook/best-
practices/coding-standards/css
• GOV UK Style Guide: www.gov.uk/guidance/style-guide
• Chicago Manual of Style Online: www.chicagomanualofstyle.org/16/
contents.html
You’ve Got Style, Darlings - Chris Hester - TCUK 2016

30. Credits
• The Economist Style Guide, http://www.economist.com/styleguide/
introduction
• Yelp Style Guide, https://www.yelp.co.uk/styleguide
• Editorial style guide, University of Cambridge, https://www.cam.ac.uk/
brand-resources/guidelines/editorial-style-guide
• Pattern library, Do Something, http://forge.dosomething.org/
• BBC Global Experience Language, http://www.bbc.co.uk/gel

31. Thank you!
Chris Hester
Consultant, Owner
Red Desk Studio, Inc.
chris@reddeskstudio.com
@chris_oh
You’ve Got Style, Darlings - Chris Hester - TCUK 2016