Case Study: Lucentum, creating our own React component library

About a year ago, we faced the challenge of creating a whole new React ui-kit with a completely custom look & feel to unify the styles of all the web apps for some public European institution. What challenges did we face? How did we overcome them?
How have we contributed to the React community? This is the study case of Lucentum: the first (but not last) React component library born and raised in Alicante!

Transcript

1. September 2017 Case sudy: Lucentum, creating our own React component library Flavio Corpa
2. Thanks to our sponsors!
4. Have you ever developed your own React component library *completely* from scratch? !
5. Why “lucentum”?
7. Initial Stack
11. The Block Component
15. The Icons ⬅↗
19. Whom of you have ever used classnames? *
23. Introducing react-css-props
28. The Button
33. The DatePicker
35. react-dates
37. The Language Component 345
39. react-intl
41. The Select / Autocomplete / Typeahead / Magic ✨
45. “Abstractions are good, but not always!”
46. The (stupid) Map
48. 1.073,7K (gzipped: 321,7K)
49. react-simple-maps
50. @zcreativelabs 9 205,7K (gzipped: 63K)
51. Adding Flow ⚡
53. Theming ;
59. — Linus Torvalds “Talk is cheap. SHOW ME THE CODE.”
60. Open Source?
61. Open Source
63. @FlavioCorpa kutyel