Most of the time, people showcase Tailwind's @apply feature with one of Tailwind's single-property utilities (which changes a single CSS declaration). When showcased this way, @apply
doesn't sound promising at all. So obviously, nobody wants to use it. Personally, I think Tailwind's @apply
feature is better than described.
Tailwind’s @apply Feature is Better Than it Sounds originally published on CSS-Tricks, which is part of the DigitalOcean family. You should get the newsletter.
https://css-tricks.com/tailwinds-apply-feature-is-better-than-it-sounds/
Zaloguj się, aby dodać komentarz
Inne posty w tej grupie

I know, I know: there are a ton of content management system options available, and while I've tested several, none have really been the one, y'know? Weird pricing models, difficult customization,


Okay, nobody is an exaggeration, but have you seen the stats for hwb()
? They show a steep decline, and after working a lot on color in the CSS-Tricks almanac, I’ve just been wondering


Using scroll shadows, especially for mobile devices, is a subtle bit of UX that Chris has covered before. Geoff covered a newer approach that uses the animation-timeline
property. Here

The CSS shape()
function recently gained support in both Chromium and WebKit browsers. It's a way of drawing complex shapes when clipping elements with the clip-path
prope
