Docs

[Raynos]

• explain input/state/update/render
• explain modules
• explain how it does things
• compare to other frameworks
• demonstrate that you can swap things out because of modularity
• demonstrate opinion is optional.

[kuraga]

It would be good to make a docs Contents...

[Raynos]

These still need doing.

• We need to document how mercury actually works, although the lifecycle documentation is a start.
• We have demonstrated that things can be swapped out with the unidirectional demos.
• We need to document that various pieces of opinion in mercury are optional and that it's flexible and allows you to build your own tooling. I know @neonstalwart @kumavis @staltz have effectively been able to customize mercury to work the way they want it to work.

[elnygren]

Didn't want to start a new issue as this is a pretty minor thing I just noticed when stumbling upon JS frameworks:

"mercury is compact, it's 11kb min.gzip.js, that's smaller than backbone."
http://backbonejs.org/ -> 1.1.2 is 6.5kb min/gzip.

[Raynos]

@elnygren I included the size of underscore in backbone; underscore+backbone is more then 6.5kb;

mercury has a ton of dependencies and they all fit in 11kb.