New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ability to edit skin colors #3886
Comments
You can easily override css from the admin panel. I'm not against this feature, but would it really be used over easily changing css? |
That's true, but it would be easier with like a color picker, and recently/commonly used colors. |
Admins like me would use this feature. I can edit css. I really, really, do not want to. |
A dedicated skinning manager may be completely out of scope (plugin request?) But what if core had the ability to modify a given bootstrap skin's |
The problem with the global css changes is that it plays havok with different skins. I would like to be able to create a new skin, ideally based off an existing one so updates would automatically apply. For example, the default theme may use Cyborg + a background image. But if the user selects a different theme, the background image should not apply because it would look terrible. |
@sunsetbrew this commit NodeBB/nodebb-theme-persona@9476854 will help you do that. this adds a class to the body tag named after the skin used so you can apply updates specific to the skin. |
Ooo, that is awesome. So we will see in the next update. :) |
I think the change @pichalite did + ACP custom CSS panel is good enough |
I think it would be cool, but might take a little bit, if you made it so that admins could make custom skins by just changing the colors, and setting if it is a round or square skin, so like the Cerulean skin VS. the Cosmo theme. I know its asking for a bit much, but I think it would look cool. I want a blue based skin(with the background blue, and the navbar blue), but I noticed that it is just Bootwrap skins, so I think this would be a very cool addition.
The text was updated successfully, but these errors were encountered: