Tracking all the friction points

[chenglou]

A general issue to track each part that might cause friction in usage. I'll work on each of them. For the more controversial ones I'll submit issues to discuss on solutions.

1. template's README: not directly publishable currently.
2. yeoman's README: way too long.
3. repo has no description.
4. travis not passing.
5. statics: requires knowing how it works, and extra package.json fields.
6. statics-stylesheet: same.
7. stylesheets: bigger overhead: requires knowing the API.
8. Yeoman: sticking with this as soon as generator options are introduced.
9. Browserify: not universal.
10. Jasmine: same.
11. entrypoint.js.
12. current folder structure.
13. trouble with multiple components: no dedupe command yet
14. statics multi-plugins support.
15. uglifyjs fails if it's not globally installed already.
16. workflow with loopholes: npm dedupe and collect-static should be run by watch, but this takes way too long currently.
17. the react-library name: doesn't ring a bell. Confusing since there's also react-quickstart.
18. commands: too many.
19. noisy output.

[petehunt]

One thing we need to do is make statics support multiple plugins. I started refactoring it to support this -- shouldn't be too hard! I imagine future plugins being like image spriting.

[petehunt]

We'll kill react-quickstart and replace it with react-library I think

[petehunt]

This is part of a bunch of smaller modules.

The main goal is that you should be able to run this generator and get a "fill-in-the-blanks" for creating a new React component (testing, example entrypoint, shipping statics etc). React "apps" should just be yet another component. We could have Router components that you npm install to build a big app, and model management etc would just be other installable libs.