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

 Replying to [comment:28 dd32]:

 Thanks for the comment. First of all, my apologies to all involved in this
 ticket, as I should have corrected its course earlier.

 > Unfortunately at present we don't have the ability to customise the
 display of the update message about the upcoming release in previous
 WordPress versions.

 This was one of the things for which I needed to set time aside in order
 to better understand core's upgrade process. Indeed, any change in the
 pre-upgrade copy would require a 4.9.9 release, which I would really like
 to avoid for many reasons.

 **As such, we need to say no to any sort of messaging in core that happens
 before the upgrade.**

 > The post-upgrade screen should be a celebration of the new editor, it
 shouldn't be giving the feeling of half-baked or "you probably don't want
 this" which I'm getting from the proposed changes.

 I agree that a better balance is needed here. The starting focus of this
 ticket was the flow moreso than the copy, but it's time to look at that
 now.

 > Asking the user immediately after updating feels like the wrong time to
 be asking this, it's just way too early.

 Agreed.

 > The user is unlikely to be informed and probably doesn't know what
 "Gutenberg" is anyway (either by codename, OR by using it).

 The name Gutenberg should probably be left out of the messaging ''unless''
 a user has the Gutenberg plugin installed. At most, it should be mentioned
 as a codename when pointing to a canonical reference such as
 wp.org/gutenberg (e.g. "Read more about WordPress's new block-based
 editor, codenamed Gutenberg, […]").

 > Seems like the Classic Editor plugin should definitely add a note to the
 post-Upgrade screen '''and''' to the new-post screen to mention that it's
 active, and it's changing the experience the user will get.

 I think a lot should be offloaded not just to Classic Editor, but also to
 the Gutenberg plugin. Actually, this is in line with:

 > I'd suggest something like this: (of course, this needs a lot of word-
 smithing)
 > > The Gutenberg plugin has been deactivated, as the features are now
 included in WordPress 5.0 by default. If you'd like to continue to test
 the upcoming changes in the WordPress Editing Experience, please
 [Reactivate the Gutenberg Plugin].

 **Setting aside the technical means and recapping in terms of user
 interactions, the bulk of these should be limited to the post-upgrade page
 and timely WP-Admin notices. I can see the Help drawer be updated to
 provide context for the user, but this should be dealt with separately,
 likely led by the Docs team. I'm not sure about Screen Options.**

 Finally, I think we can separate responsibilities a little:
 - Classic Editor could absorb some of the communication seeking to assuage
 the user who is afraid to upgrade or to lose legacy functionality. It
 could even reach out to the user, once 5.0 is out, pre-emptively informing
 of this available upgrade even if the user isn't looking at the Updates
 page.
 - The Gutenberg plugin would make its own case to its users, informing
 them that they can get on the Beta track by reactivating it.
 - Thus, changes in Core would mostly be limited to the post-upgrade page,
 which gives us a nice narrower scope but also, personally, greater
 confidence that we aren't "tainting" core's upgrade process with new
 logic.

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