3 ms·
Now maintain an app with 3 front end devs. With Tailwind there’s no consistency across developers. It’s all highly configurable, but no convention.
by awb 4y ago
Now maintain an app with 3 front end devs.
With Tailwind there’s no consistency across developers. It’s all highly configurable, but no convention.
- alvarlagerlof 4y agoThat's when you make components
- awb 4y agoDev 1 might make a card component with grey text as #999 and Dev 2 might make a footer component with grey text as #888. Components are locally consistent but not globally consistent. Or, let’s say you want to change all your grey text to #777, then you have to go back through all your individual components and hope you didn’t miss anything.
- kaba0 4y agoYou ain’t hardcoding colors inline, you refer to them via “variables” basically, so this situation doesn’t exist: https://tailwindcss.com/docs/customizing-colors https://tailwindcss.com/docs/customizing-colors
- armatav 4y agoNo buddy, text-gray-600 is globally consistent. So are your own custom defined colors like text-armatav-500. Use the thing before you dismiss it.
- armatav 4y agoHave maintained one with 10 FE devs - Tailwind is a godsend. You should have a design with a catalogue of components to build off of so you don’t have 30 card components. It’s a your-team issue, not a Tailwind issue.