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 was looking for this to be reproduced anywhere (hopefully in more detail and nicer) but couldn't find it.

I think that whether or not you call it a bug's lifecycle, it's super important to have an outline somewhere of what standard engineering practices are absolutely vital -- among them code review, branching+pull request+code review, passing tests, proper commit messages and reasonable rebasing, and such