Join the Webstudio community

Updated last year

token breakpoint manager

At a glance

The post discusses the potential issue of having multiple components from different packages in a project, which could lead to a bundle of unnecessary breakpoints. The community members suggest using a token manager to manage the breakpoints and avoid maintainability issues. However, they note that the token manager is not yet built, and the best approach is to stick to one official design language. The community members plan to introduce CSS variables and an official standard for how templates should be structured, which would allow mixing templates from different authors. They mention that this process will take some time and will involve the community in the discussion.

With the new marketplace addition, there's a potential to add multiple components to your existing project.

If you pull components from different packages, you could potentially get a bundle of unnecessary breakpoints.

I'm wondering if there's a way to make collect breakpoints into a token-type manager so it wouldn't become unmanageable over time.
O
7 comments
token manager is something we have been planing on, but haven't built yet, so yes, one has to be careful and ideally stick with one sections library to avoid having all kinds of naming conventions mixed
even with token manager, using multiple different systems will result in bad maintainability
the best way is going to be sticking to one official design language
we haven't created one yet because we want to do that after we introduce css variables, once we have it, we will introduce an official standard for webstudio for how templates should be structured on top of that official design language
this way if done well one can mix templates from different authors
it will take us some time to get there
we will be making this standard a public discussion and involve the community
Add a reply
Sign up and join the conversation on Discord