-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create 2025 Scorecards “site” #645
Comments
In terms of URLs, we’ll be continuing the convention we started last year, where the latest content is always available at the year-less paths, while older content has the year in it. So, we’ll have a "transitional" period, where only the new ("updated") Methodology has been published, and that’ll require us to change only two URLs:
But eventually, all the URLs will change:
|
The methodology one is the only complicated one as it's going against all the other ones in that it does not always load the default methodology year. However, I can resolve this by adding in a setting I think which is the simplest option. |
This is all done for the scores side in that appending the year to the URL will load the scores etc for that year. Need to update PLAN_YEAR in settings to 2025 to set the default. Will need some work to handle the "static" pages but this should be doable by creating a 2025 and 2023 directory in templates and then putting a copy of each into there and then I guess create a mixin to load a template based on the view year. And then some slightly tweaking of the url file. It might be that only the about page needs this in which case can just do this directly there. FWIW, the methodology page already handles the year. |
Last year, we moved the 2022 Plan Scorecards into the
scoring2022
Django app, and created a newscoring
app for future ("Action") Scorecards years.This year we probably want to extend the
scoring
app, with a second year of Action Scorecards.The text was updated successfully, but these errors were encountered: