[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-           |     Focuses:  administration,
  screenshots                        |  privacy
-------------------------------------+-------------------------------------

Comment (by kjellr):

 > @kjellr's tablet/mobile designs from 122 seem to be based on the earlier
 designs, so I haven't tried to implement them. The responsive CSS is
 currently super tiny, so there's no issue with deleting that and doing
 something completely different. 🙂

 Now that we're working with those two columns, I think removing the image
 at tablet breakpoints makes sense. We ''could'' keep it in on small
 screens, but I like the idea of leaving it out to save people some
 scrolling. So what you've got above looks good to me!

 > We're still using the old image in the first column. @kjellr, could you
 upload a copy of the image you'd like to appear there? It can be static or
 animated.

 Here you go!

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

 I think that version should work ok if we're only using it on desktop
 screens, but here's an even higher res version just in case:
 https://cloudup.com/ifFhSdLadMG

 > I'm inclined to agree with @chanthaboune's comment that the third column
 heading needs work, but nothing was jumping out at me, so I left it as is.

 I like @michelleweber's suggestion: "Get your site ready for the switch.",
 through we could possibly remove "for the switch" and keep it more
 concise. I also like the new body copy for that column.

 > I haven't implemented the extra notice when the box is dismissed. I'm
 wondering if a better option for a "second chance opt out" here would be
 to implement it into the 5.0 upgrade flow, or when someone first visits
 the block editor after upgrading.

 Agreed – integrating that message elsewhere sounds like a more elegant
 solution.

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