One of the best things about Tailwind (and the component and HTML-first movements in general) is a move towards Locality of Behavior: https://htmx.org/essays/l

One of the best things about Tailwind (and the component and HTML-first movements in general) is a move towards Locality of Behavior: https://htmx.org/essays/locality-of-behaviour/ https://htmx.org/essays/locality-of-behaviour/ With these approaches, you can achieve a complete understanding of a component in one place, without needing to pick around in a bunch of different places, using id-matching or some other mentally burdensome mechanism to keep everything straight. There are trade-offs (as the essay mentions) but Locality of Behavior obviously has a lot of advantages.