3 ms·
We defined Tailwind config overriding the default values to match our design system. Then on top of this we have components library with common basic component
by random_kris 4y ago
We defined Tailwind config overriding the default values to match our design system.
Then on top of this we have components library with common basic components and layouts
Then inside the apps we use the components and that Tailwind config and it works quite nice.
We have rules for tokenized colors and sizes so it all references the config.
There are problems and all, but all in all I think is quite good
- chiefalchemist 4y agoThat makes sense, but what value does TW add? Why have that dependency? And not have the team roll your own CSS?
- moomoo11 4y agoBecause you can ship in a few days instead of wasting weeks trying to bike shed through something as basic as css. Use tailwind as a tool, have a component library that can be put together in a couple days max, and now you have ubiquitous styling language and don’t need to waste hours on css of all things. There are bigger fish to fry.
- random_kris 4y agoWell you don't override everything but just what you need. Then devs can still use Tailwind docs on how to use the classes and all
- deleted 4y ago[deleted]