feature request: override CSS from config about etch

[LukasJoswiak]

Hi, thanks for opening an issue. I've been thinking about this for a while, but I'm not sure I'm convinced of how necessary it is. This seems like (as you mentioned) what forking is meant to do. Forks can be kept up to date with the upstream repository as well. A more lightweight alternative to forking is to just modify the CSS in the theme after adding it as a submodule.

I did look into implementing this. Currently, the CSS files in assets/css/ are combined into a single file and minified. The goal is to keep the number of network requests down (it can be argued whether this is a worthwhile goal). Anyway, it appears that resources.Get can only read files from the assets folder within the theme folder and not from within the user's website folder. This means it would be necessary to make extra network requests for each user defined stylesheet. Since I'm not yet convinced how necessary this feature is in the first place I'm hesitant to go ahead with implementing it. I'm happy to keep discussion open though.

[burtonr]

I agree, this would be a great feature. 👍

[LukasJoswiak]

It's been a while and I still think forking is the way to go for changes, so I'm going to close this issue.