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