8. 8
Theoldway
✴ Duplication of code
✴ Inconsistent code style
✴ Poorly named classes
✴ Visual bugs, regressions
✴ Inconsistent visual system
✴ Generally unmaintainable and expensive
9. 9
A styleguide, in this context, is a developed, “living”
UI library containing all recurring styles used across a
project.
Styleguide Driven Development is the practice of
using the styleguide as the focal point for all front-end
UI development tasks.
What?
16. 16
How?
Take an inventory of design (so far)
✴ Colors?
✴ Header levels?
✴ Grid system?
✴ What modules should be created?
✴ How should things be named?
17. 17
How?
Define a structure and
choose tools
✴ User a CSS preprocessor (Sass, Stylus, etc)
✴ Use partials, if available
18. 18
How?
Use documented code style
✴ Routinely maintained and
version-controlled
✴ Include comments and todos
20. 20
How?
Build custom modules
✴ Modules are the heart of the styleguide
✴ Use a system (BEM, SMACSS, OOCSS)
✴ Make modules small
✴ Make modules versatile
21. 21
How?
Module example: The Media Object
http://www.stubbornella.org/content/2010/06/25/the-media-object-saves-hundreds-of-lines-of-code/
25. 25
Before
✴ What markup and CSS do I need?
After
✴ What modules is this page made of?
✴ Do I need to create any new ones?
✴ Future modules and pages start in styleguide
Theprocess