8 things I learned from building a pattern library Inayaili de León Persson CSS Meetup London, August 2016 

Hi! 

First, a bit about me. 

No content

No content

No content

Pattern libraries are nice. 

No content

No content

ww.ubuntu.com www.canonical.com design.ubuntu.co eloper.ubuntu.com design.canonical.com font.ubuntu.c es.canonical.com discourse.ubuntu.com shop.ubuntu.c aas.io jujucharms.com snapcraft.io summit.ubuntu.co buntuonair.com ubuntuforums.org forms.canonical.com mmunity.ubuntu.com askubuntu.com insights.ubuntu.c pps.ubuntu.com webapps.ubuntu.com help.ubuntu.com andscape.canonical.com cn.ubuntu.com ru.ubuntu.com .ubuntu.com cloud-images.ubuntu.com tour.ubuntu.co ty.ubuntu.com wwww.ubuntu.com/usn assets.ubuntu.c fridge.ubuntu.com lists.ubuntu.com errors.ubuntu.com opcon.ubuntu.com loco.ubuntu.com planet.ubuntu.com ww.ubuntu.com www.canonical.com design.ubuntu.co eloper.ubuntu.com design.canonical.com font.ubuntu.c es.canonical.com discourse.ubuntu.com shop.ubuntu.c aas.io jujucharms.com snapcraft.io summit.ubuntu.co buntuonair.com ubuntuforums.org forms.canonical.com 

1. Put someone in charge 

No content

2. Have a roadmap 

No content

bit.ly/vanilla-roadmap 

3. Be open 

No content

4. Define the contribution process 

No content

bit.ly/vanilla-process 

5. Provide guidelines 

No content

6. Put everything in one place 

No content

7. Plan maintenance 

No content

8. Set realistic goals 

No content

And to recap… 

No content

No content

Thank you for listening. @yaili