FSE Outreach Program: Overview & Outreach

After sharing a few posts on Make Test that I’d love to include this team on, @tobifjellner very kindly suggested I post directly on the Polyglot Team’s blog to better coordinate efforts. Thanks in advance for patience as this is a new area for me so if please correct anything I might be mistaken on.

What is the program?

The Full Site Editing (aka FSE) Outreach Program is an experimental outreach program whose goal is to improve the Full Site Editing experience by gathering feedback from WordPress site builders. This does not replace anyone giving feedback about the feature itself but is merely there to act as a coordinated and intentional effort. Ideally, by having more translations of resources around this program (calls for testing, handbook pages, etc) combined with liaisons this program can expand its reach beyond those comfortable giving feedback in English.

What needs help?

Pulling from this post, here are a few ideas of how I’d love help from the Polyglot team and/or those who are a part of their local community. You don’t need to take part in all of these ideas. Even just helping with one would be a huge help!

  • Translate this page on “How to test FSE” into your local community language so more people can participate. 
  • Translate future Calls for Testing and share your community’s feedback in the FSE Outreach Program in English. 
  • Facilitate testing in your community by following the Calls for Testing and translating the feedback into English either to share on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ or on the official Call for Testing post. 
  • Bonus idea: you can create content in your local language on Full Site Editing. Here’s an example from @overclokk who did a video in Italian talking about this feature

Props to @mimi who translated the “How to Test FSE” page for the Japanese community and @nobnob who translated an overview of the program into Spanish already.

Who can participate?

Anyone can participate. 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 not sure, join anyway and see for yourself. 

Where to find more information?

What projects on translate.wordpress.org need to be translated in order to have the experimental environment localized?

Currently, the program uses the Gutenberg Plugin and the TT1 Blocks theme for testing. This matches the minimum viable productMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia goal of building a site using the Twenty Twenty-One 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. theme with Full Site Editing without needing to alter code.

How to handle feedback in other languages than English?

Ideally, this is an area where we can have community members translate the feedback back into English. I’m very new to this space though so if there are other ideas or approaches, please let me know.

For official Calls for Testing, feedback is welcomed on the post itself (example) or in GitHub directly. For feedback outside of Calls for Testing, it’s best to share directly in GitHub but you can share in #fse-outreach-experiment or #core-editor first if you need a second opinion.

To close, I have a question: what resources can I create to help you all?

I’d love to do my part to make this easier to contribute to in the future so if there’s anything I can do or anything I can create let me know.

Thank you to @nao and @tobifjellner for reviewing this post.