Outdated CSS for released Guidelines

[rettinghaus]

There is a problem with released Guidelines and the used CSS files:

The CSS that comes with the MEI repo are needed for local builds, but these files interfere with the online versions of the music-encoding website. All changes we make to the header or the CSS for the main site, we need to migrate to the MEI repo, so these tend to be out of sync. Furthermore, the released versions

• https://music-encoding.org/guidelines/v4
• https://music-encoding.org/guidelines/v5

reference their own, outdated versions of the CSS files, which results in the scoial icons not being white.

Is there a way we can split the CSS rules to use a global file for all those things (like header etc.)?

[bwbohl]

Yeah, that’s something that’s been irritating me for quite a while, too!

Also, I’m not completely sure why the mei-screen.css in music-encoding/music-encoding includes additional rules that aren't maintained here?

What about

1. referencing https://music-encoding.org/css/main.css from utils/guidelines_xslt/odd2html/htmlFile.xsl instead of maintaining a separate version there? The only drawback would be the need to be online for local builds to look good. Alternatively, we could download it via an Ant task, right?

2. Separating the styles to a own repository and then either including them as a submodule or publishing them separately?

3. Define all styles here, publish them as a separate package here?

[bwbohl]

And about separating the css files is doable in the SASS setup. This is for example also done with bib.css vs mei.css, cf https://github.com/music-encoding/music-encoding.github.io/tree/main/_sass

(Also worth a look: https://github.com/jekyll/jekyll-sass-converter/tree/master/docs)