Skip to content

Latest commit

 

History

History
89 lines (66 loc) · 2.78 KB

Components.md

File metadata and controls

89 lines (66 loc) · 2.78 KB

Locating your components and organizing your style guide

Finding components

By default Styleguidist will search components using this glob pattern: src/components/**/*.{js,jsx,ts,tsx}.

It will pick up files like:

  • src/components/Button.js,
  • src/components/Button/Button.js,
  • src/components/Button/index.js.

But will ignore tests:

  • __tests__ folder,
  • files containing .test.js or .spec.js (or same for .jsx, .ts and .tsx).

If it doesn’t work for you, create a styleguide.config.js file in your project’s root folder and configure the patterns to fit your project structure. For example, if your components look like components/Button/Button.js + components/Button/index.js (meaning you need to skip index.js, otherwise the component will be loaded twice):

module.exports = {
  components: 'src/components/**/[A-Z]*.js'
}

Note: All paths are relative to the config folder.

Note: Use ignore option to exclude some files from the style guide.

Note: Use getComponentPathLine option to change a path you see below a component name.

Sections

Group components into sections or add extra Markdown documents to your style guide.

Each section consists of (all fields are optional):

  • name — section title.
  • content — location of a Markdown file containing the overview content.
  • components — a glob pattern string or a function returning a list of components. The same rules apply as for the root components option.
  • sections — array of subsections (can be nested).
  • description — A small description of this section.
  • ignore — string/array of globs that should not be included in the section.

Configuring a style guide with textual documentation section and a list of components would look like:

module.exports = {
  sections: [
    {
      name: 'Introduction',
      content: 'docs/introduction.md'
    },
    {
      name: 'Documentation',
      sections: [
        {
          name: 'Installation',
          content: 'docs/installation.md',
          description: 'The description for the installation section'
        },
        {
          name: 'Configuration',
          content: 'docs/configuration.md'
        }
      ]
    },
    {
      name: 'UI Components',
      content: 'docs/ui.md',
      components: 'lib/components/ui/*.js'
    }
  ]
}

Limitations

In some cases Styleguidist may not understand your components, see possible solutions.