Responsive websites can be built with Bootstrap, a frontend toolkit with components and a grid system.
Storybook
UI components and pages can be built, tested, and documented in isolation with Storybook.
About Storybook
Storybook is a frontend workshop for building UI components and pages in isolation. It lets developers render components in specific states, save those states as stories, and reuse them during development, testing, and QA without running the whole app.
It supports visual, interaction, accessibility, snapshot, and spot testing from stories, along with documentation that combines examples, Markdown, and version history. Teams can publish Storybook as a website for review, embed stories in wikis and Figma, and run it as a CI step.
Key features
- Build UI components and pages in isolation from app logic
- Save hard-to-reach component states as reusable stories
- Test appearance, interactions, accessibility and markup from stories
- Generate UI documentation with Markdown and custom pages
- Publish Storybook as a website for team review
- Embed stories in wikis, Markdown and Figma
Best for: Frontend developers and teams building and maintaining shared UI components and design systems.
Good for
- Combines isolated development, testing and documentation around reusable stories
- Incrementally adoptable and integrates with existing tools
- Stories can be published and embedded for review without touching code
Storybook at a glance
- Website
- storybook.js.org
- Category
- Development › Frontend Development
- Type
- Website
- Pricing
- Not confirmed. Check the site
- Platforms
- Web
- Open source
- Not stated
- Language
- English
- Last checked
- Oct 5, 2026 · Online when checked
- Listed
- Oct 5, 2026
Storybook alternatives
Tools and sites you could use instead, ranked by how closely they match.
Popular in Frontend Development
Well-known listings from the same topic.
Float UIfloatui.comReact Suitersuitejs.comPuckpuckeditor.comreact-springreact-spring.devshadcn-svelteshadcn-svelte.comDocusaurusdocusaurus.io
Storybook FAQ
Why build UIs in isolation?
To implement components and pages without dealing with data, APIs, or business logic, and to reproduce states and edge cases that are hard to reach in a full app.
What kinds of UI tests can use stories?
Spot tests, visual appearance tests, interaction tests, accessibility checks for WCAG and ARIA issues, coverage reports, and snapshot tests for markup.
Is something wrong or out of date?
Tell us and an editor will check it.
Own this website?
Claim this listing
Claim the listing and suggest updates yourself. An editor checks every claim first.