Curious about your expectations:
Do you rely on utility classes only in your workflow, or do you split reusable patterns into "original CSS"-like @apply blocks?
And how would you categorise the complexity of the Apps/UIs you build like this?
I'm very interested in the specifics of successful applications of Tailwind that the maintainers keep deeming a good solution, since CSS as a whole is one of my main scopes and I've had quite some projects that where basically some variation of writing custom brand-lib frameworks for teams who embraced Tailwind at first, but in time ended up hard locked when needing to refactor or iterate their UI
And how would you categorise the complexity of the Apps/UIs you build like this?
I'm very interested in the specifics of successful applications of Tailwind that the maintainers keep deeming a good solution, since CSS as a whole is one of my main scopes and I've had quite some projects that where basically some variation of writing custom brand-lib frameworks for teams who embraced Tailwind at first, but in time ended up hard locked when needing to refactor or iterate their UI