Skip to content
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

Normalize colors to the palette #4867

Merged
merged 4 commits into from Aug 2, 2020
Merged

Conversation

fqueiruga
Copy link
Contributor

@fqueiruga fqueiruga commented Jul 24, 2020

This PR normalizes many colors used in Jenkins to the new palette used in the sidebar, hyperlinks, buttons, tables, etc.

Changes:

  • Swapped the --primary and --primary-hover variables to reflect their actual use. The current primary hover color was used as primary on the first iterations of the palette
  • Merged the --lightest-grey into --very-light-grey, with a value of #f8f8f8 (as in the color palette)
  • Removes some hardcoded, off-palette greys on several resource files. buildHistory widget and plugin excerpts now use proper palette colors.
  • Removed unused CSS variables.
  • Changes default icon fill to --text-color.
  • .bigtable styles applied to the Matrix Project tables.
Some screenshots

Matrix project table using .bigtable styles for coherence
Captura de pantalla 2020-07-23 a las 14 44 22

Plugin uninstall warning using proper colors
Captura de pantalla 2020-07-23 a las 15 39 44

Note: this PR intentionally leaves out many hardcoded values due to difficulty of changing the values or testing the changes. On example is the progress bar. If the proper --primary and --danger values are used in the progress bar it will still look weird because the fill animation is done using a gif.

Fixes #4867

Proposed changelog entries

  • Normalized colors in different widget to be consistent with the new color palette.

Proposed upgrade guidelines

N/A

Submitter checklist

  • (If applicable) Jira issue is well described
  • Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
    • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
  • Appropriate autotests or explanation to why this change has no tests
  • For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@timja
@uhafner
@oleg-nenashev
@daniel-beck

Maintainer checklist

Before the changes are marked as ready-for-merge:

  • There are at least 2 approvals for the pull request and no outstanding requests for change
  • Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
  • Changelog entries in the PR title and/or Proposed changelog entries are correct
  • Proper changelog labels are set so that the changelog can be generated automatically
  • If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
  • If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

- Merges the --lightest-grey into --very-light-grey, with a value of #f8f8f8 (as in the color palette)
- Removes some hardcoded, off-palette greys on several resource files
- Brings to palette colors on buildHistory widget, plugin excerpts
- Removes unused CSS variables
- Changes default icon fill to --text-color
- Applies the .bigtable style to the Matrix Project tables
@oleg-nenashev oleg-nenashev added rfe For changelog: Minor enhancement. use `major-rfe` for changes to be highlighted web-ui The PR includes WebUI changes which may need special expertise labels Jul 24, 2020
Copy link
Member

@uhafner uhafner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@timja timja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All seems fine,

It doesn't appear to fix jenkinsci/dark-theme-plugin#126 as reported that it does though.

@fqueiruga
Copy link
Contributor Author

@timja should work now

@timja
Copy link
Member

timja commented Jul 31, 2020

@timja should work now

confirmed, works, thanks!

Copy link
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds about right.

We may merge it in 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process

@oleg-nenashev oleg-nenashev added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Jul 31, 2020
@timja timja merged commit 87f9404 into jenkinsci:master Aug 2, 2020
@timja timja added bug For changelog: Minor bug. Will be listed after features and removed rfe For changelog: Minor enhancement. use `major-rfe` for changes to be highlighted labels Aug 4, 2020
@fqueiruga fqueiruga deleted the consolidate-colors branch August 5, 2020 10:14
olivergondza pushed a commit to olivergondza/jenkins that referenced this pull request Aug 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug For changelog: Minor bug. Will be listed after features ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback web-ui The PR includes WebUI changes which may need special expertise
Projects
None yet
5 participants