Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve UX of completed and hidden items and the recent workspaces list #120855

Closed
miguelsolorio opened this issue Apr 8, 2021 · 2 comments
Closed
Assignees
Labels
getting-started insiders-released Patch has been released in VS Code Insiders ux User experience issues
Milestone

Comments

@miguelsolorio
Copy link
Contributor

Overview

This is to track improving the way that Getting Started items are displayed when there are no items left.

Concept

One idea is to shift the content to make better use of the space. This would move the "Recents" list to the right and place "Getting Started" below it. We'd also have some way to trigger resetting items if someone accidentally dismisses one.

CleanShot 2021-04-08 at 11 53 01

And in the case we want to have a setting to completely hide "Getting Started", it would like this:

image

@JacksonKearl
Copy link
Contributor

Currently:
image

image

image

Using a top-level "configure" button as opposed to one mounted on the getting started list, could go either way with this. I was thinking that once we add a section for changelogs it'd be nice to have a single way to configure everything, though that might be confusing... will revisit when the time comes.

@JacksonKearl
Copy link
Contributor

An aside, it could be neat to render the recent list more like the getting started tiles, perhaps with an icon corresponding to the remote provider, or if its a file vs workspace vs folder or something.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
getting-started insiders-released Patch has been released in VS Code Insiders ux User experience issues
Projects
None yet
Development

No branches or pull requests

3 participants
@JacksonKearl @miguelsolorio and others