The concept of webstudio tokens over webflow classes is great! It would be even greater, if one could apply local changes in Style to already defined tokens, that are already applied on the element. That way one could try out changes locally and then adopt the changes for the token (or otherwise dismiss them for the token)

If I have set different style-options for different breakpoints an then create a token: Does the token memorize, which style-option is set on each breakpoint? Or do I have to create a token for each element AND each breakpoint seperatly?

Im trying to show different svg headres, depending on breakpoint.
AI tells me:
"Style changes you make on one breakpoint will cascade and affect that breakpoint and all smaller ones. Here are key points about managing component visibility across breakpoints:
You can use the show/hide functionality to control component visibility at different breakpoints
When you hide a component using the show/hide toggle, it is completely removed from the page server-side - it's not just visually hidden
This makes it useful for: - Conditional content display - Testing different components - Creating responsive layouts where certain elements only appear at specific breakpoints"
Tooltip tells me: "Removes the instance from the DOM.
Breakpoints have no effect on this setting."
Tooltip seems to be right. Show/hide toggle has no effect at different breakpoints.
In a different post I read, that changes in the settings panel have no effect on breakpoints, only changes in style panel do. So I tried StylePanel>layout>display>none, but this also doesn't work. Changes for visibility affect all breakpoints at the same time. Please see screenshots of the wanted effect and compare with the shared project. I post the 3 svg-files as attachments

It would be nice, if one could change the values of Craft/Open Props CSS variables direktly from within the Style Guide. For example right-clicking on the Text of the css-variable or on the Color Palette or of "--foreground-primary" would reveal an option to restyle the Craft/Open Props CSS root-variable directly without switching to the Globel Root and identify the corresponding CSS variable in a painfully long list of variables and change them there.

I'm looking for a possibility to change the orientation and ratio for images in a Grid, that come from a cms/cdn. Default would be square 1 column by 1 row. If the image has the "orientation"-value set in CMS to landscape it would span 2 by 1, if set to portrait it would span 1 by 2. Maybe an additional value "size" could set greater spans like 4 by 4 (square), 3 by 2 (landscape) and 2 by 3 (portrait) for promoted images. I found a tutorial for Webflow, which covers most of the functionality: https://www.youtube.com/watch?v=VJ0swK8mbg4
Since Webstudio doesn't have an integrated CMS, the Values would have to come from an external (headless) CMS. But how to read them out and process them, so that the Grid-Items in Webstudio visualise as wanted?

I#m still on "Hobby" .
Using the "Portfolio" craft-template, I find items with differnt colors in the navigator. Most of them are black an have a style panel. Some of them are violet and don't have a style panel. I think, this is because the violet items of the template refer to external data / data variables. Does the violet color mean: "here is some information missing?". Is there a possibility to change the item from external data to local to get back the styling-panel for the objects? Ordoes the violet color mean something completely different?

👏 that helped, thanks!

Hello Webstudio Team!

I'm new to webstudio and taking my first steps. I've tried with webflow before. What I liked there: they have great video tutorials not only about the Ui und functionality, but also on really building sites and the pros and cons of different design-concepts.
What I didn't like: not OpenSource an longterm cost not transperent.

What I like with webstudio: generous freee tier, OpenSource, the concept of tokens ans craft-css and tho possibility to connect to any external CMS/CDN.

What I don't like about webstudio: if I got that right, for connecting to external CMS/CDN Webstudio Pro is needed. The free trial period of 14 days is too short for me. It would be nice, if the CMS-connection could at least be activated for the craft templates to study how this works. The videos and tutorials are not as comprehensive and extensive as with webflow. Webstudio is new in the market, so I'm shure, documentation and range of functions will improve.

You did an extraordinary good job in almost no time (since 02.2023) so far!