Skip to content

feat(css): tint neutral palette based on brand

Nick Brandt requested to merge 1452-tint-neutral-palette into main

What does this MR do?

This updates our neutral colors to have a tint based on our branding. More details can be found in gitlab-org/gitlab-services/design.gitlab.com#1452 (closed).

palette

You can see how the adjustment of the neutral palette impacts the product in gitlab!102565 (closed).

Screenshots

📝 Note: Screenshots haven't been updated to reflect the lightening of $gray-10.

component before after
alert alert-before alert-after
badge badge-before badge-after
buttons buttons-before buttons-after
button group button-group-before button-group-after
card card-before card-after
toast toast-before toast-after
toggle toggle-before toggle-after
token selector filter-component-before filter-component-after
heatmap heatmap-before heatmap-after
dashboard skeleton dashskeleton-before dashskeleton-after
typescale typescale-before typescale-after

Does this MR meet the acceptance criteria?

Conformity

  • Code review guidelines.
  • GitLab UI's contributing guidlines.
  • If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • If the MR changes a component's API, integration MR(s) have been opened in the following projects to ensure that the @gitlab/ui package can be upgraded quickly after the changes are released:
  • Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.

Closes gitlab-org/gitlab-services/design.gitlab.com#1452 (closed)

Edited by Jeremy Elder

Merge request reports