An Experimental Outreach Project for Full Site Editing

Update: following some discussion about themes as they relate to full site editing, I’ve extended the deadline for expressing interest in this program for an additional week, closing on 22 May, 2020. – Josepha

As we approach the second release of 2020 with an eye toward WordPress 5.6, I’ve got full site editing (FSE) on my mind. During the WordPress 5.0 retrospective, one of the things that came up routinely was the need for better engagement with users*. It was generally agreed (from all levels and areas of contribution) that users* will be most impacted by GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc., but that users* are also the group we have the least channels of communication to.

To help get user feedback to WordPress developers a little more seamlessly, I am going to try an experimental outreach project. With FSE set to launch by the end of the year, this experiment aims to get feedback about pain points to the right people faster and help keep us on track for Phase 2.

If you are interested in testing early versions of upcoming releases that will make FSE work better for you, your customers, or anyone who is building or maintaining a WordPress site, please fill out this interest form between now and May 14th. By filling out the interest form below, you’ll get more information about the program when it launches: 

Sign me up for more information!

I’m still working on the finer points of this experiment, but the intention is to use Gutenberg in as close to a client setting as possible. Time to provide feedback is flexible but could be up to 3 hours a week on average. Thanks in advance if you’re able to help us shape this work!

The interest form will be open until May 14th, 2020!

#testing #FSE

*Users can be defined in many ways, but in this case, I’m referring to those who build with WordPress (not those who build WordPress) and those who maintain WordPress sites (not those who visit sites).