DOCUMENTING YOUR
STYLESHEETS USING A
STYLEGUIDE IS AWESOME
AND PERHAPS YOU SHOULD
THINK ABOUT DOING IT.
Speaking about...
Slide 2
Slide 2 text
As your codebase grows it becomes
harder and harder to create a mental
map of it as a whole.
This is especially true for your CSS
Slide 3
Slide 3 text
HEY THERE
I’m Justin Morris (@plasticine)
I am the design & frontend guy at...
Slide 4
Slide 4 text
CONTEXT
• We have a fairly large (# of Views) app
• We have a LOT of UI (editing/reading interfaces)
• We have LOTS of CSS (~11k SLOC SCSS)
• Everyone at TC writes/maintains/implements front-
end code (which is awesome)
Slide 5
Slide 5 text
CONTEXT
• Every day;
... CSS is altered across dozens of different commits
... by many devs
... all working in different areas of the codebase
Slide 6
Slide 6 text
LOL , GOOD
LUCK KEEPING
ON TOP OF THAT
Slide 7
Slide 7 text
THE PROBLEM
CSS can sometimes feel like this:
Slide 8
Slide 8 text
THE PROBLEM
...which leads to this:
DEV 1: “I need to style this widget, is there a .class for this?”
DEV 2: “Who knows! :D Just write even more CSS!”
DEV 1: “LOL, Ok! More CSS is better, right? RIGHT!?”
...which results in this (and crap code):