Skip to content

edmullen/srccon-style-guide-discussion

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 

Repository files navigation

Style guides (a.k.a. pattern libraries, templates)

Notes for style guide discussion for SRCCON 2014.

What is a style guide?

This is my own definition.

A style guide creates standards and best practices for a system or set of decisions that are otherwise subjective.

To note, "style" does not mean that the decisions are visual, it means that the decision that is made is subjective and based on opinion or style.

There are two main questions to think about when defining what a style guide is. The style of what system or set of decisions? And, how are standards and best practices transferred or communicated?

Wikipedia article about style guides

The style of what?

There are many different possibilities of what it is that is being styled.

  • digital interfaces (web)
  • print design/layout
  • code
  • copy
  • tone
  • visualizations
  • interactives
  • project management

Medium of the guide

How these best practices and standards are communicated can vary as well.

  • narrative
  • code
  • specifications
  • generative

Pros and cons

Pros

  • Saves time building.
  • Makes communication smoother.
  • Provides consistency.
  • Easier to maintain whatever the style guide is for.
  • Can provide for an early testbed.
  • (CSS) Ensures most minimal amount of CSS is written.

Cons

  • Takes time to create.
  • Takes time to maintain.
  • May limit creativity.
  • Requires expertise.

Examples

This is not an exhaustive list.

News

News interface examples:

News copy examples:

News code examples:

News code project templates:

Other news examples:

  • Propublica's nerds guides: A set of narrative best practices for project philosophy, application components, coding, FB/Twitter HTML tagging, and data processing.
  • NPR best practices: A set of best practice documents for project workflow, versioning, and coding for the NPR Visuals team. Tied closely to their app-template.

Non-news

Non-news interface examples:

Non-news code examples:

Non-news design examples:

Non-news copy examples:

Other non-news examples:

References

Helpful links:

Discussion

Introduction

  • Assign note taker.
  • Gatekeeper. If you speak more than twice, you should really think about speaking again.
  • Who I am and the like.
  • Our recent style guide.
  • Goals and outline:
    1. Better define a style guide
    2. What are the benefits and weaknesses
    3. How can we make style guides
    4. Can we make a general style guide
  • (depending on how many people in room) Introduce each other
    • Name
    • Org
    • Favorite thing to read on the internet, besides your own org.

Feel for the room:

Question Answer
How many people have a style guide at their organization for any purpose? _
How many people have written code? Any amount, including HTML/CSS? _
How many people have worked on a style guide of any sort? _

Examples

Let's get the creative juices flowing and look at some examples.

  • AP Stylebook
    • Copy and grammar style guide example
    • Standard for American journalism.
    • Not open.
  • BBC news style guide
    • Copy and grammar style guide example that is free and public.
    • Cross between dictionary and style guidelines.
  • Voice and Tone (MailChimp)
    • Tone example.
    • Not sure why this is a separate site when content is pretty specific to MailChimp.
    • Talks about user feelings and reasoning for responses.
    • Uses examples.
  • The Dallas Morning News Graphics Stylebook
    • Example of print-ish design guide.
    • Focuses on graphics, charts, maps, etc.
    • Exact specifications for design and layout of graphics.
    • Even has map of the building to help person get oriented.
  • Chicago Tribunes NewsApps style guide
    • Web interface example.
    • Based/forked from Bootstrap.
    • Stylings for near all HTML elements.
    • Reusable components.
    • Code-based.
  • Bootstrap
    • Web interface example.
    • Meant for general re-use.
  • NYT Objective-C Style Guide
    • Code style guide example.
  • NPR Visuals' Best Practices
    • Technical project management guide.
    • Specifics about project structure, versioning, and coding techniques.
    • Ties to their template.
  • Tarbell
    • Application/templating system for publishing lightweight web apps.
    • Makes a lot of decisions for you.

Groups (maybe)

Depending on number of people, break out into groups of about 7.

  • Number off (if lots of people), or just arbitrarily split the room.
  • Assign note taker.
  • Assign report(back)er.

Discussion points

For each question, groups should discuss then report back to whole group.

  1. What are the types of things that have style?
    • What could have a style guide?
    • Try to aim broad, like "code". But if you get in the details, that's alright too.
  2. What are the benefits and weaknesses of style guides?
    • How would you sell the idea to your org?
    • What are the perceived roadblocks of creating a style guide?
  3. How would you go about creating a style guide?
    • Pick a type of style guide. For interface, for code, for copy.
    • What are the parts you need?
    • Who do you need for it?
    • How do you keep it up to date?
    • How do ensure others are using it?
    • What tools or techniques would you use (or have you used)?
  • Can or should we make style guides to use across multiple newsrooms?
    • For instance, the AP Stylebook.
    • Or the ProPublica Nerd's Guide

About

Style guide discussion for SRCCON 2014

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors