feat(tailwind): add the custom configuration
What does this MR do?
feat(tailwind): add the custom configuration
This backports the Tailwind configuration we have been iterating on in the GitLab project. This results in a more or less complete config which consumer can start leveraging to apply Pajamas-compliant CSS utils.
BREAKING CHANGE: This overrides several Tailwind configuration option. Consumers that were already using Tailwind with the GitLab UI preset should keep an eye out for utils that might behave differently.
Screenshots or screen recordings
Integration merge requests
-
GitLab: gitlab!157486 (merged) -
CustomersDot: https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/10334 - [-] Status Page: Not using Tailwind yet.
-
GitLab Docs Hugo: gitlab-org/technical-writing-group/gitlab-docs-hugo!125 (merged)
Does this MR meet the acceptance criteria?
This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.
Toggle the acceptance checklist
Conformity
-
Code review guidelines. -
GitLab UI's contributing guidelines. -
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 (see integration merge requests above). -
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"
toaria-expanded="true"
when an accordion is expanded. -
Color combinations have sufficient contrast.