The post asks "why not use tailwind CSS?". The community members discuss the pros and cons of using Tailwind CSS. Some key points:
- Tailwind provides a grid system out of the box, which is seen as a benefit.
- Tailwind's predefined classes can be used as a design system, similar to tokens, and the naming convention can be adopted even without using Tailwind.
- Tailwind's functional class names are seen by some as a new language that is unnecessary.
- With the upcoming release of CSS variables, the need for Tailwind's functional naming style may become obsolete, as variables can be used to define sizing and other values.
- Some community members feel that the manual effort required to set up Tailwind adds overhead compared to using an existing design system or style guide.
- Potential solutions suggested include using templates, a token marketplace, and improving the ability to import tokens.
There is no explicitly marked answer in the comments.
you mean classes like "grid-cols-1"? these are similar to tokens and can be just imported as a style guide / design system using any webstudio style guide or your own.
In the essense these are just names you can define. The fact that they are predefined in tailwind essentially means you could create a bunch of tokens using tailwind naming convention if you like them
see it this way: tokens allow you to use tailwind or any other convention, more so they allow you to style locally without a lot of custom syntax e.g. top-[117px]
its good to have predefined values for spacing, typography, grids to have a constrained design system, but you don't have to use tailwind for that, its just the design system
I agree. That is not the issue. I think the issue is rather the fact that you have to manually add a lot of stuff that already exists sompleplace as a file
