After work there is always something to study and deepen, and if it happens that your work is also your passion, studying is really the best thing!
Today I am about to finish the first "dusting" on Tailwind (tailwindcss.com), to then move on to some practical exercises on components.
The only thing to keep in mind when using Tailwind, born to write semantic CSS, is that the markup will get very polluted, and I must to evaluate the maintainability of code written with this type of approach.
With the @apply directive you can create custom classes to which the Tailwind classes "attach", in order to have a custom nomenclature.
In general, I like the idea of keeping markup separate from style, but so it is! Obviously having HTML overflowing with classes it doesn't really matter to some.
Tailwind also, in production, removes the unused CSS, so that we can lighten and optimize the project!
Visual Studio Code has the integration of the Tailwind Intellisense extention, that allows you to view the list of classes while you are writing, a very valuable aid to not do the continuous "ping pong" from the documentation.
I still have to "mess around" a bit to get carried away, but Tailwind has given me good vibrations, also for the good documentation that it hangs around with, (the community looks really nice, you can find it on Discord and GitHub) I will probably work on some small components to share on Codepen.