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 33 | needing to navigate to them in your app. Here are some handy patterns for managing page 34 | data in Storybook: 35 |
36 |-
37 |
- 38 | Use a higher-level connected component. Storybook helps you compose such data from the 39 | "args" of child component stories 40 | 41 |
- 42 | Assemble data in the page component from your services. You can mock these services out 43 | using Storybook. 44 | 45 |
47 | Get a guided tutorial on component-driven development at{' '} 48 | 49 | Storybook tutorials 50 | 51 | . Read more in the{' '} 52 | 53 | docs 54 | 55 | . 56 |
57 |
58 | Tip Adjust the width of the canvas with the{' '}
59 |
68 | Viewports addon in the toolbar
69 |
70 |