Re:Storybook 8
by lowboy on Wednesday March 13, 2024 @06:56PM
(#39698579)
This has great discoverability for other eng teams ime. Duplication of components across multiple product teams is a drag on velocity and a major pain when you want to update brand/design across the board. In a previous role, we spun up a Storybook with the few dozen atomic React + pure HTML components, shopped it around the relevant teams. Saw great uptake for centralizing components, and a few teams did storybook-driven development for their more complex UIs. Can recommend.
Also very useful for non technical stakeholders (design, product, etc) to test UIs in isolation.
Also very useful for non technical stakeholders (design, product, etc) to test UIs in isolation.