Pages in Storybook
17 |18 | We recommend building UIs with a{' '} 19 | 24 | component-driven 25 | {' '} 26 | process starting with atomic components and ending with pages. 27 |
28 |29 | Render pages with mock data. This makes it easy to build and review page 30 | states without needing to navigate to them in your app. Here are some 31 | handy patterns for managing page data in Storybook: 32 |
33 |-
34 |
- 35 | Use a higher-level connected component. Storybook helps you compose 36 | such data from the “args” of child component stories 37 | 38 |
- 39 | Assemble data in the page component from your services. You can mock 40 | these services out using Storybook. 41 | 42 |
44 | Get a guided tutorial on component-driven development at{' '} 45 | 50 | Storybook tutorials 51 | 52 | . Read more in the{' '} 53 | 58 | docs 59 | 60 | . 61 |
62 |