Rebuilt Documentation in Gitbook

[AlinaWithAFace]

You can see the results here, but basically I rebuilt all of the documentation to work with gitbook since it's a bit more user-friendly compared to READMEs scattered throughout folders.

[jselstad]

Wow, this looks great! Gitbook is a huge visual upgrade over the standard Github readmes.

A couple questions:

• Is this missing a book.json?
• How is ownership of the pages managed with respect to gitbook.io? My current impression is that we'll need to initialize a separate Gitbook.io instance from your staging deployment.

Once the pieces below and the merge conflicts are fixed (and @fmaurer approves), I see no reason not to merge this.

[AlinaWithAFace]

I've only been working with gitbook for the past month or so using their webapp client, so admittedly I don't know if it's missing a book.json or not, or what it would look like.
They apparently use some sort of teams system, again via their webapp. I'd be happy to add leap motion staff to what I've already set up if you'd like to keep the domains (I'd need emails!), or you should be able to connect another instance via their github integration.