UX: Improve Workspace page (exploration)
MR: Pending
Description
There's potential to iterate on the Workspaces page and get some quick quality of life wins.
Preview link
Problem 1:
- Showing the url as a link likely isn't necessary or particularly helpful to a user.
Problem 2:
- Using
Preview
as the column label is inaccurate as the link launches the workspace in the Web IDE and isn't really a preview.
JTBD:
- Launch the remote dev environment and start writing code.
Possible solutions:
- Use a
Launch workspace
button instead of a url link. - Use a dropdown with various IDE options to launch workspace.
- Rename or consider removing
Preview
column label.
Workspace status
Problem 1:
- Is it clear to an end user how
stop
andterminated
states are different?
Examples:
- Customer question:
-
-
What is the difference between "stop" and "terminate"? Both options when selected do the same thing: delete the NS, and PV.
-
JTBD:
- Manage remote development environment resources effectively.
Devfile location
Problem 1:
- The devfile is key part of a workspace configuration and users now have the ability to specify paths to devfiles. However, it's not clear how important this is to an end user and how/if it should be exposed in the workspace list.
Examples:
JBTD:
- Manage a remote dev environment's configuration.
UX Scorecard recommendations
- Revisit preview link
- “It was strange to me to hit Preview to find this”
- Revisit "terminated" terminology
- (consider
delete
instead) - Could this impact how we name "Terminated workspaces" tab in #409531
- (consider
- Revisit how devfile and config options are presented
- Can be unclear how the devfile relates to the workspace
- Some users would like to see logs from the UI. It appears we have access to this data: #409309 (closed)
- Revisit
Project
label onYour work > Workspaces > Create workspace
- The
Project
label could be more descriptive to help users understand the scope of the projects that appear in the list. - For example: All projects in their instance, all projects they have access to, or all projects that are configured with the workspace feature.
- Consider if we can help users understand within the list whether a project can be used with the workspace feature.
- The
- Make it easier to open a workspace locally (VS Code)
Acceptance Criteria
-
Design solution concepts -
Gather feedback from team -
Validate concepts internally -
Split up into iterable issues
Edited by Taylor Vanderhelm