Prep for first release

Made some metadata changes to the project to prep for first release. @pushred At one point, you had made a comment about adding Sparkart info in the package.json, but I'm not sure what field(s) to add that in.

Since this is my first time releasing, I'm figuring out the process as I go;

Bower: http://bower.io/docs/creating-packages/#register

npm: https://gist.github.com/coolaj86/1318304

GitHub: https://help.github.com/articles/creating-releases/
Thoughts on namespacing these with `blocks-`? On the one hand they're pretty neutral in their implementation, mostly free of dependencies (for now). They're useful standalone. But they'll consistently follow certain conventions and through that be very interoperable. That's pretty similar to [SUIT](http://suitcss.github.io), which follows a `[suitcss-](https://www.npmjs.org/search?q=suitcss-)` prefix. You could say gulp plugins are [really just that too][1], modules that are plugins by following specified conventions. They similarly share the `gulp-` namespace so that others can more easily find them. There's [some talk][2] of formalizing all this in npm at least.

If we don't namespace we'll eventually be forced into some awkward names to avoid conflicts in either of the registries.

[1]: https://github.com/gulpjs/gulp/blob/master/docs/writing-a-plugin/guidelines.md
[2]: https://github.com/npm/newww/issues/106