The problem is that to do so we're hardcoding the paths and that is why I proposed that the css files of the templates should be on a folder in the media folder

And the hardcoding of paths (for what I'm not clear exactly) is an issue why? Do realize a fair number of us don't only git clone this repo for contributing to core, we also work on our own projects using this local installation. Already running the build tools on 4.0 I have seen occasional warnings about some of the directories I have symlinked to other projects, our tool suite shouldn't be over eager here and be trying to process files it isn't designed to work with.

our tool suite shouldn't be over eager here and be trying to process files it isn't designed to work with

I can work around this, np. The whole idea, though, with the separation of source and distribution is something that we need asap because right now the repo is marking a bazillion of compiled/minified files which is extremely inconvenient for anyone that wants to contribute. We should care only for the sources all the compiled/transpiled and minified files shouldn't exist in the repo. I hope we all agree on that

Tried to test but got a syntax error:

SyntaxError: ./media/plg_system_stats/js/stats-message.es6.js: Unexpected token (5:9)

I would probably put the files into /build/media or /build/media-source/ to avoid having another root folder. This way it's also clear for anyone that this folder isn't in the distributed CMS.

Please remove the index.html files. I don't think there is a reason for those.

Please remove the index.html files. I don't think there is a reason for those.

I will once I have a step to create the missing folders per template.

I would probably put the files into /build/media or /build/media-source/

Also, I don't mind using the build folder. We already have plenty of code in there

I will once I have a step to create the missing folders per template.

Does JS not generate path automatically if you create a file?

I don't mind using the build folder. We already have plenty of code in there

Isn't that the purpose of that folder? To hold everything related to build a release? ?

Maybe it's just me but every time I see an acronym written in capital case it hurts my eyes

eg
compileJs ==> compileJS
compileCss ==>compileCSS
compileCe ==> compileCE

@dgrammatiko Can you take care of the syntax error so this can be tested?
And of course throw a bone to hound so he is satisified.

Maybe it's just me but every time I see an acronym written in capital case it hurts my eyes

@brianteeman this cannot be done the reason is that this line:

if (Program.compileJs) {

translates to --compile-js. I'm sorry for your eyes, but there is nothing I can do about it.

If there is an agreement on moving the assets to a common folder I'll redo this PR. For now separation of sources from the distributable media folder is way more important