migration guide: This page documents the method to configure storybook introduced recently in 5.3.0, consult the migration guide if you want to migrate to this format of configuring storybook.
Storybook Docs transforms your Storybook stories into world-class component documentation. Storybook Docs for Angular supports DocsPage for auto-generated docs, and MDX for rich long-form docs.
To learn more about Storybook Docs, read the general documentation. To learn the Angular specifics, read on!
- Installation
- DocsPage
- Props tables
- Manual Compodoc setup
- MDX
- IFrame height
- Inline Stories
- More resources
First add the package. Make sure that the versions for your @storybook/*
packages match:
yarn add -D @storybook/addon-docs
Then add the following to your .storybook/main.js
exports:
export default {
addons: ['@storybook/addon-docs'],
};
When you install docs you should get basic DocsPage documentation automagically for all your stories, available in the Docs
tab of the Storybook UI.
Getting Props tables for your components requires a few more steps. Docs for Angular relies on Compodoc, the excellent API documentation tool. It supports inputs
, outputs
, properties
, methods
, view/content child/children
as first class prop types.
During sb init
, you will be asked, whether you want to setup Compodoc for your project. Just answer the question with Yes. Compodoc is then ready to use!
You'll need to register Compodoc's documentation.json
file in .storybook/preview.ts
:
import { setCompodocJson } from '@storybook/addon-docs/angular';
import docJson from '../documentation.json';
setCompodocJson(docJson);
Finally, to set up compodoc, you'll first need to install Compodoc:
yarn add -D @compodoc/compodoc
Then you'll need to configure Compodoc to generate a documentation.json
file. Adding the following snippet to your projects.<project>.architect.<storybook|build-storybook>
in the angular.json
creates a metadata file ./documentation.json
each time you run storybook:
// angular.json
{
"projects": {
"your-project": {
"architect": {
"storybook": {
...,
"compodoc": true,
"compodocArgs": [
"-e",
"json",
"-d",
"." // the root folder of your project
],
},
"build-storybook": {
...,
"compodoc": true,
"compodocArgs": [
"-e",
"json",
"-d",
"." // the root folder of your project
],
}
}
}
}
}
Unfortunately, it's not currently possible to update this dynamically as you edit your components, but there's an open issue to support this with improvements to Compodoc.
Finally, be sure to fill in the component
field in your story metadata:
import { AppComponent } from './app.component';
export default {
title: 'App Component',
component: AppComponent,
};
If you haven't upgraded from storiesOf
, you can use a parameter to do the same thing:
import { storiesOf } from '@storybook/angular';
import { AppComponent } from './app.component';
storiesOf('App Component', module)
.addParameters({ component: AppComponent })
.add( ... );
MDX is a convenient way to document your components in Markdown and embed documentation components, such as stories and props tables, inline.
Docs has peer dependencies on react
. If you want to write stories in MDX, you may need to add this dependency as well:
yarn add -D react
Then update your .storybook/main.js
to make sure you load MDX files:
export default {
stories: ['../src/**/*.mdx', '../src/**/*.stories.@(js|jsx|ts|tsx)'],
};
Finally, you can create MDX files like this:
import { Meta, Story, ArgsTable } from '@storybook/addon-docs';
import { AppComponent } from './app.component';
<Meta title='App Component' component={AppComponent} />
# App Component
Some **markdown** description, or whatever you want.
<Story name='basic' height='400px'>{{
component: AppComponent,
props: {},
}}</Story>
## ArgsTable
<ArgsTable of={AppComponent} />
Yes, it's redundant to declare component
twice. Coming soon.
Also, to use the Props
doc block, you need to set up Compodoc, as described above.
When you are using template
, moduleMetadata
and/or addDecorators
with storiesOf
then you can easily translate your story to MDX, too:
import { Meta, Story, ArgsTable } from '@storybook/addon-docs';
import { CheckboxComponent, RadioButtonComponent } from './my-components';
import { moduleMetadata } from '@storybook/angular';
<Meta title='Checkbox' decorators={[
moduleMetadata({
declarations: [CheckboxComponent]
})
]} />
# Basic Checkbox
<Story name='basic check' height='400px'>{{
template: `
<div class="some-wrapper-with-padding">
<my-checkbox [checked]="checked">Some Checkbox</my-checkbox>
</div>
`,
props: {
checked: true
}
}}</Story>
# Basic Radiobutton
<Story name='basic radio' height='400px'>{{
moduleMetadata: {
declarations: [RadioButtonComponent]
}
template: `
<div class="some-wrapper-with-padding">
<my-radio-btn [checked]="checked">Some Checkbox</my-radio-btn>
</div>
`,
props: {
checked: true
}
}}</Story>
Storybook Docs renders all Angular stories inside IFrames, with a default height of 60px
. You can update this default globally, or modify the IFrame height locally per story in DocsPage
and MDX
.
To update the global default, modify .storybook/preview.ts
:
export const parameters = { docs: { story: { iframeHeight: '400px' } } };
For DocsPage
, you need to update the parameter locally in a story:
export const basic = () => ...
basic.parameters = {
docs: { story: { iframeHeight: '400px' } },
}
And for MDX
you can modify it as an attribute on the Story
element:
<Story name='basic' height='400px'>{...}</Story>
Storybook Docs renders all Angular stories inline by default.
However, you can render stories in an iframe, with a default height of 100px
(configurable using the docs.story.iframeHeight
story parameter), by using the docs.story.inline
parameter.
To do so for all stories, update .storybook/preview.js
:
export const parameters = { docs: { story: { inline: false } } };
Want to learn more? Here are some more articles on Storybook Docs: