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

[WordPress Trac]

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

Comment (by andrew.taylor):

 Howdy,
 I've been testing WordPress 4.9.8 on Pantheon in preparation for the
 release at the end of the month. First, I would like to say that I
 appreciate the work that has gone into this initiative. The thoughtful
 design and desire to give users a great experience is inspiring.

 In this testing I noticed two items I would like to provide feedback and
 have a discussion around.

 How do others plan to handle the call to action to install Gutenberg when
 users have another environment, such as a staging environment, available?
 I think ideally users should test Gutenberg outside of production, rather
 than on the live site.

 Currently, the options I see, are to append more panel content with the
 `try_gutenberg_panel` action or use that same action to completely remove
 the existing panel. I am leaning towards the latter in our production
 environments.

 However, removing the call to action all together does not seem ideal so I
 welcome feedback on how to best address this situation for our users.

 Perhaps we can still ''inform'' users of Gutenberg in production but keep
 the call to action to install Gutenberg limited to non-production
 environments.

 I recognize some users don't have access to multiple environments and when
 they do each host has a different setup. While I don't expect core to
 address every case some additional filters hosts can use for these
 different scenarios would be most welcome.

 The second thing that will be very confusing for our users is that the Try
 Gutenberg callout suggests installing Gutenberg even when WordPress cannot
 write to the plugin directory (see
 https://wordpress.slack.com/files/U02RRBCRW/FBW485Q9K/try-gutenberg-no-
 write-access-failure.mp4).

 Pantheon test/staging and production environments, as well as development
 environments in Git mode, are not writeable outside of `wp-
 content/uploads`. Additionally, in our test/staging and production
 environments, users can not make changes without doing a deployment from a
 development environment so asking them to provide FTP credentials would be
 equally confusing.

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