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.
If you’d like to help test Full Site Editing, please join the FSE Outreach Program. You can find current calls for testing for this program here and you can join the fun in #fse-outreach-experiment.
This is a FAQ for the Full Site Editing Outreach Experiment. If you have a question to add to this document, please share it in #fse-outreach-experiment in WordPress slack.
What is the goal of this outreach program?
Previously, the goal was to improve the Site Editing experience by gathering feedback from WordPress site builders. When Phase 2 was completed with WordPress 6.3, the goal has shifted to focus on improving adoption of the Site Editor and 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. themes by having it transform into a focused space for solving issues, creating resources, and facilitating conversations related to adoption.
What led to this program being created?
For big picture context, Site Editing was a major part of Phase 2 of Gutenberg. Inspired by the constructive feedback following the 5.0 release, this experiment started as an effort to elicit early and frequent feedback from users in advance of future major releases. In its current form, it’s in place to help aid the adoption of all things phase 2.
Why is it an experiment?
Because something like this has never been tried before for gathering feedback in this way. Thanks to the original format, it has built in flexibility to the approach, allowing the program to evolve as it’s needed to alongside the software.
How long will this experiment run for?
The program started in May 2020 and ran for nearly three 3.5 years in the form of a feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop., education, and awareness building space around Site Editing. Going forward, in line with this evolution, the following timeline is in place:
Is this the only way to give feedback about Full Site Editing?
No—This is WordPress after all. You’re welcome and encouraged to share your feedback on GitHub as this program is meant to supplement not replace the current feedback pathways.
What kind of folks should join this program?
If you build with WordPress for others (compared to those who build WordPress) and/or maintain WordPress sites (compared to those who visit sites) and/or who create content, this program is a great fit. If you’re curious about the Site Editor and adopting block themes, it’s also for you. If you’re not sure, join anyway and see for yourself.
How can I join this program?
Simply create a WordPress slack account and join the channel #fse-outreach-experiment.
What do I need to join this program?
A curious, kind mind that wants to learn about what’s possible today in WordPress.
Where will the results of this program be published?
All posts will be shared on the Make Test Blog with cross posts to Make Core Blog using the following tags for ease of use:
All calls for testing and summaries have been shared on Make Test. Here are the tags you can use to follow along specifically:
If you’re in the #fse-outreach-experiment channel, the posts will also be shared there for ease of access.
Last updated: