- From: Christoph Päper via GitHub <sysbot+gh@w3.org>
- Date: Sun, 29 Jan 2023 22:11:15 +0000
- To: public-css-archive@w3.org
There are so-called _utility-first_ frameworks like [Tailwind](https://tailwindcss.com), which are based on atomic classes that often contain a single CSS rule and also somewhat expose property and value in their class name, e.g. `.bg-green {background-color: #97EE11}`. Those predefined _utility classes_ form a restricted or controlled set of design options and are applied directly in the markup as usual, so `class` attribute will frequently have a long list of values. If such lists repeat, the resulting pattern may be condensed in a classic semantic class again by framework-specific means of this can be left to some solution for templates.
This approach apparently has some benefits for implementing graphic designs as websites and maintaining them.
If I understand the proposal correctly (and I certainly don’t understand all of it), a part of it would reenable the separation of style and content within the utility first paradigm:
~~~~ css
$utility {color: green}
.pattern {@include $utility}
~~~~
~~~~ html
<a style="@include $utility">foo</a>
<b class="pattern">bar</b>
~~~~
instead of current non-standard solutions like
~~~~ css
.utility {color: green}
.pattern {@apply utility}
~~~~
~~~~ html
<a class="utility">foo</a>
<b class="pattern">bar</b>
~~~~
Is this correct and in scope?
--
GitHub Notification of comment by Crissov
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3714#issuecomment-1407783568 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 29 January 2023 22:11:17 UTC