https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37054 --- Comment #55 from Jonathan Druart <jonathan.druart@gmail.com> --- (In reply to David Cook from comment #54)
So then I'm thinking of a DB table like "ui_staff" where these "staff_header_color" and "staff_bg_color" are either text columns OR they're object keys in a JSON column.
--
But... I think you could argue that a new DB table might be premature since right now you're only proposing 1 new column. Fair enough.
I think this is the solution. We need a library.library_css that would be a JSON version of CSS rules specific to the library. We allow edition via a "css" form that could be on the edit library view, with some attributes and color picker. It will build a solid ground for future changes. Example: https://snipboard.io/WVSrnt.jpg It does not seem to be a lot of work, but allow for way more flexibility than introducing the "1 DB column per css rule/color" pattern. -- You are receiving this mail because: You are watching all bug changes.