Add styling and CSS
-Like with web applications, there are many ways to include CSS within Storybook. Learn more about setting up styling within Storybook.
- Learn moreProvide context and mocking
-Often when a story doesn't render, it's because your component is expecting a specific environment or context (like a theme provider) to be available.
- Learn moreLoad assets and resources
-To link static files (like fonts) to your projects and stories, use the - `staticDirs` configuration option to specify folders to load when - starting Storybook.
- Learn moreAutodocs
-Auto-generate living, - interactive reference documentation from your components and stories.
- Learn morePublish to Chromatic
-Publish your Storybook to review and collaborate with your entire team.
- Learn moreFigma Plugin
-Embed your stories into Figma to cross-reference the design and live - implementation in one place.
- Learn moreTesting
-Use stories to test a component in all its variations, no matter how - complex.
- Learn moreAccessibility
-Automatically test your components for a11y issues as you develop.
- Learn moreFollow guided walkthroughs on for key workflows.
- - Discover tutorialsAcme
-Pages in Storybook
-- We recommend building UIs with a{' '} - - component-driven - {' '} - process starting with atomic components and ending with pages. -
-- Render pages with mock data. This makes it easy to build and review page states without - needing to navigate to them in your app. Here are some handy patterns for managing page - data in Storybook: -
--
-
- - Use a higher-level connected component. Storybook helps you compose such data from the - "args" of child component stories - -
- - Assemble data in the page component from your services. You can mock these services out - using Storybook. - -
- Get a guided tutorial on component-driven development at{' '} - - Storybook tutorials - - . Read more in the{' '} - - docs - - . -
-