All Guidelines Pages should have dropdown menu in footer to go to other versions in the Vault.

TEIC / Stylesheets

TEI XSL Stylesheets

238 stars 126 forks source link

All Guidelines Pages should have dropdown menu in footer to go to other versions in the Vault. #321

Open jamescummings opened 6 years ago

jamescummings commented 6 years ago

In thinking about the TEI Guidelines web pages footer for https://github.com/TEIC/Stylesheets/issues/125 it occurs to me that all Guidelines web pages should have a dropdown menu in the footer allowing a user to jump to a previous version of that page in any of the previous versions. (I would just make this an addition taken from a list of releases rather than testing that this element in particular existed in that previous version.) i.e. a dropdown might list 3.3.0, 3.2.0, 3.1.0, 3.0.0 and if an element was introduced in 3.2.0 then anything I select before that just results in a 404. (That would be fine, it shows quickly what release the element was introduced in.)

raffazizzi commented 6 years ago

F2F subgroup likes this idea a lot. We discussed a couple strategies for implementation, which is not as straight forward as one might think.

Create a persistent structured file that maps past versions and file names of TEI Specs and Guidelines
~~New build will add a new entry to this file using the file on master branch (or Vault?) as the source in order to avoid pollution from dev version numbers.~~ We need a way to update the file with only release numbers, while making available dev version for testing (think of changelog script)
Add a dropdown menu in the build that uses this structured file to figure out what to show for each spec or guidelines page.

jamescummings commented 6 years ago

@jamescummings assigned to look at this when he gets enough round tuits. Low priority. Another option is as an XSLT hackathon or stylesheets group activity.

jamescummings commented 6 years ago

If we do create this persistent list of versions it might help @raffazizzi in being able to automatically produce a list of versions of the TEI to base your TEI P5 ODD starting point in https://github.com/TEIC/romajs

martindholmes commented 1 year ago

I'm going to remove myself from this ticket for the moment because I'm not sure what's required; if it depends on the maintenance of a canonical list of versions which RomaJS can use, then that would seem to be the first thing to do; but there's also the obvious problem that some pages will not have equivalent versions in other released of the Guidelines, and I don't know how this could be known or deduced without a lot of processing.

ebeshero commented 5 months ago

I'm adding @hcayless and @joeytakeda to this ticket as we're working on Guidelines HTML for integration in the new website, and might try working this in to a new footer...