News for hackers. Stuff that matters.
Re:Why I Love Tailwind by w_t_payne on Monday December 07, 2020 @10:42AM (#25333198)
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.

Re:Why I Love Tailwind by cuddlecake on Monday December 07, 2020 @03:42PM (#25337203)
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

Re:Why I Love Tailwind by regulation_d on Monday December 07, 2020 @11:29AM (#25333673)
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.