Commit e0c43662 authored by Ezekiel Kigbo's avatar Ezekiel Kigbo

Merge branch 'patch-209-docs' into 'master'

Remove bootstrap-looking component class from docs example

See merge request gitlab-org/gitlab!38534
parents 3f68c499 f472b0db
...@@ -49,11 +49,6 @@ We recommend a "utility-first" approach. ...@@ -49,11 +49,6 @@ We recommend a "utility-first" approach.
This encourages an organic growth of component classes and prevents the creation of one-off unreusable classes. Also, the kind of classes that emerge from "utility-first" tend to be design-centered (e.g. `.button`, `.alert`, `.card`) rather than domain-centered (e.g. `.security-report-widget`, `.commit-header-icon`). This encourages an organic growth of component classes and prevents the creation of one-off unreusable classes. Also, the kind of classes that emerge from "utility-first" tend to be design-centered (e.g. `.button`, `.alert`, `.card`) rather than domain-centered (e.g. `.security-report-widget`, `.commit-header-icon`).
Examples of component classes that were created using "utility-first" include:
- [`.circle-icon-container`](https://gitlab.com/gitlab-org/gitlab/blob/579fa8b8ec7eb38d40c96521f517c9dab8c3b97a/app/assets/stylesheets/framework/icons.scss#L85)
- [`.d-flex-center`](https://gitlab.com/gitlab-org/gitlab/blob/900083d89cd6af391d26ab7922b3f64fa2839bef/app/assets/stylesheets/framework/common.scss#L425)
Inspiration: Inspiration:
- <https://tailwindcss.com/docs/utility-first> - <https://tailwindcss.com/docs/utility-first>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment