429 Too Many Requests

Welcome

The Test Team helps manage testing and triage across the WordPress ecosystem. They focus on user testing of the editing experience and WordPress dashboard, replicating and documenting bug reports, and supporting a culture of review and triage across the project.

Weekly Meetings (Calendar)

Bi-Weekly Test Team Chat: Wednesday at 16:00 UTC
Bi-Weekly Test Team Triage: Wednesday at 16:00 UTC

You can join these meetings from the #core-test Slack channel.

Please drop by any time in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. with questions or to help out.

This post is a summary of the fifth call for testing for the experimental FSE outreach program. Thank you to everyone who participated, whether through testing directly or sharing the call for testing with others. It all helps! Special thanks to the following people:

@piermario for translating the call for testing into Italian!
@ippei-sumida and @mimitips for facilitating testing with 30+ people in the Japanese WordPress community resulting in 40+ items of feedback.
@bobbingwide for making two different videos going through the test using only his keyboard.

A few reminders:

Round two of a call for FSE related questions is currently underway, so join #fse-outreach-experiment in slack and/or subscribe to this Make blog and stay tuned for more.
The sixth call for testing is planned for May 12th.

What’s next for the Query BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.?

For anyone interested in the future of this powerful block, check out this overview issue tracking future improvements planned for 5.8.

How far can one go?

Since this was a more open ended call for testing with options to go further in the Query Quest if one chose to do so, it’s neat to see the directions people went. In particular, the following from @webmandesign shows a lovely take on the call for testing both in terms of the design and because @webmandesign went beyond the initial scope of the instructions: