-
Notifications
You must be signed in to change notification settings - Fork 14
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
Color updates #19
Color updates #19
Conversation
There may be more areas to refine in regard to colors. |
Issue #21 opened to track these updates. |
While you're in this file, please review the header category tabs section. It appears to me that ZCA_HEADER_TABS_COLOR and ZCA_HEADER_TABS_COLOR_HOVER appear to have been swapped (perhaps since day one). Shouldn't ZCA_HEADER_TABS_COLOR apply to |
Are you saying this because visually it looks wrong? Or because text-descriptions mentally seem misaligned? I'm having trouble seeing what you think it should look like visually. |
The text-descriptions seem misaligned. I just looked at the admin side and found the same misalignment, so the two misalignments cancel out. Visually they are OK. |
My old eyes don't always work. Visually they're swapped between admin and store sides. |
admin/includes/init_includes/init_bc_config.php sets the following titles for the admin side: The store side is reversed. Looking at the color values on the admin side, the Color on Hover is a lower value than Color. The Color on Hover is darker than Color. Looking at the store side, the color on hover is lighter than non-hover. |
You're right. It's reversed, and the default colors are therefore reversed too. |
…lors Ref discussion with @dennisns7d at lat9#19 (comment)
Ref discussion at lat9#19 (comment)
I've added the following to this PR: and PR'd an update to swap the default colors and improve the admin descriptions of those values: https://github.com/lat9/ZCA-Bootstrap-Template/pull/25/files |
…lors Ref discussion with @dennisns7d at lat9#19 (comment)
If I've done it right, we might want to add something in the Release Notes that tells people who are upgrading to double-check (and possibly swap) the colors they've assigned for |
Ref discussion with @dennisns7d at lat9#19 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we now include a stylesheet_configs.php
(I'm sure there's a better name) to include these non-color-specific styling changes?
IMO no. In theory end-users won't "need" to touch/edit this file, so if it contains one entry that's not color-related but pulls dynamic values from store configuration, it won't cause any confusion. If the current naming of stylesheet_colors.php is confusing in terms of semantics, I have no objection to it being renamed. |
No description provided.