Flag old GLs versions as old and point to their replacement
Consider injecting some JavaScript to surface a (non-modal) alert noting that older versions of the Guidelines have been superseded and by what.
@raffazizzi I'm not sure I like the idea of a dialog box popup; how about a CSS rule that could add some content to the footer based on something in the footer like:
a.link_ref[href~="4.10.1"]:after{ content: " OLD VERSION"; background-color: pink; }
We could add a new rule to the stylesheet for every release that cycles out of current, and that way we would never actually have to change the pages themselves.
If we did this with pure CSS, it would be a TEI ticket, and would also affect Documentation (TCW22).
I agree. I usually prefer to place this type of warning at the top rather than the footer, though. See https://scholarlyediting.org/se.index.issues.html
It's also unlikely that CSS content will be considered by search engines. Perhaps it doesn't matter, but adding an HTML banner to the existing content would address this
I do think this would likely be better in JS since it’s not something that needs to be part of the actual guidelines, but just as part of the guidelines when they are in the vault and not current.
I think a banner at the top that’s dismissible, which is created on page load iff the page is loaded from the Vault URL?