3 ms·
I want the styles to be in the template though, because I don't want to bounce back and forth between 2 files when designing a single UI. And it's not just inli
by hbn 4y ago
I want the styles to be in the template though, because I don't want to bounce back and forth between 2 files when designing a single UI. And it's not just inline styles, there's some things Tailwind can do that a style tag can't. Such as screen size breakpoints.
Here's how to make a div have 0.5rem of left/right padding on mobile, and 2rem on any screen larger:
<div class="px-2 sm:px-8">
I'd much rather do this than mess with CSS's horrible media query syntax myself. And when I come back to this later, I don't have to cross-reference between (probably badly named) classes across 2 files to figure out how that div behaves.
- jakelazaroff 4y agoOkay, but now we’re back to Tailwind being back to syntactic sugar for styles (you can definitely put media queries in a style tag). I disagree with your preference; all the classnames are not easily parseable and obscure the markup, and I much prefer the CSS media query syntax. But that’s, like, just my opinion, man. If you like it better, don’t let me stop you!
- skttl 4y ago>(you can definitely put media queries in a style tag) How?
- jakelazaroff 4y ago<style>@media (min-width: 100px) {}</style>