The community members discuss structuring a new Webstudio project. They suggest that the Finsweet Client-First methodology is not necessary, as Webstudio's design token system provides a simpler approach. The key points are:
- Custom classes and Combo classes are not needed, as elements can be styled directly using local styles and composable tokens.
- Utility tokens are recommended, as they provide reusable functional styles.
- Semantic tokens can be used to name styles based on their context.
- The community members suggest creating a "Token Naming Methodologies" page in the Webstudio documentation to compare different approaches and explain the token system.
semantic would be when you want to name something based on how its used in a specific context, utility - a more reusable functional naming, can be reused everywhere
The more granular utilities you make, the more composable they get. E.g. you could use tailwind-style atomic utilities, which define one property at a time