Because great design systems are
usable by your entire team.
Slide 42
Slide 42 text
Your team is full of
designers.
Slide 43
Slide 43 text
Your team is full of
developers.
Slide 44
Slide 44 text
Your team is full of
people who want to learn.
Slide 45
Slide 45 text
Help awesome people do
awesome shit.
Slide 46
Slide 46 text
Breaking interfaces down into
patterns has been immensely
helpful in learning and re-
evaluating the best possible code
to implement them.
— Dan Cedarholm, on Pears
https://github.com/simplebits/Pears
Slide 47
Slide 47 text
No content
Slide 48
Slide 48 text
No content
Slide 49
Slide 49 text
How?
Slide 50
Slide 50 text
Build and document your design
system within the product.
Slide 51
Slide 51 text
No content
Slide 52
Slide 52 text
Or, build the components and
document them in a library.