building.gittip.com

This is the start of a new site aimed at people building Gittip. It's supposed to be a one-stop shop for designers, developers, marketers, etc., both newcomers and veterans. Here's what it looks like so far:

![building-gittip](https://f.cloud.github.com/assets/134455/2056091/469cf710-8ad2-11e3-8efa-4e712d12d80e.png)

Building Gittip is implemented as an additional Aspen site in the main repo, under `building.gittip.com`. I included it in the main repo to make it easier to do literate programming, where we write documentation inline as much as possible and pull that out and present it in a unified way on http://building.gittip.com/. I propose we adopt this practice where possible to make it easier to keep documentation in sync with reality.

Having building.gittip.com in the main repo makes it harder to configure hosting, because Heroku (and Dokku) are designed to serve a single site out of a single git repo. We already have gttp.co and Gittip-Everywhere as separate repos that should properly be included in the documentation on building.gittip.com, so maybe it makes sense after all to put building.gittip.com in a separate repo.

The problem with multiple repos is that it's potentially more complicated to get started hacking on Gittip. What repo do I start with? Where do I report issues? To help with that, we could have a master meta-repo named `gittip` that has all of the other repos as [submodules](http://git-scm.com/book/en/Git-Tools-Submodules) and doesn't use GitHub issues. We would document this in our quick-start guide that we'll put up on building.gittip.com. :-)