GitHub/storybook
1
0
Fork 0
mirror of https://github.com/storybookjs/storybook.git synced 2025-04-04 22:21:27 +08:00
Code Issues Packages Projects Releases Wiki Activity

updates component reference in paragraph

Browse Source
This commit is contained in:
jonniebigodes 2021-05-13 15:26:06 +01:00
parent f06074924c
commit 5e21d8fb57
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
addons/docs/docs/docspage.md
View File

@ -59,7 +59,7 @@ If you're coming from the `storiesOf` format, there's [a codemod that adds it fo
## Subcomponents parameter
Sometimes it's useful to document multiple components on the same page. For example, suppose your component library contains `List` and `ListItem` components that don't make sense without one another. `DocsPage` has the concept of a "primary" component with the [`component` parameter](#component-parameter), and can also accept one or more "subcomponents":
Sometimes it's useful to document multiple components on the same page. For example, suppose your component library contains `Button` and `ButtonGroup` components that don't make sense without one another. `DocsPage` has the concept of a "primary" component with the [`component` parameter](#component-parameter), and can also accept one or more "subcomponents":
```js
import { Button, ButtonGroup } from '../ButtonGroup';
@ -79,7 +79,7 @@ If you want organize your documentation differently for groups of components, we
## Replacing DocsPage
What if you don't want a `DocsPage` for your storybook, for a specific component, or even for a specific story?
What if you don't want a `DocsPage` for your Storybook, for a specific component, or even for a specific story?
You can replace DocsPage at any level by overriding the `docs.page` parameter: