I like Tailwind. I think the appeal here is to write less CSS, get things done faster, have a consistent design and the maintainability. All good so far.
But let's remind everybody that this is only one approach of many you can use.
One approach that can solve problems Tailwind tries to is proper planning. An initial style guide can show you that the `author-bio` component looks similar to `article-preview` (taken from the author's blog post[1]), so you beforehand plan for that HTML and CSS and create a component you can reuse.
Of course, you could have decisions made after the fact and go back and change stuff; nothing is bulletproof.
But let's remind everybody that this is only one approach of many you can use.
One approach that can solve problems Tailwind tries to is proper planning. An initial style guide can show you that the `author-bio` component looks similar to `article-preview` (taken from the author's blog post[1]), so you beforehand plan for that HTML and CSS and create a component you can reuse.
Of course, you could have decisions made after the fact and go back and change stuff; nothing is bulletproof.
- [1] https://adamwathan.me/css-utility-classes-and-separation-of-...