Sorry if this sounds a bit naive. We have done a fair bit of styling, simple stuff but a fair bit to our Discourse theme with custom CSS tweaks etc. Its a hosted plan, every time I make changes to the CSS in the UI it gives me a warning in regards to updates and overwriting.
Is it best practice to set up a GitHub repo and host all the theme files and theme components there to avoid this issue?
Absolutely, it is best practice to keep any sizeable theme on a Git repo. It makes tracking changes easier, using theme creator CLI the workflows are delightful so its even easier to hack on.
I’ve missed that. The cli will, what, see that a change has been pushed to github and reload it? I’ve only seen it push local files to discourse. I just reread the announcement and don’t see anything there about github.
Oh, wow! I just used it for the first time in a while (after I couldn’t make it work for 2 days because I forgot that you have to use a use API key and thought that there was a different problem, but I digress I just edited the topic to tell people that) and WOW it’s crazy-great now.