Skip to content
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

Open
zarino opened this issue Apr 2, 2024 · 2 comments
Open

Create 2025 Scorecards “site” #645

zarino opened this issue Apr 2, 2024 · 2 comments

Comments

@zarino
Copy link
Member

zarino commented Apr 2, 2024

Last year, we moved the 2022 Plan Scorecards into the scoring2022 Django app, and created a new scoring app for future ("Action") Scorecards years.

This year we probably want to extend the scoring app, with a second year of Action Scorecards.

@zarino
Copy link
Member Author

zarino commented May 3, 2024

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:

Content Current path New path
2023 methodology /methodology/ /2023/methodology/
2025 "updated" methodology /methodology/

But eventually, all the URLs will change:

Content Current path New path
2023 homepage / /2023/
2023 methodology /methodology/ /2023/methodology/
2023 about page /about/ /2023/about/
2023 council pages /councils/:slug/ /2023/councils/:slug/
etc… /…/ /2023/…/
2025 homepage /
2025 "updated" methodology /methodology/
2025 about page /about/
2025 council pages /councils/:slug/
etc… /…/

@struan
Copy link
Member

struan commented May 7, 2024

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.

@struan struan closed this as completed May 7, 2024
@struan struan reopened this May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants