WordPress.org

Make WordPress Core

#43614 closed task (blessed) (duplicate)

Tweak the Dashboard Gutenberg callout

Reported by: pento Owned by: pento
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: Cc:
PR Number:

Description

There are a couple of tweaks to be made to the callout.

The GIF we have loaded is showing a pretty old interface, we should replace that before 4.9.5 is release.

https://s.w.org/images/core/gutenberg-screenshot.gif

Also, @nikolam noted in Slack that he was confused by the similarity of the "Install Today", "Activate Today" , and "Try Today" messages on the button. @melchoyce, @karmatosed, do you have thoughts on this?

Attachments (4)

43614.diff (978 bytes) - added by pento 20 months ago.
Screen Shot 2018-03-26 at 12.45.38 pm.png (176.4 KB) - added by pento 20 months ago.
43614.2.diff (1.9 KB) - added by pento 20 months ago.
43614.3.diff (3.6 KB) - added by pento 20 months ago.

Download all attachments as: .zip

Change History (16)

#1 @pento
20 months ago

  • Owner set to pento
  • Status changed from new to accepted

This ticket was mentioned in Slack in #core-editor by pento. View the logs.


20 months ago

#3 @Clorith
20 months ago

If we're looking at tweaking it, perhaps taking a second look at pushing people towards GitHub as well?

GitHub is fine if you're a developer, but if you are an end user, which is a large part of our target audience with the callout, it's an unknown place with more "techy" users for the most part.

When wanting to share an enhancement on GitHub, you need to go to Issues > New Issue (I didn't have an issue, I had an idea). You are then greeted by a two-page scroll of pre-filled text in, many of the parts would make no sense to a non-developer.

When you read the description on GitHub, it's pointed out that the easiest way to give feedback is in the #core-editor slack channel (we're now sending them back again, to a place without any real moderation I might add), and requiring them to make a .org account in the first place.

Perhaps it's more sensible to direct them to the Gutenberg plugin forums? They would still need a .org account, but it's one step instead of 3. It's also a plain text form which many users are familiar with, and it has moderation tools (after all, experience shows that passions run hot in times of change).

#4 @bph
20 months ago

I would suggest a simple change in this sentence: "WordPress is working on a better way to control your content. How about giving it a try early?" and add "for you" and make WordPress be more like a group of people.

It could read "WordPress developers (or contributors) are working on a better way for you to control your content. How about giving it a try early?"

Without the "for you," it reads a little bit like the overlord wants to control my content. And it might help if users that are people behind the software working for people, rather than being this corporate entity.

#5 @afercia
20 months ago

Without the "for you," it reads a little bit like the overlord wants to control my content.

@bph you made a point here :) I can easily imagine slightly incorrect translations in other languages might turn this message in something a bit worrying. Ideally, the original English text should be as clear as possible to avoid the risk.

#7 @afercia
20 months ago

The previous GIF file size is about 1.5 MB, the new one about 1.2 MB. To my knowledge, since it's used in a <img> element, browsers will always load the image, even in the responsive view when it's not actually displayed. I'm not sure there are ways to avoid this other than JavaScript hacks. I'd rather consider to use it as a background image set only in a CSS media query for large screens, if possible. Browsers are able to determine which assets to load based on media queries.

@pento
20 months ago

@pento
20 months ago

#8 @pento
20 months ago

I've updated the image on the CDN. For those playing along, note that it might not update on your Dashboard until tomorrow: it's using the date as a cache buster, and the CDN caches very aggressively.

In 43614.2.diff:

  • Use the <picture> element to only load the image on larger screens, I've tested that this works correctly in Chrome, Safari, and Firefox: the image file is only downloaded when the screen width is greater than 1024px.
  • Add "for you" to the middle column.
  • Add a "Need help? Head over to the support forums." point to the get involved list.

@melchoyce: What do you think of the screenshot above?

#9 @Ov3rfly
20 months ago

  • Keywords gdpr added

The current user IP address and browser information is sent to a third party (CDN) by visiting the WordPress dashboard.

This might be an issue for #gdpr-compliance.

#10 @pento
20 months ago

Thanks for the input, @Ov3rfly.

This is the same CDN and data as you mentioned in #43631. Rather than trying to do a half-baked solution for it on this ticket, let's keep the GDPR work in #43631.

This ticket was mentioned in Slack in #core by audrasjb. View the logs.


20 months ago

@pento
20 months ago

#12 @pento
20 months ago

  • Keywords needs-design gdpr removed
  • Milestone 4.9.5 deleted
  • Resolution set to duplicate
  • Status changed from accepted to closed
  • Version 4.9.5 deleted

As the callout won't be in 4.9.5, I'm closing this ticket in favour of continuing on the original, #41316.

Note: See TracTickets for help on using tickets.