I rarely use Storybook for my clients.

Instead I:

1. Use create-react-app and the company’s design system to create a custom doc site

2. Generate component metadata with react-docgen

3. Use the metadata to display component props & descriptions

4. Show code with Prism

🧵👇

Benefits:

✅ Full control over the look, feel, branding, and dev experience

✅ Can use custom tags, categories, navigation, related components, & search to improve discovery

✅ Dogfooding (Using our components and design system to create our docs) helps us vet and design them

That said, Storybook is a wonderful, low commitment way to get started. Since the stories are plain components, you can move them to your own doc site if you “outgrow” Storybook.

But I tend to have large companies as clients, so I often skip Storybook and start custom.

View original on X