[wp-trac] [WordPress Trac] #41316: Introduce "Try Gutenberg" callout

[WordPress Trac]

#41316: Introduce "Try Gutenberg" callout
---------------------------------------+-----------------------------
 Reporter:  melchoyce                  |       Owner:  pento
     Type:  task (blessed)             |      Status:  reopened
 Priority:  normal                     |   Milestone:  4.9.8
Component:  Editor                     |     Version:
 Severity:  normal                     |  Resolution:
 Keywords:  has-patch has-screenshots  |     Focuses:  administration
---------------------------------------+-----------------------------

Comment (by matveb):

 Great to see these mockups! Going over the goals a bit so we can clarify
 the choices.

 - Introduce users to the upcoming new editing experience.
 - Allow them to be prepared before 5.0 happens.

 There are two main goals, one which is informative, and one that might
 require some action from the user. The possible choices would be:

 - Install the Gutenberg plugin.
 - Install the Classic Editor plugin.
 - Do nothing.

 Let's go over how each should generally work.

 **Install the Gutenberg plugin** — the user gets access to the new editor
 and potentially the notice disappears. I say potentially because we also
 need to consider what would happen when a site running Gutenberg is
 updated to 5.0 (like deactivating the plugin), which also depends on
 whether all the current features from Gutenberg are included. Maybe a
 small notice that you are running the plugin could be good?

 **Install the Classic Editor plugin** — I think the emphasis should be on
 allowing people to set their sites up ''in advance'' of 5.0, so when it is
 released they don't have to rush or do anything at the last minute to
 retain the Classic experience if that's what they wanted. It's a sort of
 early opt-out that should give more confidence to site maintainers.
 Installing this should dismiss the admin notice.

 **Do Nothing** — should be clear to people that with this option the
 editing experience will change when the site is upgraded to 5.0 but that
 they can install Classic at any point.

 ----

 With these considerations, I like the last proposal.

 However, without going too much on a tangent, perhaps it's worth
 considering a two-step approach. The informative notice and a "what do I
 need to do?" modal / action. This sounds potentially complex and not
 necessarily a better user experience, but wanted to mention it anyways.

 ----

 How much do we want to show the term "Gutenberg" here? Maybe in titles we
 just say "Test the new editor today", for example.

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