Where do you see shared layouts/workspaces actually helping you as a dev/platform team?
Is it more about:
End-users tweaking and sharing individually?
Standardising “golden” setups for a desk by the platform team?
Onboarding new apps/teams?
Faster support (“send me the layout that reproduces this issue”)?
What would be the required vs. nice-to-have features?
It is meant for end users to tweak and shared. It really is nice to have since they don’t really change their workspace frequent.
Thanks for sharing @sunsay00!
Yes, I was thinking the same. Most end-users will not change they default workspace, but there can always be some efficiency seekers and power users that can come up with a smarter solution a developer wouldn’t think of. Now will a normal conversatin during lunch be “Hey, guess what cool layout I have configured” maybe not, idk. But making them visible, maybe further tweaked by the platform team, and then distributed to other users sounds pretty cool.
We are extremely heavy users of workspaces
We have the notion of “global workspaces” that are considered the golden setups for particular use cases in our buisness workflows. These are created alongside developers and a few buisness analysts.
These golden layouts are then adapted by end users or just used directly, if a users finds a better way of working and its accepted by their team we then update the “global workspace” to this new workspace, they tend not to share between each other except for this
This is especially useful when making adjustment to the workflow, new app changes etc… as the new apps automatically load or changes appear directly in the golden layout
We also use contexts inside workspaces to have “shared” applications between teams that then have specalisations using the workspace context to save this so it opens in the teams context view to help with their ways of working
We have at times used workspaces for issues allowing us to re-create the scenario a lot easier