---
title: 'DocsPage'
---

<div class="aside">

💡 <strong>NOTE</strong>: Currently there's an issue when using MDX stories with IE11. This issue does <strong>not</strong> apply to DocsPage. If you're interested in helping us fix this issue, read our <a href="https://github.com/storybookjs/storybook/blob/next/CONTRIBUTING.md">Contribution guidelines</a> and submit a pull request.

</div>

When you install [Storybook Docs](https://storybook.js.org/addons/@storybook/addon-docs), DocsPage is the zero-config default documentation that all stories get out of the box. It aggregates your [stories](../get-started/whats-a-story.md), text descriptions, docgen comments, [args tables](./doc-blocks.md#argstable), and code examples into a single page for each component.

The best practice for docs is for each component to have its own set of documentation and stories.

## Component parameter

Storybook uses the `component` key in the story file’s default export to extract the component's description and props.

<!-- prettier-ignore-start -->

<CodeSnippets
  paths={[
    'common/my-component-story.js.mdx',
  ]}
/>

<!-- prettier-ignore-end -->

## Subcomponents parameter

Sometimes it's helpful to document multiple components together. For example, a component library’s ButtonGroup and Button components might not make sense without one another.

DocsPage has the concept of a "primary" component defined by the `component` parameter. It also accepts one or more `subcomponents`.

<!-- prettier-ignore-start -->

<CodeSnippets
  paths={[
    'common/button-group-story-subcomponents.js.mdx',
    'common/button-group-story-subcomponents.ts.mdx'
  ]}
/>

<!-- prettier-ignore-end -->

![Subcomponents in Docs Page](./docspage-subcomponents.png)

Subcomponent `ArgsTables` will show up in a tabbed interface along with the primary component. The tab titles will correspond to the keys of the subcomponents object.

If you want to organize your documentation differently for component groups, we recommend using MDX. It gives you complete control over how it's displayed and supports any configuration.

## Replacing DocsPage

Replace the DocsPage template with your own to customize its contents.

### With null to remove docs

Override the `docs.page` [parameter](../writing-stories/parameters.md) with `null` to remove its contents.

<!-- prettier-ignore-start -->

<CodeSnippets
  paths={[
    'common/button-story-disable-docspage-component.js.mdx',
  ]}
/>

<!-- prettier-ignore-end -->

### With MDX documentation

Write your documentation in MDX and update the `docs.page` [parameter](../writing-stories/parameters.md) to display it. The `id` of reference follows the pattern: `group-subgroup-...--name`, where the `groups` and `subgroups` are defined as according to the [Grouping Documentation](https://storybook.js.org/docs/react/writing-stories/naming-components-and-hierarchy#grouping).

<!-- prettier-ignore-start -->

<CodeSnippets
  paths={[
    'common/custom-docs-page.mdx.mdx',
    'common/button-story-docspage-with-mdx.js.mdx',
  ]}
/>

<!-- prettier-ignore-end -->

### With a custom component

Storybook's UI is built using React. If you want to include a custom component to display documentation, you'll need to update your environment to allow React components to be correctly transpiled.

For example, with Angular start by adding a `babel.config.js` file at the root of the project with the following content:

```js
// babel.config.js

module.exports = function(api) {
  process.env.NODE_ENV === 'development' ? api.cache(false) : api.cache(true);
  const presets = [
    [
      '@babel/preset-env',
      {
        targets: {
          node: 'current',
        },
      },
    ],
    '@babel/preset-typescript',
    '@babel/preset-react',
  ];
  const plugins = [];
  return {
    presets,
    plugins,
  };
};
```

Then, update your `tsconfig.json` to include the following:

```json
{
  "compilerOptions": {
    ....
    "allowJs": true,
    "jsx": "react-jsx",
  },
}
```
Finally write your custom React component and and update the `docs.page` [parameter](../writing-stories/parameters.md) to render the custom documentation.


<!-- prettier-ignore-start -->

<CodeSnippets
  paths={[
    'common/custom-docs-page.js-component.js.mdx',
    'common/custom-docs-page.ts-component.ts.mdx',
    'common/button-story-docspage-with-custom-component.js.mdx',
  ]}
/>

<!-- prettier-ignore-end -->

## Remixing DocsPage using doc blocks

Doc blocks are the basic building blocks of Storybook Docs. DocsPage composes them to provide a reasonable UI documentation experience out of the box.

If you want to make minor customizations to the default DocsPage but don’t want to write your MDX, you can remix DocsPage. That allows you to reorder, add, or omit doc blocks without losing Storybook’s automatic docgen capabilities.

Here's an example of rebuilding DocsPage for the Button component using doc blocks:

<!-- prettier-ignore-start -->

<CodeSnippets
  paths={[
    'common/button-story-remix-docspage.js.mdx',
    'common/button-story-remix-docspage.ts.mdx',
  ]}
/>

<!-- prettier-ignore-end -->

In addition, you can interleave your own components to customize the auto-generated contents of the page or pass in different options to the blocks to customize their appearance. Read more about [Doc Blocks](./doc-blocks.md).

## Story file names

Unless you use a custom [webpack configuration](../configure/webpack.md#extending-storybooks-webpack-config), all of your story files should have the suffix `*.stories.@(j|t)sx?`. For example, "Badge.stories.js" or "Badge.stories.tsx". This tells Storybook and its docs preset to display the docs based on the file contents.

## Inline stories vs. iframe stories

DocsPage displays all the stories of a component on one page. You have the option of rendering those stories inline or in an iframe.

By default, we render React and Vue stories inline. Stories from other supported frameworks will render in an `<iframe>` by default.

The iframe creates a clean separation between your code and Storybook’s UI. But using an iframe has disadvantages. For example, you have to set the height of iframe stories explicitly, or you’ll see a scroll bar. And certain dev tools might not work right.

Render your framework’s stories inline using two docs configuration options in tandem, `inlineStories` and `prepareForInline`.

Setting `inlineStories` to `true` tells Storybook to stop putting your stories in an iframe. The `prepareForInline` accepts a function that transforms story content from your given framework to something React can render (Storybook’s UI is built in React).

Different frameworks will need to approach this in different ways. Angular, for example, might convert its story content into a custom element (you can read about that [here](https://angular.io/guide/elements)).

Here’s an example of how to render Vue stories inline. The following docs config block uses `prepareForInline` and an effect hook provided by [@egoist/vue-to-react](https://github.com/egoist/vue-to-react).

<!-- prettier-ignore-start -->

<CodeSnippets
  paths={[
    'common/storybook-preview-prepareforinline.js.mdx',
  ]}
/>

<!-- prettier-ignore-end -->

With this function, anyone using the docs addon for [@storybook/vue](https://github.com/storybookjs/storybook/tree/master/app/vue) can make their stories render inline, either globally with the inlineStories docs parameter, or on a per-story-basis using the inline prop on the `<Story>` doc block.

If you come up with an elegant and flexible implementation for the `prepareForInline` function for your framework, let us know. We'd love to make it the default configuration to make inline stories more accessible for a larger variety of frameworks!