I thought we were keeping those template CSS for now to help with testing so you don't have to do an npm install everyone you need to test a quick CSS change in a pr.

At least that was my understanding

I see changed files everytime I run npm install on the repo. Either because they are outdated or because my env compiles them different than when it was commited - I don't know. It's confusing. ?

I've asked in the maintainer chat if it is intentional and was told to remove them. So no clue ?

Maybe I misunderstood what @wilsonge said

@Bakual @brianteeman the conversation is about moving or not the sources in build/whatever and me proposing to move also the compiled files in media/whatever.
Maybe one reason that I didn't mention before is that having all the static assets under one folder makes the implementation of a service worker for them a 5 line task...

This is the comment from @wilsonge that has perhaps confused me #21306 (comment)

Not sure why he wants to make that dependant on a decision of where those files live in the end.
Imho we either remove all compiled files from the repo or we don't. But having the compiled template CSS files in the repo while all other compiled CSS files are gone makes no sense to me.

Adding them to .gitignore is really not that hard. It's not like we're talking about 100 files. And once the sources are moved to whatever place, we can probably just .gitignore the templates CSS folder instead of single files like now.

Rebased, solved conflicts and made it more complete.

Rebased again to take care of #21810

Not sure why he wants to make that dependant on a decision of where those files live in the end

I thought we were going to have that conversation almost immediately as everything else was happening. but it never happened. So doing this now is fine i guess.