Custom Style Backend with simple CSS

[innosmith]

Analogous to custom styles in the frontend, it would be great to be able to configure the appearance of the admin backend using CSS.

This would make it easy to hide unused attributes, for example, or to implement help instructions for admins more visually. This leads to fewer support cases and a better user experience for admins.

Thanks to Decidim Awesome, this would become possible and Tenant-specific.

[microstudi]

This would be nice, I'd add that Awesome itself shouldn't be modifiable to avoid any mistake that prevents removing any unwanted side effect (like hiding something unintended).
Another option would be to add some minimal button in a corner to deactivate custom styles momentarily in case of "emergency".

Do you think you can collaborate on this one?

[innosmith]

Some of the backend uses case we're thinking of:

• making the assembly or participatory process page clearer by removing some attributes just by CSS-hiding
• first time admins have to accept the admin terms and conditions first before they can start. On first login it looks like everything is fine because the background color suggests so. Instead admins have to first find the link to read the admin terms and conditions and then accept.
• Pages to configure Awesome and other platform admin interfaces may remain untouched by this extension request. We're looking to improve admin pages for participatory spaces, often managed by admins with lower rights than platform admins.
• In general the backend color theme and fonts could be individually changed to better represent the topic of a decidim tenant

Regarding collaboration: how much dev power and/or funding do you think of? Then I can check to find supporters.

[microstudi]

Thanks, it would be "awesome" if you could found ways to collaborate either financially or dev-wise. We are currently working on our dev planning and will contact you soon.

[larsUE]

@innosmith FYI this is a duplicate of #333, which i believe is being implemented! 🚀

[paarals]

@innosmith FYI this is a duplicate of #333, which i believe is being implemented! 🚀

ou, you are right! :)