right now we are telling people to vendor the css templates and have them manually update them, maybe we should mention git submodules in the readme as an alternative to make it easier to update all the templates?
if we do switch it over it would also be nice to have valid-ish paths in the example config. all of mine have looked like ./templates/colors-whatever.css. im thinking of having like an officially endorsed directory structure that all the example configs use. should this filed into be another issue?
using git submodules would also be a nice way to get more contributions as changes inside the submodule will already be in a git tree (some github cli commands are still needed to make it into a fork and setup the git remotes etc).
right now we are telling people to vendor the css templates and have them manually update them, maybe we should mention git submodules in the readme as an alternative to make it easier to update all the templates?
if we do switch it over it would also be nice to have valid-ish paths in the example config. all of mine have looked like
./templates/colors-whatever.css. im thinking of having like an officially endorsed directory structure that all the example configs use. should this filed into be another issue?using git submodules would also be a nice way to get more contributions as changes inside the submodule will already be in a git tree (some github cli commands are still needed to make it into a fork and setup the git remotes etc).