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

Move governance to yearly path #1420

Open
dylancashman opened this issue Jan 24, 2022 · 0 comments
Open

Move governance to yearly path #1420

dylancashman opened this issue Jan 24, 2022 · 0 comments
Assignees

Comments

@dylancashman
Copy link
Collaborator

There is a script in the build process that moves the current year's governance to the root governance folder.

https://github.com/ieee-vgtc/ieeevis.org/blob/vis2022/scripts/fix_file_extensions.sh

Looking at the commit history, this seems to date from about 2017 and may have been done so that only the current governance pages would be visible on the site. Moving forward, we've gotten requests to move some of these government pages to a yearly basis, so that new versions could be on the main website but previous versions could be used.

  1. Get rid of the fix_file_extensions.sh from the build process so that new and old governance versions are visible at /year/XXX/governance/YYYY
  2. Add in some forwarding or redirects so that any old links to /governance/YYYY get redirected to /year/CURRENT_YEAR/governance/YYYY. I'm not too sure what the best way to do this is, you might have to do some rooting around. Maybe there's a jekyll way that will automatically create some meta-redirect file in the build process.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants