You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
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.
The text was updated successfully, but these errors were encountered:
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.
fix_file_extensions.sh
from the build process so that new and old governance versions are visible at/year/XXX/governance/YYYY
/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.The text was updated successfully, but these errors were encountered: