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

 > Does that mean that warnings will continue to be displayed forever?

 @blvtomoya - @JoshuaWold and I worked on update to this user flow
 yesterday... I think he'll be posting it sometime tomorrow. The suggestion
 we've agreed that makes sense here is to nudge a user in the right place
 (e.g. on the "5.0 Welcome" screen, perhaps on the main dashboard, etc.)
 there would be dismissible notices that encourage sites to try Gutenberg.
 I think it's important to encourage, but not to force, users to try the
 new editor. We also think it's important to tailor the messages on the 5.0
 Welcome page based on path that site is in the userflow presented. In
 short, some sites are ready to dive deeply into Gutenberg, others will
 take a while to get there. (We hope not too long.)

 Also, a heads up - there's a mistake in the current sketch in flow 2 that
 reads:
 > Would you like to try the new editing experience? Requires deactivating
 classic editor plugin.
 This would appear in Classic Editor, probably above a post.

 Just as you can now use both the Classic and Gutenberg editors in a paired
 mode, you'll be able to do the same from 5.0. Our suggestion would be that
 another encouragement would appear ''n'' # of times (three?) but also be
 dismissible probably though a toggle in `Screen Options` as is the pattern
 to hide/show things in the current interface for WordPress. But if it's
 not for you yet, that's fine too.

 We believe W.org's intent is to show that Gutenberg provides great value,
 and we there's an important effort here to provide enough of a way for
 sites to hold off if they need to, hence the reference to
 [https://github.com/Automattic/gutenberg-ramp Gutenberg Ramp] earlier,
 which takes the Classic Editor controls and expands them a bit further to
 encourage an opt-in experiences for sites that need that functionality
 fully.

 @mcsf - Speaking of which, we'll take the discussion regarding Ramp to the
 appropriate repo to focus this discussion :)

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