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

WordPress Trac noreply at wordpress.org
Tue Oct 17 11:29:08 UTC 2017


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

Comment (by pento):

 Replying to [comment:33 celloexpressions]:
 > What are the usability implications of putting a large screenshot of wp-
 admin at the top of the dashboard? At first glance this seems confusing
 and disorienting for new users especially.

 The design leads of Gutenberg and the 4.9 release are cool with it, I'm
 going with their recommendations. We'll also be updating the screenshot
 regularly.

 > What is the status of guaranteeing backwards and forward compatibility
 for content created while the plugin is active and continues to be evolve?

 Backwards compatibility already works. The format can be easily changed in
 a backward compatible way, and can be versioned if it doesn't. Similarly,
 it can be forward compatible if we add versioning to Gutenberg now, but
 it's not a high priority.

 > There should be a make/core post addressing this issue

 That's part of a post I'm in the middle of writing.

 > Is it appropriate to refer to this as "gutenberg" in code, or in
 database fields (as user meta)? Note that [attachment:41316.8.diff] still
 uses "Gutenberg" in some user-facing text. From a core perspective, this
 word is unlikely to ever mean anything once it's eventually merged -
 should it be described that way now?

 It's fine to call it Gutenberg, because that's what it's referred to
 everywhere - the plugin name, the repo name, news articles. Changing it to
 something more generic is unnecessarily confusing.

 > Why is there an `@since 4.9.9` in [attachment:41316.8.diff]?

 Well, I was going to leave that function out until WordPress 4.9.9, but I
 guess we can put it in 4.9, instead. 😉

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


More information about the wp-trac mailing list