Compile .css files in CI rather than checking in compiled files about documenter.jl HOT 1 OPEN

So, I largely disagree with the points above.

• By having users recompile the CSS all the time, we'd be more exposed to attacks against the dependency tree. While that could also affect us here, (1) the attack surface is fixed and much-much smaller, and (2) there is at least some review of the compiled CSS, and the CI check is pretty robust in my opinion.

• Compiling the CSS is not computationally expensive, but you have do deal with additional dependencies. And while Sass.jl would probably be fine as a Documenter dependency nowadays, we may well have to move away from libsass to calling Dart code. (https://sass-lang.com/libsass/ piever/Sass.jl#27)

• One thing I do half-agree on is that the generated files are annoying bloat in the repo, although it's not an issue in practice in my experience. We have a .gitattributes file that declares these files generated, so tooling should take that into account.

  In my mind, the correct way to handle the compiled CSS would be via Artifacts. But I have no clear idea how to manage that end-to-end since, in general, we'd need different artifacts for each commit. We could potentially maintain the theme in a separate repository, but that makes working on any front-end changes quite a bit more annoying.

• One bonus for compiling the theme during makedocs would be that handling custom themes would be slightly easier. But it's also not hard to import DocumenterTools in make.jl if you need that.

from documenter.jl.