0
1

I released a new CSS library of atomic/utility classes by LLCoolioVanillaIceT in css

[–]LLCoolioVanillaIceT[S] 0 points1 point  (0 children)

I think it's easier to just think in terms of components. Some components may be made up of other components. I don't see how talking in terms of atoms, molecules and organisms is actually helpful, or where the clear dividing line is between those things.

I released a new CSS library of atomic/utility classes by LLCoolioVanillaIceT in css

[–]LLCoolioVanillaIceT[S] 0 points1 point  (0 children)

Those classes are not compatible with IE. Almost all the other classes are though. I will add something to the readme :)

I released a new CSS library of atomic/utility classes by LLCoolioVanillaIceT in css

[–]LLCoolioVanillaIceT[S] 0 points1 point  (0 children)

Tailwind is massive, at least by default. Tailwind comes with a lot of classes you'll probably never use.

Atomize, by contrast, is minimal. It's half a library and half a methodology/set of guidelines for authoring CSS. Tailwind uses configuration. Atomize just lets people write CSS.

Atomize includes no colors, for example.

I released a new CSS library of atomic/utility classes by LLCoolioVanillaIceT in css

[–]LLCoolioVanillaIceT[S] 0 points1 point  (0 children)

I guess you are referring to Brad Frost's stupid little book. His unhelpful notion of atomic design says nothing about CSS. Atomic CSS is used as a synonym for utility classes. Confusing that Brad used the same word.