Will HopeUI be Tailwind based now instead of CSS in JS? #274
JacobZwang
started this conversation in
General
Replies: 1 comment
-
Hi, yes I will use Tailwind to generate the CSS of Hope UI. However I will not use the component layer or <button class="ui-flex ui-text-white ui-bg-blue-600">Button</button> The reason i'm doing this is because The benefit of only using prefixed utility classes is that Tailwind users will also be able to override Hope UI styles with utility classes too. /* index.css*/
@import "@hope-ui/core/style/hope-ui.css" /* Tailwind preflight + @tailwindcss/forms + prefixed Hope UI utilities. */
@import "tailwindcss/base" /* preflight disabled here, because already provided by Hope UI. */
@import "tailwindcss/components"
@import "tailwindcss/utilities" /* utilities here will take precedences over the ones from Hope UI. */
@layer base {
:root {
--hope-colors-primary-500: 13 148 136 /* override theme colors with RGB color channels. */
}
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I saw you change the README to say you will be moving away from CSS in JS. Does this mean that you will be moving to a Tailwind-based solution now? That would be fantastic IMO. I've been building design systems using a combination of components, Tailwind Utility classes, and the Tailwind component layer and have found it an excellent workflow. I've found using the component's name as the prefix to related classes to be very intuitive.
Beta Was this translation helpful? Give feedback.
All reactions