Make release cycle charts reusable#1708
Merged
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

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
.cssfile.This PR moves the colours into the SVG files themselves, except for the theme-aware overrides using things like
--color-foreground-primaryfrom 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/