Document known changes in editor behavior

[danielbachhuber]

As a user switching from the Classic to Gutenberg editor, it would be helpful to have a documented list of UX changes so I can know which changes are intentional vs. which might be bugs. My expectation, as a user switching from one to the other, is that they're as consistent as possible.

A non-exhaustive list of changes includes:

• Using the tab button no longer indents an ordered or unordered list Tab unexpectedly highlights "Add block" instead of indenting unordered list #4181
• Many buttons have been removed from the text formatting toolbar, including text color Need of TextColor for inline formatting (single words/characters) #6080
• Some HTML attributes and additional markup are stripped from blocks Allowable tags gettings stripped from Header blocks when drafts are auto-saved #5876 Converting a table in a classic block to a table block removes all inline styles #6096 Converting To Blocks Looses Existing Anchor Tag Parameters #4498
• Text content is automatically wrapped with <p> tags Should Gutenberg continue to automatically add <p> paragraph tags? #4446 (comment)
• Hidden metaboxes no longer exist Force the display of hidden meta boxes #7570

Previously #4181

Related:

• Document WordPress classic editor integration points and Gutenberg equivalents Document WordPress classic editor integration points and Gutenberg equivalents #4151
• https://github.com/danielbachhuber/gutenberg-migration-guide

[youknowriad]

My expectation, as a user switching from one to the other, is that they're as consistent as possible.

While I'm not sure I agree with this statement as we're trying to improve the editor so being consistent is not a goal in itself but yeah we should educate users and NUX #3670 #4173 is part of the solution here.

[danielbachhuber]

While I'm not sure I agree with this statement as we're trying to improve the editor so being consistent is not a goal in itself

Maybe a better way of phrasing is:

Any editor UX changes are deliberate and documented. Those that aren't can be considered bugs.

The default should be consistent behavior between editors, except where a deliberate decision has been made to change the behavior.

[danielbachhuber]

@chrisvanpatten volunteered to help get this over the finish line. We can use https://github.com/danielbachhuber/gutenberg-migration-guide as a starting point for these details.

[designsimply]

@danielbachhuber what action is still needed for this issue. Since 11252 and 11251 each mention documentation sections such as "What's different about the new editor?" and "Important deprecations/changes from 4.x" respectively, can we close this issue in favor of finalizing work in the new issues?

[danielbachhuber]

Since 11252 and 11251 each mention documentation sections such as "What's different about the new editor?" and "Important deprecations/changes from 4.x" respectively, can we close this issue in favor of finalizing work in the new issues?

Sure, that's fine. It seems like moving chairs around though.

[designsimply]

Cool. It looked to me like several things had already been addressed in closed PRs and I am working to consolidate issues where possible. Thank you!