Overhaul

Build available at: http://webdev-bootcamp-osmose.readthedocs.org/en/overhaul/

So I decided to take a stab at reorganizing the bootcamp. I ended up splitting the thing into two sections:

1. The Guide, which is an ordered guide to the basics of getting set up as a new contributor/employee to Webdev.
2. The Reference, which is a sort've dumping ground for useful info on topics that people commonly ask questions about.

In particular, I tried to omit any information that was likely to become out-of-date at some point. This meant losing some otherwise useful info, like setting up localization for a new project. I'm not sure if the Bootcamp is the right place for that information anyway, as anyone made responsible for that should, in theory, be equipped with the ability to find that information for themselves.

I also tried to stay away from information that varies a lot between projects, unless it was really important. Some of the things I mention as being in a project's documentation commonly aren't, but I think that's a problem with the project's documentation rather than with the bootcamp.

This is the result of my first pass. I'm still reviewing this and thinking about it myself, but I figured some early feedback would be useful. As long as you keep that in mind, feedback is quite welcome!
I think this idea is covered by "Indenting code should be done in one of two ways: a hanging indent, or 4 space indent on the next line."

Also having to re-indent I don't think is the compelling reason here anyway. In that situation I'd actually go with:

```python
result = django.test.RequestFactory().get(
    '/page', parameter1=1, parameter2=2)
```

To be fair, while I've used that style for a while I've never put the reasons into words, so feel free to say "Osmose you're making stuff up now", but I prefer it because:

- The parameters aren't complex enough to warrant splitting them between lines.
- Keeping the line compact instead of spreading among lines helps indicate that only a single action is being taken here; `get` isn't all that complex, which is reflected by how simple it's arguments are.
- If a more compact and equally readable alternative is available, I prefer it because code that's spread out too much is as unreadable as code that is squished together.

Thoughts?