I was very much against frameworks initially: tailwind, bootstrap etc. However, when I started really building sites & apps using components, I found tailwind made my life a lot easier, so I could easily see and change styling while writing code/html, and it would only affect that component.

Beforehand, I was trying to come up with names for CSS classes all the time, and then I'd change one thing, and fuck up styling on a diff page.

[–] Karjalan@lemmy.world 16 points 1 day ago

Honestly love tailwind. Once you get used to all the names/abbreviations and how they work with sizes and states etc. it's much easier to see what's happening when eyeballing code.

Makes reviewing and bug fixing easier too.

I get that early on it feels annoying. I recall disliking it the first time I learnt it, but then when I went back to regular css and classes I really missed it.

[–] moriquende@lemmy.world 2 points 1 day ago

Yep, a component is a good abstraction level, no point in making life difficult by creating and coming up with names for smaller parts.

[–] MonkderVierte@lemmy.zip 3 points 1 day ago (2 children)

Now it is remembering tags for property instead.

[–] moriquende@lemmy.world 2 points 1 day ago

Any passable editor nowadays does the heavy lifting for you, you can usually even write the CSS tag you want and it'll show you the options.

[–] FooBarrington@lemmy.world 2 points 1 day ago

Except that you learn the class names once and re-use them across all your projects, whereas CSS classes are different for every single project.