Integrate Code for San Francisco assets, update to bootstrap 3 and jekyllize website

Found some spare time this weekend to begin playing with an integration of a couple of things around the projects/people page forked here. I don't know if it was the intention for this to become the SFBrigades v2 project/people tracker, but I thought I'd play around. Here's what it looks like online: http://jasonlally.com/labplc_projects_page/

- I started with the core labplc_projects_page repo and layered in Jekyll Liquid templates to make maintaining the site a little easier over time. 

- I pulled the projects and people pages into subdirectories to give them cleaner urls without the .html (that's mostly a style choice). So now /projects.html is just /projects

- I moved the custom js for projects and people into separate files (projects.js and people.js) and put them in the js folder. I also added a little Liquid logic to pull custom script files out of an array into the footer of the default template.

- I updated the people.js to merge stats across single users so that a user with multiple project contibutions would only show up once instead of multiple times (the code's a little messy, lots of loops, but it works)

- I cleaned up the homepage a little by merging code from both KC brigade and the Open Gov hack night, upgrading to Bootstrap 3. I kept copy that made sense to keep from the original site, but didn't intend these copy choices to be final. I imagine needing a lot of edits on these.

- I made minor copy edits and changes, but didn't focus here

The intention of this PR is to get us kickstarted on refreshing our online presence. There's still much to do here, but hopefully this is a good start and most of the basic infrastructure is in place to make iterations on design and features pretty quick.

I checked with Maya whether this made sense, but let me know if there are problems integrating these changes here and starting to build off of this repo for v2 of the Brigade website.

For this PR, I focused mostly on making infrastructural choices that will hopefully help the website refresh move forward, I did not focus on design or content choices, so please do not consider this a statement on how the final thing should look.

A couple of issues to consider:
- The projects page is great as an MVP, but could we get something with a bit more detail on updates and status changes. This is something Philly does really well. We can probably accomplish something like this through Jekyll posts or maybe even through Github issues. It would be great to do something quick and easy that wouldn't require separate hosting.
- The people page is great for leveraging the API, but a lot of the people highlighted are in other Brigades because we're forking their projects, maybe that's okay? But maybe we want to at least have some more curation around this as well, especially for the leadership team or others that choose not to contribute via github?
- Events is not built out. Lots of ways to do this, but it would be great to even just embed a calendar and have the community team keep that up to date as a start? Chicago reads from a google spreadsheet I believe.
- There's still no way to surface emerging projects or pain points (things without github repos). Can we do that, through simple Jekyll posts that project owners keep up to date, or is that too technical? Maybe a google form? Is there a combination of workflow and technology that could do for now? e.g. project lead posts to form, delivery lead updates website each week?
- And more, I'm sure...

@ondrae, what do you think?