What the cool kids are using
Storybook is what the cool kids are using as part of design systems. Trouble is; the cool kids are oftem morons, so it often gets used badly. Having seen it being more trouble than it was worth, I'm not evangelising. It's not going to change your life. But it is quite useful. And it looks cool. Which is important.
Another approach is to use Storybook is as part of the development process. For us, Stories are the finest grain in our Agile GitHub workflow. Everything starts with a Story.
Like any environment where experimentation is encouraged, It's quite easy to leave storybook broken or get halfway through some component and then move it into some other project or whatever. Storybook needs to be curated and always available to be useful.
- Easy to knock up and share ideas quickly
- Stories can be connected to real services like auth etc
- Great for responsive development, letting you set custom viewport sizes
The Even Better
Even betterer would be when a storybook repo could double as a GitHub package. Properly linted and CI'd, the package could be used across multiple projects while keeping the development and QA of UI components away from places that matter.