4 ms·
I suggest we have these things called "tags" which might wrap up CSS settings into a generally usable form. So rather than 1,000,000 <div> and a bunch of css di
by AtlasBarfed 4y ago
I suggest we have these things called "tags" which might wrap up CSS settings into a generally usable form. So rather than 1,000,000 <div> and a bunch of css differentiating them, perhaps a "tag" encapsulates some common behavior. The "tags" could have "attributes" to adjust specific parameters on their behavior.
/s
- unsupp0rted 4y agoI use Vuetify for this. There’s a million lines of CSS under the hood but I end up writing maybe 5 lines of CSS per project, not counting all the layout and color classes I attach to elements. Tailwind is similar, except that Vuetify components are appearance + functionality. Whereas Tailwind is appearance-only.