Pages in Storybook
12 |13 | We recommend building UIs with a 14 | 19 | component-driven 20 | 21 | process starting with atomic components and ending with pages. 22 |
23 |24 | Render pages with mock data. This makes it easy to build and review page states without 25 | needing to navigate to them in your app. Here are some handy patterns for managing page data 26 | in Storybook: 27 |
28 |-
29 |
- 30 | Use a higher-level connected component. Storybook helps you compose such data from the 31 | "args" of child component stories 32 | 33 |
- 34 | Assemble data in the page component from your services. You can mock these services out 35 | using Storybook. 36 | 37 |
39 | Get a guided tutorial on component-driven development at 40 | Storybook tutorials 45 | . Read more in the 46 | docs 51 | . 52 |
53 |
20 |