[wp-trac] [WordPress Trac] #45073: Upgrading to 5.0 and handling the Gutenberg plugin

[WordPress Trac]

#45073: Upgrading to 5.0 and handling the Gutenberg plugin
-----------------------------+-----------------------
 Reporter:  mcsf             |       Owner:  mcsf
     Type:  defect (bug)     |      Status:  assigned
 Priority:  normal           |   Milestone:  5.0
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  ux-feedback      |     Focuses:
-----------------------------+-----------------------

Comment (by JoshuaWold):

 @mcsf

 > In flow 4, it may not be immmediately apparent that last two
 illustrations show notices rendered by Classic Editor and not core, the
 same ones that were deleted in flow 2. It makes sense to show them in the
 flow, but maybe the document can highlight their source.

 Updated in the attachment below. What do you think?

 > Flows 3 and 4 haven't addressed the question of visibility around a
 What's Next tab. I don't mind having that tab there, but wonder if instead
 another notice might be a more flexible and visible mechanism.

 This may be lame, but we could put an icon beside the "What's Next" label,
 or change the background color to make it stand out more. Beyond that we
 could add a section below the what's new paragraphs, highlighted like an
 alert, offering the message to re-activate Gutenberg. Thoughts?

 @remediosgraphic

 Thanks for jumping in with feedback. It's much appreciated!

 > WP 5.0 have a big visual change on WordPress content creation, so let
 every user know again about this is very important. A link to how
 Gutenberg work and how install the classic editor is a must.

 On Path 1 where would you propose putting in this message, and what would
 the message look like?

 > As Gutenberg is native on WP 5.0 the update should deactivate the plugin
 by default. Manually deactivate this is more clicks and work for the user.

 I believe this the case, as proposed in Paths 3 and 4. Am I missing
 something?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/45073#comment:37>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform