Redirect all of our website content to HTTPS #211
Description
As part of our HTTPS efforts, we should redirect all of our website content to HTTPS (documentation, etc). We're already doing this for the important pieces (like the signup form), but we should do this for all our website content too. Redirecting our webpage content to HTTPS doesn't have nearly the ramifications as redirecting APIs, so this should be a pretty safe and easy thing to do.
I think the only thing we might need to verify are some of the Swagger docs we're hosting, since I remember there were some oddities with Swagger on mixed HTTP/HTTPS pages (which should actually be simplified by just forcing everything to HTTPS).