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