Publish to npm

[vesparny]

[mcollina]

This is really important. Also git rid of that checkout, and make it usable with both generators and a module.

You might want to use yeoman, in case check out bespoke.js for insight on how to do that. You might want to do something simpler like building a command system with commist, help-me and generify.

[vesparny]

@mcollina I really like the idea of the yo generator, I'll start tomorrow thanks.

I'd also like to split the monolith app in some semantic npm modules like stated in #13.
Any thought on which is the best way to separate the current structure?

I would also love to give end-user the ability to install themes via npm.
the problem here is that in Morpheus the theme is the hearth of the app logic as for the React's nature, and I'm a bit scared that separate it from the core would lead to have an untestable component.

[mcollina]

I have not enough experience in React to get to the best solution here.
For what it seems, a morpheus theme can only be a CSS thing, like bespoke themes. It is no ideal (others allows to specify HTML), but that's the only option given the scope of the project: in order to hook the handlers on the static HTML, you need to know how the HTML is composed.

You need to take care in how you embed stuff, e.g. a nice usecase for this might be plugging it within another website.

[vesparny]

well, what you are saying is true, but it seems a bit complicated to achieve since react couples logic and templates by nature.
I'll think about it, after having created the yo generator, and published it.
Thanks