[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
Component:  Editor            |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  has-patch commit  |     Focuses:  administration
------------------------------+-----------------------------

Comment (by johnjamesjacoby):

 Is it too late to make the code around this non-specific to Gutenberg? My
 concern is that the current approach is not scalable to future feature
 developments beyond Gutenberg.

 For example, when a new codenamed feature comes along for WordPress 5.2,
 cloning this same approach does not seem ideal. Also, when Gutenberg ships
 with WordPress, are we going to (can we) really strip all of this work
 back out, only to put it back in again for another flagship feature?

 The one technical concern I have with the current approach, is that
 Dashboard meta-box names will now be a constantly moving target on a per-
 release basis. This places unwelcome overhead on the managers of all
 existing WordPress installations who will want to protect their users from
 seeing these ever-changing pitch statements.

 Also, the multitude of admin area "White Label" type plugins will need to
 more frequently update the disallowed meta-box names for each feature, and
 maintain their own per-version dictionary of what boxes to remove when.

 ----

 If this mock meta-block is to stay (which I am really neither for nor
 against) my preference would be that it be reinvented as a "teaser" box –
 not a Gutenberg specific one – and that the related code become a bonafide
 full-time part of the Dashboard experience like has been done successfully
 with the Community meta-box. This way, we can hype the new hotness on an
 as-needed basis, and plugins that want to hide it forever can reliably do
 so 1 time in a plugin.

 I see 260 references in trunk to `gutenberg` already, so I know it won't
 be quick or easy to refactor this code during beta/RC, but I feel pretty
 confident the current approach is not the best version of what this should
 be, and may accidentally cause undue stress and harm to users and
 developers in the long-term.

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