Why tailwind and isn't it the antithesis of dry developement?

[StrangeTech]

@JulianM

In this regard using an alternative to tailwind like acss makes sense to keep the semantic approach and the benefits of usability, maintainability and rapid development right?

As @Louis mentioned in the live, there are pos and cons to both approaches. For ACSS, they use BEMs which can potentially create inflexibility and may or may not suit certain teams or developers and for Tailwind, the duplication of classes in the html may not work for others.

@JulianM

I understand its a matter of preference but I am looking for better options to improve the workflow and the results, I pay attention to the options while learning which one could be better.

It is definitely wise to keep updated on the different approaches and find the one that works best for your case.

We are also exploring ACSS as an option in parallel to Tailwind, now that it is available.

@JulianM

I would like to know more about this type of workflow exactly.

I have created a new post that discusses this:

Cwicly Tailwind Shells and Components

As it has come up recently, this is just a quick non-exhaustive summary of the similarities and differences between Shells and Components. Components and Shells can work independently of one another or be combined together. While there is some overlap in what they do to a degree, they are not solving exactly the same use cases. Components are much more powerful ways to create reusable block hierarchies that can have editable properties and variations. See the Cwicly documentation for more in…

@JulianM

How components add to this and how it works in terms of html output?

HTML output is not changed with Shells, the Shell is an editing only concept that allows for semantic development - the Tailwind classes are still added to the HTML and the Shell itself has no reference in the frontend.