Make the website less pink

[biped-mathnews]

Is your feature request related to a problem? Please describe.
Right now the website has math pink as the primary colour, but on the main page the site is also coloured based on the cover colour of the latest issue.

This makes it jarring when I click to another page on the site, since everything suddenly changes colour. I don't think most of the possible cover colours go very well with pink.

Describe the solution you'd like
I think the colour of the entire site should be based off of the colour of the latest issue. This will unify the site's design and also look cooler. It will also make it easy to tell when a new issue has been released.

Describe alternatives you've considered
The website could also be all white and black, which will always go with any color, but that isn't as cool.

[tyxchen]

This is an interesting idea that I wouldn't be too opposed to. It would probably require another layer of global state, but we're reaching the point where we really should consolidate all of our providers into a single super-provider. Composition can only go so far before it becomes unwieldy.

For reference, here's our current mockup: https://www.figma.com/file/B36nUhGrIhgE1cE0mcZPCO/Slugline?node-id=0%3A1. Please ignore the individual article page as I'm still working on it, but hopefully this gives an idea of what we expect the general usage of colour to look like.

@ktrieu thoughts on the technical side of things?

[ktrieu]

Sounds like a cool idea design-wise.

The traditional approach would be to handle this with some ThemeProvider type component which we can use in a hook, but we'd have to get the color we fetch from the server into the CSS variable somehow. I don't think having two providers is necessarily a huge problem, theme and authentication don't re-render often enough that I'm concerned about performance. If we want dark mode, a ThemeProvider would probably be a good idea anyway.

My other idea is serving a CSS file from the server, with the CSS variable filled in. This gets rid of the need for the ThemeProvider, but it's another request, and we'd probably have to directly include it via a <link> tag, since our SCSS gets compiled to a huge blob.

[tyxchen]

@biped-mathnews I've pushed some relevant changes to the implement-issues branch --- do you mind checking it out and letting me know what your thoughts are?