Closed digitarald closed 8 months ago
To clarify, would the command just bring up the filtered keymaps extensions view?
One possible option would be an additional icon added the toolbar e.g.
We don't yet have the right icon in codicons so consider the new icon a placeholder for now
The command is workbench.extensions.action.showRecommendedKeymapExtensions
(Preferences: Keymaps)
One possible option would be an additional icon added the toolbar e.g.
I am skeptical that am icon solves the discoverability problem. The UI is already pretty dense and an icon might just blend in with everything. Could we explore a non-primary labeled button as well?
I agree. Without changing the existing toolbar I can see that the commands can also feature a label. However I've never seen this used in VS Code so I'm not sure it's the right way to go.
I'll take a look at some other options and will report back.
Oh ok, I see what you're referring to now re: Settings Sync. Hadn't noticed this since it's always been on for me :)
I realize this one is a bit of scope creep here. I'm actually curious how we're getting away without an H1 on this or similar pages. @misolori would you have any context there?
We tend to rely on the file tab as the "heading" for most of our single pages (settings, running extensions, etc.) and the extensions detail page is one of the exceptions of this:
Closing for now as we lost traction on this.
Usertesting showed that keymap extensions are not easy to discover due to a mix of issues. Users have many different terms for them, don't know that they exist or don't look in the right places.
To improve organic discovery the idea here is similar to Turn on Settings Sync button in Settings, showing a Migrate your Keyboard Shortcuts from other Editors in the Keyboard Shortcuts page.
To focus on new users, it could be hidden when a user installed a keymap.