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
I'm really glad to see TailwindCSS shifting from JavaScript-based configuration to more CSS-driven declarations in v4. I have notice that some plugins may not be on the same spirit (yet) and it would, especially for official plugins, make sense to follow suit.
In particular, I’d love to see @tailwindcss/typography eventually support configuration via CSS variables. I don't think i've seen it in the roadmap, but I think it could be a great improvement, especially for projects already adapting their design systems around v4.
Use-case example:
@theme {
--color-foreground:oklch(0.5100/1);
/* Allow prose styles to inherit from existing design tokens */--tw-prose-body:var(--color-foreground);
}
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm really glad to see TailwindCSS shifting from JavaScript-based configuration to more CSS-driven declarations in v4. I have notice that some plugins may not be on the same spirit (yet) and it would, especially for official plugins, make sense to follow suit.
In particular, I’d love to see
@tailwindcss/typography
eventually support configuration via CSS variables. I don't think i've seen it in the roadmap, but I think it could be a great improvement, especially for projects already adapting their design systems around v4.Use-case example:
Beta Was this translation helpful? Give feedback.
All reactions