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

 Thanks @matveb, that's all helpful. Here are some fairly subtle edits with
 all that in mind.

 [[Image(https://cldup.com/MkUf5KzTxW.thumb.jpg)]]
 ''Mobile: https://cloudup.com/cjNxnykw8SC''

 Revisions:

 - Added "is coming soon" to the main headline to make it clear that they
 should be expecting this soon. (I considered changing the sub headline to
 something along the lines of "Make sure your site is ready" but I wasn't
 sure if that was too scary or not?)
 - In the second column, revised the headline so that it sounds a little
 more serious: "Prepare for the transition."
 - In the second column, clarified that Gutenberg will be enabled by
 default in 5.0. More clearly explained the benefit of installing the
 Classic Editor plugin in advance.

 Is this enough?

 ----

 For simplicity's sake, if someone has already accomplished any of those
 actions, but not specifically dismissed the notice, I suggest we replace
 the appropriate column with an alternate set of content. Swapping out each
 column individually allows us to continue messaging the user regarding
 Gutenberg plugin if they've already installed the Custom Editor plugin,
 and vice versa. For example:

 ''Left column:''

 [[Image(https://cldup.com/NuteaDaxo8-3000x3000.png)]]

 ''Right column:''

 [[Image(https://cldup.com/nZdWdbrjOC-3000x3000.png)]]

 (Note that we don't currently have a "compatibility guide", but I think we
 should. 😄 I think to start, this could just be the "Compatibility"
 section from wordpress.org/gutenberg, moved into a dedicated section of
 the handbook.)

 ----

 > 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.

 > 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.

 I think the "Do Nothing" option is handled by dismissing the callout. If
 we want to be especially persistent, maybe we could adopt a modal or a
 follow-up callout when they dismiss the message:

 [[Image(https://cldup.com/aK_83sYe1I.gif)]]

 (Though I agree that's not a great experience.)

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