Auto-load addons

[ndelangen]

We could load all addons we know @storybook/addon-** and the community developed ones storybook-addon-** by reading the package.json.

[tmeasday]

I think "automagic" like this hurts more than it helps. People don't really understand how it works and so when they have problems they don't have any clue how to fix them.

It doesn't seem worth it to save a one line import '@kadira/storybook-addon-notes/register'; (etc)

[usulpro]

In general I like the idea of lowering the barrier to entry. Take a look at storybook-addon-material-ui. It's more Material-UI tool then Storybook, and people coming from there maybe never use Storybook before. So making their life easier is make sense for me.

On the other hand, in addition to registering the addon, we need some templates. That's why I'd like to have some API like $ getstorybook storybook-template-material-ui

[ndelangen]

@usulpro Can you make a note about templates on this issue: #1108

@tmeasday Do you recommend we do not do this?

[tmeasday]

That is my recommendation, yes. Not so wedded to it that I would complain if we wanted to go another way, but this is based on my experience with other OSS projects.

[shilman]

Definitely with @tmeasday on this one, and for the same reasons (cough, Meteor, cough)