Well, I started to use Tailwind recently and I do it mainly with the help of @apply. I think this way of writing classes is better because it doesn't "pollute" HTML with hundreds of classes, which then blow the whole markup. In addition I think it is easier to discover some typo or make a change direct in CSS. But I still use them in HTML, where it makes sens for me.
Generally I think Tailwind with the entire customization and PurgeCSS is a great way to deal with CSS in a project.
Well, I started to use Tailwind recently and I do it mainly with the help of
@apply. I think this way of writing classes is better because it doesn't "pollute" HTML with hundreds of classes, which then blow the whole markup. In addition I think it is easier to discover some typo or make a change direct in CSS. But I still use them in HTML, where it makes sens for me.Generally I think Tailwind with the entire customization and PurgeCSS is a great way to deal with CSS in a project.
For sure. And with Tailwind v2.0 they've made it easier to do just that:
blog.tailwindcss.com/tailwindcss-v...