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