[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 remediosgraphic):

 "How much information should be offloaded to the “Welcome to 5.0” post-
 upgrade page and what should we handle separately?"

  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.


     "Should we account for the prospective intent of some users to keep
 using the Gutenberg plugin?"

 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.


     "Should the message conveyed vary depending on a user’s installed
 plugins (Gutenberg, Classic Editor)?"

 The message can be the same but is important show on the welcome board the
 link to the classic editor plugin.

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