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

WordPress Trac noreply at wordpress.org
Fri Mar 30 03:50:31 UTC 2018


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

Comment (by bph):

 After reading through [Jeff Chandlers tale]https://wptavern.com/my-
 gutenberg-experience-thus-far I have to admit, among us friends, the "Try
 Gutenberg prompt" has me a little worried.

 Most content creators just want to get their work done. And even if they
 are brave and go and try out things. They will get mad, when we let users
 install and activate Gutenberg, on live sites, when we '''know''' some of
 the plugins installed won't work and they won't get their work done.

       ''"People may not remember exactly what you did, or what you said,
 but they will always remember how you made them feel." --''

 Is there are way to warn a person before they install and activate
 Gutenberg, when they have plugins installed we '''know''' won't work
 (Publish Post Preview, or Switch Post Type)?

 Can we have a warning on the prompt, stating 1) it's still in beta, and
 they are part of a test.  Things might break and 2) if they are brave
 enough to try it, here are things that WILL NOT work? And make it
 individual to their own installation.

 I started a list of known Themes and Plugins that bomb, its rudimentary
 right now from various sources, with maybe a 14 - 16 items on it. I can
 certainly use the next couple of weeks to add to it, and maintain it also
 in machine readable form (json, csv, txt, whatever) so it can be polled by
 a script, that comes with the "Try Gutenberg" prompt.
 In essence, all you would need is the plugins' slugs in a list, I'd be
 happy to augment it with export of Daniels data.

 And this list gets better and better the more people try it and report.
 That way, we can warn the people of the potholes along the way regardless
 how fast the hick-ups can be fixed. The list of known plugins can be
 updated with every Gutenberg update.

 If the 'hard-hat-zone" searcher finds plugins installed from the list, the
 prompt could also just not appear.

 The goal of the prompt, as I understand is to find out how 'real users'
 (not experts) work with Gutenberg. It should give information about the
 use of editor itself. It would be a shame when we want to get users
 working with Gutenberg, yet some users, ready to help-out get discouraged
 just because we didn't warn them even if we could. And instead getting
 more user to help debugg the Gutenberg editors, we primarily collect
 tickets on incompatibilities. It has its own value, admitted, but do we
 need 'normal users' to get to this pain to discover them?

 I have a lot of empathy for users that can't get their work done because
 they didn't think twice and clicked on a nice blue button.

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


More information about the wp-trac mailing list