You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been theming Firefox for a number of years and it has always been so tedious to attempt to navigate and try out new themes by manually editing, moving around files within an obscure profile directory.
For a long while, I've been hoping that someone would write a theme manager the same way that Spotify has spicetify. Mozilla missed the ball with .xpi extensions but maybe there's hope (though it will likely be limited to what Mozilla allows tinkering with).
My suggestion (though this is a big one) would be to integrate a CLI manager within the FirefoxCSS Store - the closest, I've seen is nyoom. It has the ability to accept git repository as sources and it's being actively developed.
If you were to fully integrate a CLI manager as the de-facto installation method for any theme within the store, you could just have user's copy a single CLI command to install the previewed theme from the store which would allow them to try out the theme without having to go through the tedious manual download and installation steps from each repository.
This would also mean you could enforce some standard formatting of the repo that would be detectable by nyoom before that theme is accepted into the store (and you could likely setup a GitHub Action to test each repo to make sure it installed properly).
cc: @ryanccn (I hope you're not bothered by this mention 😅)
The text was updated successfully, but these errors were encountered:
I've been theming Firefox for a number of years and it has always been so tedious to attempt to navigate and try out new themes by manually editing, moving around files within an obscure profile directory.
For a long while, I've been hoping that someone would write a theme manager the same way that Spotify has spicetify. Mozilla missed the ball with .xpi extensions but maybe there's hope (though it will likely be limited to what Mozilla allows tinkering with).
My suggestion (though this is a big one) would be to integrate a CLI manager within the FirefoxCSS Store - the closest, I've seen is nyoom. It has the ability to accept git repository as sources and it's being actively developed.
If you were to fully integrate a CLI manager as the de-facto installation method for any theme within the store, you could just have user's copy a single CLI command to install the previewed theme from the store which would allow them to try out the theme without having to go through the tedious manual download and installation steps from each repository.
This would also mean you could enforce some standard formatting of the repo that would be detectable by nyoom before that theme is accepted into the store (and you could likely setup a GitHub Action to test each repo to make sure it installed properly).
cc: @ryanccn (I hope you're not bothered by this mention 😅)
The text was updated successfully, but these errors were encountered: