Re restore

Based on #10. Can now restore a piece of content. The revision fields and last modified timestamps are updated automatically.

A caveat is that you may find yourself having to modify the required fields in Composer to be able to publish the content again.

The API URL is still hardcoded. Let's have a chat about how to solve that in a way we're happy with.
Left this undone for now as I'm not sure how to the deployment will work yet.

Maybe do require on a config.js file. On deploy we run a script that will copy an environment specific config file to wherever our require() is pointing at, and then run browserify.

Also I'm not sure whether we consider these URLs sensitive or not, as @theefer brought up concerns about. I think it seems odd to rely on security through obscurity. But I'll make no claims to have much IT securitiy expertise either so I'm going to leave that decision to someone else.