Improve workspaces page

[gtsiolis]

Problem to solve

Following up with all the recent features added to the product like Teams & Projects and the upcoming Usage-Based Pricing (UBP), the Workspaces page could benefit from new patterns, components, or layouts.

This could tackle potential improvements like #3594, #5125, #10140, #4635, #4225 and more.

Proposal

TBD (To be discussed)

[gtsiolis]

Posting an early design from a relevant discussion (internal).

BEFORE	AFTER

[jldec]

Thanks @gtsiolis - I copied some feedback below captured during our discussion earlier. I would recommend editing the list below to indicate which item is about which column (or perhaps connect the list to the screenshot)

Some design thinking points:

1. Removes one column, from four to three.
   jl - nice - reduces duplication, more responseive. (would like a prototype to test responsivenesss - e.g. when cells are narrower and wrap)

2. Adds back the table header.
   jl - nice - explains the columns more clearly

3. Keeps the workspace ID as the primary table identifier.
   jl - agree

4. Introduces workspace class.
   jl - agree - should surface this info everywhere we can (ws class-names messy)

5. Uses label for running status indicator for better accessibility.
   jl - agree (states should already be there ?)

6. Combines context URL with branch.
   jl - ok - It’s helpful to surface different flavors of context url but not at the expense of seeing the repo info and being able to go to the repo. Based on the header, the column is supposed to be mainly about the repo.

7. Removes the repository URL in favor of the new combined context.
   jl - I don’t like losing the repo URL entirely - is it clickable to go to github? I would put this in bold at the top of the cell, not below the team/project.

8. Introduces project association.
   jl - nice idea - but what if the project is not visible? not sure if it’s easy to do -

9. Introduces team association.
   jl - nice idea - but how to handle if the team is not visible?

10. Nudges users to add repository as project when not added.
    jl - how would this work with teams? need to clarify the flow before committing to this.

11. Surfaces credits used per workspace.
    jl - this differs from the usage per workspace session - i think it will confuse users unless we make it clear that this is an aggregate when there have been multiple sessions/instances for one workspace e.g. by showing the breakdown or session count.

12. Changes orientation of the more actions dropdown button.
    jl - fine with this 🙂

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gtsiolis]

Closing in favor of UX-26.