How and why you should build your own design system

I'm (Ingo) working as a front-end architect for a software company called TimoCom. My focus is to improve the CSS and JS performance of our web applications and to maintenance and build our design system. If I have some free time, mostly i develop hybrid mobile apps and follow one of my biggest hobbies: Eating pizza!I also write some articles on LinkedIn where I explain how to get motivation at work and how you can actually change / move things.

Transcript

1. HOW AND WHY YOU SHOULD BUILD YOUR OWN DESIGN SYSTEM
2. Hi! Nice to meet you 2 Works as front-end developer since 2015 at a Software Company called TimoCom. Addicted to simplicity and performance @ingokpp
3. 3 Front-end developers Back-end developers Non-developers HOW MANY ARE HERE TODAY ?
4. WHAT THE HELLVETICA? What do we need? Where do we get started? 4
5. 5 If you want to build an design system you need to consider the whole ecosystem.
6. 6 MISTAKES
7. 7 Where can i find the right logos? Is there a class for it? Can i use this button there? What is the right hex color? This is from the documentation, isn‘t it? Where can i find a code snippet of this element?
8. 8 !important Overwrites
9. 4122 Defined CSS Rules 9 2061 DAMN EXCEPTIONS
10. 10 It‘s nice to be important, but it‘s more important to be nice “ „ - H.P. Baxxter
11. 11 50 shades of gray
12. 12 DOCUMENTATION
13. 13 Documentation is like sex: when it is good, it is very, very good; and when it is bad, it is better than nothing. - Dick Brandon
14. Advantages 14 Documentation Performance Controll Consistent rules THE CONCEPT
15. 15 THANK YOU  ANY QUESTIONS?