8. What is a Coded Style Guide?
‣ Directory of your components in different states
‣ Components rendered in isolation
‣ Components built in isolation
‣ Live documentation
9. Advantages
‣ Encourage reuse and raising awareness
‣ Higher stability and lower maintenance
‣ Coherent branding
‣ Testing and documentation
13. Roll Your Own
‣ Main Goal: Add value for your users
‣ Stand on the shoulders of giants
‣ (Development) resources are scarce
14. Styleguidist
‣ Supports: Vue and React
‣ Markdown description of components
‣ Uses your jsdoc and prop types
‣ Zero config for CRA
‣ Otherwise webpack and custom config file
15.
16.
17.
18.
19. Styleguidist
‣ (+) Live code editor for every example
‣ (+) Completely customizable styles
‣ Default already beautiful
‣ (-) Markdown sometimes requires some hacking or
intermediate components
20. Storybook
‣ Supports: React, React Native, Vue and Angular, …
‣ Stories are just Javascript™
‣ Extensible via (a lot of) addons
‣ Zero config (webpack based)
21.
22.
23. Storybook & Testing
‣ Same data used for rendering & testing
‣ Automated (visual) snapshots
‣ Viewing test results in stories
‣ Manual checking more affordable (through isolation)
24. Storybook
‣ (+) Easier to demo complex (legacy) components
‣ (+) Test data can be reused
‣ (-) Styling is way less flexible
‣ (-) Creating a documentation is harder
25. Pitfalls
or: Learn from our learnings
‣ Start with “easy” components for quick wins
‣ Don’t try to do everything at once
‣ Encourage contribution & make part of reviews