4 ms·
Eh, I dislike Tailwind but this doesn't sound like it will hold water in the long run. Why the hell does a rule talk about consistent padding and then not use
by morbicer 3y ago
Eh, I dislike Tailwind but this doesn't sound like it will hold water in the long run.
Why the hell does a rule talk about consistent padding and then not use css variable? A class name .card is a sure thing to conflict somewhere. Typography inheritance is another good way how to introduce hard to debug bugs. Global scope css - ewww (use only absolute minimum necessary).
Please use css-in-js, Tailwind, shadow dom or at the bare minimum css modules. Friends and future you will thank you.
But hey, maybe they are building some blog. I live in the apps world.
Also some rules are valid like the one about not using margin on the component itself.
- emmacharp 3y agoThanks for the comment. It reminds me that examples should be more real-like. Hehe. Because, yeah, I would absolutely use a custom property for it. Same with .card, a simple example which in practice may be more precise, yes. Global scope is for base rules, yes. Rhythm, typography, maybe colors only. Still it's great to be able to style these design layers globally! I'll adjust the examples to reflect this. Thanks for the lesson! PS: hard to debug bugs? The inspector shows styles handily for global styles!