The addon catalog is in beta. Please report any issues you find.
Storybook addons are listed in the catalog and distributed via npm. The catalog is populated by querying npm's registry for Storybook-specific metadata in
Add your addon to the catalog by publishing an npm package that follows these requirements:
package.jsonwith module information and addon metadata
README.mdfile with installation and configuration instructions
/distdirectory containing transpiled ES5 code
preset.jsfile written as an ES5 module at the root level
Get a refresher on how to write a Storybook addon.
We rely on metadata to organize your addon in the catalog. You must add the
storybook-addons as the first keyword, followed by your addon's category. Additional keywords will be used in search and as tags.
|Addon package name||storybook-addon-outline|
|Addon description||Outline all elements with CSS to help with layout placement and alignment|
|Name of the author||winkerVSbecks|
|List of keywords to describe the addon|
Customize your addon's appearance by adding the
storybook property with the following fields.
|Link to custom icon for the addon||https://yoursite.com/outline-icon.png|
|List of unsupported frameworks|
|List of supported frameworks|
package.json above appears like below in the catalog. See an example of a production package.json here.
Once you publish the addon, it will appear in the catalog. There may be a delay between the time you publish your addon and when it's listed in the catalog. If your addon doesn't show up within 24 hours, open an issue.