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