[doubletgl]

Been through this process. Thing is, when you have a <Heading> component, you might as well simply write a css module for that component. Tailwind is great for "fast prototyping" and quickly styling a bunch of static HTML though. Wouldn't use it for a larger single page app.

[city41]

I might be overreacting to past projects, but I've almost always found bespoke css gets out of control. Most projects tame it with well defined values for margin, padding, etc, and applying and enforcing those values means you sort of end up creating your own Tailwind. The "atomic" side of Tailwind is nice, but so is the consistency in values it provides.

If I was to take the css module approach today, I might still find myself using Tailwind and @apply inside the modules.

[jozzy-james]

sure, if you have "a" heading component - but what about when you have 30 heading components?

[vanviegen]

Is that something that should happen in a well-designed web app?