Replace screenshots of Radio Control

[krokodok]

What?

Replacing screenshots showing a wrong component with the right one, as discussed in #28763.

Please help

Could someone take my two files

• https://raw.githubusercontent.com/krokodok/gutenberg/b3bfe9b6ce458de792595f863df1412975d1c714/do.png
• https://raw.githubusercontent.com/krokodok/gutenberg/b3bfe9b6ce458de792595f863df1412975d1c714/dont.png

and upload them to the make.wordpress.org server and then change the URLs in the README file? I looked through the repository into other README documents, and there do not seem to be other cases of GitHub hosted images.

Also, since the last time I commented on the original issue with screenshots, GitHub changed the visibility of GitHub hosted images. Because I created new screenshots today, that contain the big, coloured "Right" and "Wrong" indicators, I can't "host" them on GitHub via a comment on the issue, as previously. The files now live inside a branch in my fork, which is not optimal, since this could be deleted some day!

Why?

The old screenshot was not showing the RadioControl component but a custom one instead.

How?

The screenshots are replaced.

Testing Instructions

n/a

Testing Instructions for Keyboard

n/a

Screenshots or screencast

Old

New

[mirka]

since the last time I commented on the original issue with screenshots, GitHub changed the visibility of GitHub hosted images.

I see! From what I can tell from the docs and actual behavior though, the new file access restrictions are only for private repositories, not public ones like Gutenberg. The URLs we get are now github.com/WordPress/gutenberg/assets/* that redirect to the actual file, instead of a direct user-images.githubusercontent.com link.

For example, I attached your images to this comment, and the URLs should be accessible in an Incognito tab without authentication:

• https://github.com/WordPress/gutenberg/assets/555336/4a373812-d85c-4f10-83b9-775c1b575bce
• https://github.com/WordPress/gutenberg/assets/555336/8d86ea71-4f33-4aac-980d-05425b0f40d3

We are starting to use more GitHub hosted images for our docs, since it's a lot easier to maintain.

[krokodok]

Thank you @mirka, I just tried it with the dynamic generated URLs. With the static "permalinks" everything works fine.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Unlinked Accounts

The following contributors have not linked their GitHub and WordPress.org accounts: @lmartins.

Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Unlinked contributors: lmartins.

Co-authored-by: krokodok <[email protected]>
Co-authored-by: mirka <[email protected]>
Co-authored-by: dhruvkb <[email protected]>
Co-authored-by: ryanwelcher <[email protected]>
Co-authored-by: benlk <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[ajitbohra]

👍

[mirka]

Perfect, thank you for the quick responses!