Change Keyboard Shortcuts editor button into general Editor Help

[ericlewis]

The Keyboard Shortcuts help modal in the Post Editor includes not only shortcuts, but also information about how the automatic replacement of certain characters works (e.g. typing ## turning into Heading 2).

We could rename this button "Editor Help," since it's not just Keyboard Shortcuts. And also add some more useful information:

• How Shift+Enter creates a line break instead of a new paragraph.
• Information about using oembeds

[azaozz]

We actually had more extensive editor help for quite a while. The modal had an iframe loading a separate PHP file.

However found out that very very few users ever look there. The decision at the time was to leave only the keyboard shortcuts as they are the most essential. Later on the focus shortcuts and the formatting shortcuts were added.

Adding a little bit more there is a good idea, but still need to keep it "short and sweet" if we expect the users to read it.

Another idea was to open the help modal when a new user visits the Edit post screen for the first time. It didn't happen at the time as it is "too intrusive" to have a modal covering the screen. Now there are many sites that show "blocking" adds on loading, maybe can revisit?

[desrosj]

Since the introduction of the block editor, the Classic Editor is now in bug fix only mode. Going to close this out as a wontfix. If this is still relevant, an issue should be created upstream in the ​Gutenberg GitHub repository so a solution can be explored in the context of the block editor.