Keyboard shortcuts for all functionality of Dashboard + Admin Menu while in read mode

[tady]

I'm constantly hitting cmd+s (or meta+s) in the appearance file editor. I'm also constantly looking for a short cut to preview or publish a post. Aside from the accessibility assistance, I think an addition like this would make WordPress very "Power User" friendly. I know the meta+s command works in the post/page editor but the interaction is so subtle, I'd to do it a few times before I saw the "Draft saved..." comment at the bottom. I had a notion that something like meta-key + down arrow might overlay a set of keyboard instructions. Things like "cmd/ctrl + s = Save Draft, cmd/ctrl + shift + L = Preview Post, cmd/ctrl + p = Publish Post/Page" etc. Obviously, this needs work.

Is this something in the pipeline? If not is this something I can propose?

[atomicjack]

Already a feature, just you're wanting it extended. :)

[tady]

Yes, I suppose it is! Thanks! :D

[iandunn]

​Hotkeys are becoming more commonplace in rich web applications, and I think users could benefit a lot from more support in Core.

If new hotkeys are added, it'd be very useful to have a ? hotkey, which could bring up a dialog showing a reference table of all other hotkeys (both global, and for the current screen), so users don't have to memorize them. It could potentially show hotkeys registered by plugins, too (maybe even automatically via jQuery.hotkeys, instead of a manual registration step).

I think they should all be enabled by default (related #21414), because that'd be more convenient for people who want to use them, but generally wouldn't interfere with those who don't.

[iandunn]

I also think that hotkeys for navigating through screens could be very useful, since it's fundamental to everything, but tedious and slow with a mouse and a long list of menu/content items, particularly when you have to visit an intermediary screen (e.g., All Posts) in order to bring up the desired screen (e.g., a specific post).

An intent-driven keyboard interface (like Spotlight in OS X, or ​the HUD in Ubuntu) that searches an index of menu items and content could allow users to skip intermediary screens entirely, and also make it quicker and easier to find what they're looking for.

There are several plugins in this space [​1, ​2, ​3, etc], but I think it's worth considering whether it makes sense to have some support for it in Core.

[afercia]

Discussed today in the accessibility weekly meeting and as long as shortcuts are on a per-user basis and off by default, there are no objections :) For some background, see #21414.

[iandunn]

Reopening because I think this is still worth considering.

[iandunn]

GitHub ​recently launched an intent-driven interface.

[iandunn]

​Chrome DevTools also has one, accessed with cmd shift p.

[abitofmind]

👆 Extended scope of the original issue title and reflected this in the new title.

I think the time is ripe to consider implementing this!

• The Gutenberg Block Editor now has centralized and very extensive ​keyboard-shortcuts using ​Mousetrap.
• Real efficiency and UX improvement for Pro users! And meanwhile standard in mainstream web apps!

I hope it is ok that I used an existing issue for this

• I think it makes little sense to create the "Admin Menu" aspect of shortcuts as a separate issue.
• This is a wholistic matter: Shortcuts outside of the Gutenberg Block Editor lifecycle.
• In addition to the scope of the Dashboard also while viewing a page/post in read mode and being logged in, it would be great to quickly trigger the commands available in the admin menu (also when the menu's position/visibility/style is altered by a plugin such as ​Better Admin Bar)

From the reading context directly to the intended creative/editorial/administrative action

• Edit Page (e.g. E or ⌘ E) -- Most important one -- Always catch myself doing this (habit from ​Confluence)
• Create New Post -- Also quite frequently: Reading existing content gives idea for new/missing post/page.
• Create New Page -- Maybe as a distinct command, or a general "Create New" command which opens an intermediary popup for choosing the content type (again keyboard accessible).
• Open Dashboard
• Open Comments
• etc

[joedolson]

On reading through this ticket, I'm inclined to close it. This isn't because there isn't a benefit to improving support for keyboard shortcuts in core; it's because this ticket is so incredibly broad that I'm not convinced that it's actionable as it is. "Reading context" isn't a clearly defined thing; I'm honestly not sure what context you're actually requesting here.

The WordPress editor's command palette provides this context when in the editor, and in the future admin redesign, that palette would be available in all panels using the new admin, so this is on a roadmap.

For the classic admin, I think that requests for new keyboard shortcuts need to be more discrete: open tickets requesting a specific keyboard shortcut, in a specific context or contexts. That will make this something that has a better chance of creating change.

[abitofmind]

"Reading context" was possibly a misnomer. "Read mode" probably more common and fitting here.

As the changed title says:
Keyboard shortcuts for all functionality of Dashboard + Admin Menu while in read mode

So a scope which encompasses broadly all modes of operation of your role as editor/admin where NO active editor UI is open, but instead content in read mode is or certain overviews open, and from this context you want to quickly trigger your shortcuts.

In that scope no text area or input elements are active, thus A-Z keys without modifier keys could be used to trigger commands.