Move `addon-info` into addons panel

[shilman]

Why

Currently addon-info shows component info in the preview pane alongside each story. This behavior differs from typical addons, that display their info in the addons panel.

Modifying the behavior to use the addons panel would make the addon available for react-native. It also means that addon-info can benefit from addon panel UI improvements in future versions of storybook-ui.

EDIT: It would also make the addon compatible with storyshots

What

• modify the info addon to use the addons panel
• update docs

[mthuret]

Maybe it would be better to split the addon-info features to be displayed in different panel? One for the description, one for the source, one for the propTypes? What do you think?

[Gongreg]

If you are thinking about splitting it into separate panels it starts to sound like separate addons which already exist.
There are propTypes addon, description addon, source addon.

[bigassdragon]

@shilman is this a new addon?

[shilman]

@bigassdragon i'm proposing modifying the existing addon, but it could also be a separate addon. it seems like there are a bunch of addons that do similar things in this space, so it would be nice (i think!?) to consolidate and remove duplication of work...

[bigassdragon]

@shilman is there a link to the existing addon we are talking about?

I tried looking for it but I have never seen or heard of addon-panel, I would not mind having any kind of merge just need to know what it would look like and if we can make and even more awesome addon that could incorporate a lot of slick things to make documentation better.

[shilman]

@bigassdragon sorry for the confusion. hopefully this clarifies?

[bigassdragon]

@shilman OOOOHHHHHHH. I definitely get it now. yeah I use those.

However I thought there was an addon that already does a panel view of the documentation.

I think you might be trying to do something like this: https://github.com/mihalik/storybook-addon-markdown

However the difference is it would use the addon-info plugin so you do not need to create a bunch of markdown files.

Is that correct?

[shilman]

@bigassdragon AFAIK:

• addon-info looks at proptypes etc. to create an API description semi-automatically
• addon-markdown accepts generalized markdown?

I think this should all be simpler, cleaner, and compatible with the rest of the plugins.