CSS colors needs to be broken out more for customizing

Bug #1830960 reported by Rogan Hamby on 2019-05-29
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
Wishlist
Unassigned

Bug Description

One challenge for those doing frequent migrations with Evergreen is that it makes a lot of assumptions in terms of the relative colors defined in colors.tt2. However, libraries often have color schemes that don't work requiring a number of changes to the style.css.tt2 and new colors added in the colors.tt2. The patch here provides new colors in the colors.tt2 so that relatively easy customization can be done via the colors without having to change the CSS file. This will also make upgrades easier long term for libraries with customized OPACs if they don't have to touch the style.css.tt2 as much. I've been using these for a long time to make customizations easier.

It includes:

- changes the staff-hold element by default to the background, this isn't quite as pretty as the light accent but prevents a common issue of unreadable text (worth the trade)
- separate footer background text colors
- add a button color for backgrounds in addition to the button text color
- add a header text color
- add a distinct background, text and text hover color for the header links bar
- add background, over and over text for the opac button

user/rogan/more_colors_for_opac_customizations

https://git.evergreen-ils.org/?p=working/Evergreen.git;a=commit;h=bab2933f44581ff7231204b65b19dc66b7c191f4

tags: added: css
Galen Charlton (gmc) on 2019-05-29
Changed in evergreen:
milestone: none → 3.4-beta1
Rogan Hamby (rogan-hamby) wrote :

I'll be adding a commit to this to add release notes including documentation of what to look for when updating the colors.tt2 file.

tags: added: pullrequest
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers