Webstudio
Log in

Join the Webstudio community

Updated 4 weeks ago

Isolate selection + Share to Discord

HHolger
·
Currently, sharing an isolated problem means a multistep process in WS = friction. I'm convinced that people would post more question or bugs when isolating and sharing issues would be more straightforward. Maybe you at some point can give us an isolation-mode. Primarily, it should help us finding and fix problems – but it should also allow sharing just the relevant bits of a project.

Possible Flow:
  1. Run into question or malfunction
  2. Select the element that you consider problematic and call Isolation-Command from Navigator or Canvas.
  3. Everything that has no direct impact on the selected elements gets hidden.
  4. Debug. If you can locate the issue, fix it and exit Debug Mode.
  5. If the problem persists, share with support.
  6. A Temp-project is created from visible objects and opened in a new tab, ready to share on Discord.
Screenshots: Access Isolation Mode from Context Menu. Floating Isolation Panel with option to share file.
Attachments
2024-11-02_12h26_35.png
2024-11-02_13h43_06.png
B
O
H
10 comments
BBogdan
Yeah, we need to start supporting full links with url. Will be useful for tooltips to show sources of values
OOleg Isonen
I think even if we had this kind of isolation its still problematic to share the original project publicly. I think people should share the reproduction of just that specific thing as a separate project
OOleg Isonen
At this stage a shortcut for creating a project with just one instance is a bit too much, because there will be global things that need to come a long, so it will still require some manual intervention. I feel like automating this process is a lot of work and too early for us.
HHolger
I saw this isolation primarily as a tool that helps users solve problems on their own. Only when they reach the point to ask for help, a new project would be generated. Before sharing a public link, we could remove customer data – such could also happen automatically, with some lorem ipsum and Unsplash images.

Manually rebuilding a clean isolated case may take considerable time. To make sure that you don't miss anything, you likely should create a full project copy, then delete all unrelated pages and media files. If you are confident enough to rebuild the sample from scratch that exposes the same error without missing ingredients, you likely don't need help.
OOleg Isonen
Yeah, its just technically difficult, and therefore I would hesitate spending time on it for now
OOleg Isonen
usually its just creating a new project and copying the stuff for reproduction
HHolger
Semi anecdotally: I really like what the makers of the 3D sculpting app Zbrush did 10+ years ago. You could record your entire work process – and they did this in a super resource-effective way from the entire undo stack. The app automatically removes boring elements and smoothes camera motion in 3D. Basic sample https://www.youtube.com/shorts/U1N17j-wAQ8

The result was tons and tons of free marketing material for their tool, published on YouTube – long before Loom and others were around. And,  if you ran into any malfunction you had recorded evidence to send to support.
OOleg Isonen
that's sharing the final look, vs sharing the actual build
HHolger
You could also share the file with support. No idea how they did it, but they recorded each interaction with the file - you could scrub back the timeline and branch from there...
OOleg Isonen
Yeah, would need to store all patches. This is planed for versioning. A bit later
Add a reply
Sign up and join the conversation on Discord