Make release cycle charts reusable
Right now, the release cycle SVGs are monochrome when viewed as standalone images:
This is because all the colours are defined in the website's own .css file.
This PR moves the colours into the SVG files themselves, except for the theme-aware overrides using things like --color-foreground-primary from Furo, needed for dark/light mode support.
Also serve these images, so we can display them on https://www.python.org/downloads/ where our end users visit, and not just in the CPython developer's guide. Re: https://endoflife.date/recommendations#bad---python
Needed for PR: pythondotorg#2837
📚 Documentation preview 📚: https://cpython-devguide--1708.org.readthedocs.build/
Would it make sense to provide light, dark, and “responsive” variants? More generally: is this just for python.org, or do we want others to easily reuse this?
If we decide that serving 3×2 static images, rather than 2, is worth it, I'd prefer doing the related changes myself -- I can clean up and adjust the CSS while doing that.
Right now this is just for python.org which only has a light theme.
No objections to making more variants in the future, and I'm happy for you to do it.
What would a "responsive" variant be? The SVG is already, well, scalable :)
What would a "responsive" variant be? The SVG is already, well, scalable :)
Responding to the user's light/dark preference :)
I've sent my suggestions here: https://github.com/hugovk/devguide/pull/36
Any further comments?