Hacker News Reader

My take on this is that documents are different from applications, and so different approaches to composition and organisation are arguably OK.

Personally though, I'd introduce another intermediate set of names - like 'color-brand-primary', 'color-brand-secondary' etc... so you can make branding changes more easily. The majority of Tailwind can be used as-is though.

View on HN

The `blue-x00` is just the default, you can override which colors are available via the tailwind.config.js file, as detailed in the documentation:

https://tailwindcss.com/docs/customizing-colors

It's definitely feasible to add custom color names (and other properties). I have brand specific color names in an app I'm working on right now. There's a theme object in tailwind.config.js that deep merges with the defaults. Great for setting up custom colors, fonts, etc.

Reply on news.ycombinator.com