Backbone begins

[ricardobeat]

This builds on @tgriesser's work on #87, but restricting changes to the blog view. It's a huge patch even so, but I think it merges cleanly, and keeps all existing features in a working state.

I tried to be conservative about the implementation, so not everything is done _the true backbone way_™ until other pieces fall into place (routing, collections & state management, etc).

[ricardobeat]

After (if) this is merged I'll get onto the other views, one by one, so that parallel work isn't disrupted.

[ricardobeat]

@jgable good point on Collection::fetch(), will update PR.

[ricardobeat]

I'm not getting any errors from grunt validate in the vagrant box: http://cl.ly/image/2b1c0q3K0T29 :(

[ErisDS]

You should be able to login and see the errors from travis, by first logging in at magnum-ci.travis.com.

Travis is timing out. Probably doesn't mean anything. You should be able to restart builds that look like they shouldn't have failed?

[ErisDS]

I tried out squashing the commits of a pull request, which means this has my name next to it and didn't auto-close the PR. Not sure if that was a good or bad idea, just want to start getting a much cleaner history.

[ricardobeat]

I had already squashed this as two commits (add dependencies, then implement) for easy reversal. GH probably only auto-closes the PR if the commit hashes match. Looks good anyway, working on the settings page now.

edit: you can ask the author to do the squashing to preserve authorship, then rebase & merge

[ricardobeat]

and thanks for the travis tip, now I can finally see why the build fails 🤘

grunt validate is breaking on v0.8, maybe we should remove it since v0.12 is near

[tgriesser]

I think the two commits might make more sense for having clean history here, since one only had the lib additions and the other the relevant code.