music-encoding / schema

A repository where the MEI schema are published
6 stars 5 forks source link

GitHub page https://music-encoding.org/schema/ vs https://music-encoding.org/resources/schemas.html #2

Open bwbohl opened 3 years ago

bwbohl commented 3 years ago

https://music-encoding.org/resources/schemas.html is ok as first entry point although it could bear some more info on the schemata and it lacks links to older versions. https://music-encoding.org/schema/ on the other hand is a pretty ugly website that bears almost no contents, except for the short readme of this repository. I see two options here:

  1. redirect https://music-encoding.org/resources/schemas.html to https://music-encoding.org/schema/ and prettify what's found here
  2. redirect the other way round and offer a more complete link list on https://music-encoding.org/resources/schemas.html

While 2. might be easier to integrate with the website look and feel it would probably destroy the possibility to access the schemata directly for validation, e.g. by calling https://music-encoding.org/schema/4.0.1/mei-all.rng (and I like this ;-)

Opinions?

lpugin commented 3 years ago

I think that 2. would be very problematic. Not breaking validation was the reason to have the schema repository

rettinghaus commented 5 months ago

So here should be an index.html here that looks something like this:

<head>
     <meta http-equiv="Refresh" content="0;url=https://music-encoding.org/resources/schemas.html">
 </head>
 <body>
 </body>

How do we integrate it into the CI?

bwbohl commented 5 months ago

As I was instead thinking the other way round, I created a test deployment in my fork. I copied the contents of schemas.html and added some dynamic to automatically list the contents of the respective version folders in a Jekyll/GitHub page. It still needs the proper MEI styling, and maybe using https://github.com/jayanta525/github-pages-directory-listing could even improve its appearance. But as a dummy test, it’s OK: https://bwbohl.github.io/schema/