Pubsite Rewrite 2019 -- Jekyll this time!

[RamZallan]

🎉 🚢 🚀

View it live at pubsite.a.csh.rit.edu!

Here's a few previews, as well:

Closes #168
Closes #178
Closes #179
Closes #198

[rswiernik]

You might have already thought about this but since this PR is G R A N D E, it's probably worth squashing out commits so this is a nice clean cut over that can be easily tagged.

[RamZallan]

@rswiernik would it make sense to just Squash + Merge? There's a few merge commits in the PR and some history was lost anyways moving between repos (originally on CSHPublicSiteV2, then my fork of this repo).

[rswiernik]

I'm not sure that preserving the history for the dev of new versions of the site is really that important. If really wanted to, you could merge it into a separate historical branch on this repo, then merge that branch to master, squash the master history, then force push the new master history?

eg:

... Do some shit to get the history set up ...
[Reeds-MBP] tmp ❯ git checkout history                               (master|✔)
Switched to branch 'history'
[Reeds-MBP] tmp ❯ tree                                              (history|✔)
.
├── a
├── asdf
├── that
└── this

0 directories, 4 files
[Reeds-MBP] tmp ❯ git checkout master                                                                                         (history|✔)
Switched to branch 'master'
[Reeds-MBP] tmp ❯ git merge --squash history                                                                                   (master|✔)
Updating 72cf0f4..8dff9e0
Fast-forward
Squash commit -- not updating HEAD
 a    | 0
 asdf | 0
 that | 0
 3 files changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 a
 create mode 100644 asdf
 create mode 100644 that
[Reeds-MBP] tmp ❯ git log                                                                                                     (master|●3)
commit 72cf0f454d727369384043c5073146c6a8b7651d (HEAD -> master)
Author: Reed Swiernik <reed@plum.wine>
Date:   Wed Aug 7 15:36:33 2019 -0700

    first
[Reeds-MBP] tmp ❯ git status                                                                                                  (master|●3)
On branch master
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

	new file:   a
	new file:   asdf
	new file:   that

[Reeds-MBP] tmp ❯ git commit -a -m "Update to new version"                                                                    (master|●3)
[master a898d3e] Update to new version
 3 files changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 a
 create mode 100644 asdf
 create mode 100644 that

[rswiernik]

All that said, I would definitely prioritize having a single clean commit on master. But that's just me.

[rswiernik]

Also, obligatory mention, this is your time to sneakily change the organization colors back to green/white/black. Just making sure that you have all the information you need before you merge this ;)

[RamZallan]

Fixes #168 #178 #179 #198

[devinmatte]

I'm happy to see this merged!

Please make sure that whoever merges this Squash and Merge when clicking.
After merged @RamZallan please switch the openshift project and webhooks to track from this project instead of your fork.

Also please tag the new commit with a version tag 😄