Investigate SASS/LESS about suse-xsl HOT 2 CLOSED

Why close this? Using SASS or LESS would seem like a good enhancement. Especially, if we want to keep multiple documentation brandings around (SUSE, OpenSUSE, DAPS).

Preprocessors in General

Pro

• Additional features such as variables, loops, nesting structures that make writing/maintaining CSS more of a pleasure, less of a mess

Con

• May make debugging a bit harder (though using a .map file should be possible -- need to investigate)
• Nesting features may lead stylesheet authors to write longer selectors that perform worse (though that can obviously be mitigated)
• Additional step/dependencies before you get output (however, since the stylesheets now have a make process of their own anyway, this point is moot)

LESS

Pro

• CSS-compatible -> we could start using it by adding a preprocessor, and then go from there
• Great documentation

Con

• Syntax is more error-prone than SASS's
• A little less powerful
• Dependence on NPM-installed packages [there is also python-lesscpy; but if we're adding packages from NPM, autoprefixer is pretty darn great too]

SASS/SCSS

Pro

• More Python-like syntax (no brackets, no semicolons) -- makes it easier to work
• Available as an RPM-packaged Ruby Gem

Con

• Can't start using it right away, as the syntax is different from CSS
• Much less great documentation

from suse-xsl.

This is already in place for the suse2022-ns variant.

from suse-xsl.