Of course you can go back to CSS to do any of these things.
Want to target children of an element? Back to CSS. Want to target the devices between two breakpoints? Back to CSS. Want an :nth-child or ~ sibling selector? Back to CSS.
And so on.Įach of these tools is a poor facsimile of the functionality gaps it has to fill. By appending hover: a class will be applied in a :hover state. By prepending Tailwind classes with md: they will only apply above the md breakpoint. Tailwind achieves this with what it calls modifiers. All of it now has to fit into the classes-only paradigm. Media queries, pseudo elements, selectors, and states. Tailwind has to reinvent everything regular CSS can already do. Here is where Tailwind introduces new problems it shouldn't have to solve in the first place. "So what?" you might ask, what's wrong with just using those classes rather than CSS? It certainly saves some keystrokes. But then you're breaking the Tailwind style-by-classes abstraction, and you have to maintain two seperate styling touchpoints for every element. Of course you can mix Tailwind's more useful classes with regular CSS. text-center rather than text-align: center. block rather than writing display: block and. It's that in order to apply a consistent set of values with classes, you also have to create classes for every conceivable set of rule:value pairs in CSS, even where it adds no value at all. The problem with this approach isn't that its ugly, or bloated (Tailwind purges unused classes), or that "you might as well write inline styles" (you shouldn't). But that's just pedantry, and if the Tailwind way of doing things really was the panacea to all our problems then it would be a very small price to pay. Its creator acknowledges as much right on the project home page. There's no denying that Tailwind is hideous. The idea being that you no longer write any CSS of your own, you compose predefined classes like lego pieces for every single property.ĭevelopers new to this way of working often have a knee-jerk reaction just from looking at example code.Įnter fullscreen mode Exit fullscreen mode Tailwind achieves this with an extensive library of CSS classes to style everything. This was Tailwind's biggest idea, and the greatest benefit of utility-first CSS as a concept: compose don't create.
#Float none will not work for media query with wow slider code
Which means that your code stays consistent and you aren't making things up as you go. From typesets to spacing to colours, everything is defined in a single place. And for the most part, it delivers on that promise.īy using Tailwind you're almost guaranteed a single source of truth for all the values you use throughout a project. A utility-first library of CSS classes, it promises a new way of styling that's more consistent, maintainable, and faster than writing CSS directly. Tailwind CSS has taken the frontend development world by storm over the last few years.
0 kommentar(er)
