Style Guide Driven Development

Style Guide Driven Development

How to combine traditional style guides and experiences made in developing websites to living style guides and the concept of style guide driven design.

28e1c6e895146e8217caf14eb56feb7b?s=128

Nico Hagenburger

December 11, 2012
Tweet

Transcript

  1. 6.
  2. 11.

    Dead Style Guides ★ Confusion about latest version ★ Hard

    to distribute ★ Hard to edit/change/keep up-to-date
  3. 13.

    Living Style Guides ★ Are made with HTML and CSS

    ★ Use the production CSS ★ Separate design and code ★ Are under Version Control (GIT)
  4. 18.

    Clever $Variables $my-color: #89cd52; .$my-color:before { content: $my-color; } <p>

    <var>$my-color</var>: <code class="$my-color"></code> </p>
  5. 22.
  6. 26.

    A Perfect Project ★ Concepts first ★ Design right after

    ★ Design turns into CSS ★ Backend developer picks out of examples
  7. 27.

    A Real Project ★ 3 months planned for coding ★

    Design delivered in the 12th week (Happened that way.)
  8. 28.

    After 7 Days ★ Most designs available as CSS dummy

    ★ Backend implemented dummies in project ★ A lot of stuff was done
  9. 30.

    The CSS Dev: ★ No setup needed (databases, …) ★

    Dummy data is self made ★ No development problems ★ No merge conflicts
  10. 31.

    The Backend Dev: ★ Knows how it should look in

    advance ★ Just needs to pick the right stuff ★ Will love you!
  11. 35.

    All Elements in One Page ★ Just open the style

    guide in every browser ★ Most issues should occur there
  12. 37.

    Add New Elements ★ Just scroll up and down if

    it fits to the rest ★ If not, change
  13. 39.

    Hints ★ Have a coding style guide ★ Have a

    system for naming classes etc. ★ Think about how to structure modules ★ Let all modules be independent