You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Tailwind CSS finally (and excellently) supporting @apply with "variants", the use case for Kingdom CSS over Tailwind is becoming very narrow!
Actually the only major things left from Kingdom that Tailwind doesn't handle out of the box are vertical rhythm for every HTML element (level 3) and baseline-shift (level 4). But if needed in one of my projects I'd probably use Tailwind as a base and then customise line-heights and positions to achieve the same effects on a per-component level.
Responsive locks can be handled much simpler using CSS min() & max() in the post-IE era, and personally I certainly don't intend to ever launch anything new supporting IE 😄
The text was updated successfully, but these errors were encountered:
With Tailwind CSS finally (and excellently) supporting
@apply
with "variants", the use case for Kingdom CSS over Tailwind is becoming very narrow!Actually the only major things left from Kingdom that Tailwind doesn't handle out of the box are vertical rhythm for every HTML element (level 3) and baseline-shift (level 4). But if needed in one of my projects I'd probably use Tailwind as a base and then customise line-heights and positions to achieve the same effects on a per-component level.
children:
-like-variant in Tailwind, if not it's probably quite easy to write a plugin, and https://bjuppa.github.io/kingdom/modules/extenders/ is mostly used for spacing anyway and Tailwind already does that part https://tailwindcss.com/docs/spacemin()
&max()
in the post-IE era, and personally I certainly don't intend to ever launch anything new supporting IE 😄The text was updated successfully, but these errors were encountered: