Oct 2019 redesign

[shrubin2]

Cleaned up site, ready for desktop. Still need to make mobile version. I would double check to make sure that buttons go to the right places.

Description of Changes:

How This Was Tested:

Related Issue(s) or Specifications:

Checklist:

• Code follows code style of this project
• Tests added to cover changes
• All new and existing tests passing

Questions / Additional Notes:

[vkoves]

@shrubin2 - can you start by resolving the conflicts? I think you're based off an older version of the site.

[vkoves]

@shrubin2 - are their mocks for what the site should look like? It's hard for me to tell if some of the layout is intentionally the way it is.

Additionally, now that you've merged with master our CI tools have run and found a few failures. Could you take a look at the output from Travis and address those to start?

[vkoves]

Oh, one more note: I'd suggest installing and testing stylelint locally, so you can more quickly iterate on these changes and hopefully get feedback in your editor! Otherwise it'd be pretty time consuming to fix things, push, then wait for Travis until you see if you did everything right or not.

[vkoves]

@shrubin2 - two other notes, since I see Travis is still failing.

1. You can run stylelint with the --fix flag to auto-fix failures. It should catch most of them! Read more here.
2. The CI process runs a file ci.sh, so running that locally (cd into the directory than do ./ci.sh) should help you locally iterate until all the errors are fixed.

Let me know if you have any issues with those!

[vkoves]

Just doing some manual QA, this looks good on desktop overall, but breaks on mobile. Here's a screenshot of the homepage:

Since mobile is currently working right now, I'd rather you fix the responsiveness of your changes in this PR than have this PR and then have to fix up PR #8. How does that sound?