Replies: 1 comment 1 reply
-
Hey! What you described would work really well as a preset you can reuse across all your projects! This is a great approach, but bakes in a lot more opinion in a project than the default, "prototype with everything" config. Sometimes you just want to have access to all the colors under the sun when starting a project and operating in "discovery" mode. That said, customising and culling down colors is absolutely a good idea and something we recommend on a per-project/brand basis! |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello I've an idea for colors.
I find that I don't need all the different colors values, I usually need one or two variants of colors. My proposition is this, ditch all red green etc.. colors, or make them optional. Instead set a
accent
color, or if you prefer extensibility aprimary
andsecondary
color.This way not only the file size will be smaller, but more importantly when theming you don't need to change all occurrence of
red-
etc.. in the markup, or change thered
etc.. in the tailwind settings (you would end up with red color names for colors not anymore red). You just change tailwind settings colors foraccent
orprimary
andsecondary
. You decouple color name from value for theming.For special colors you can set
success
anderror
etc.. colors in the same way, since you don't have red and green colors.What do you think guys?
Beta Was this translation helpful? Give feedback.
All reactions