FAQ for FSE Outreach Program

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 experimental outreach program?

The goal is to improve the Full Site Editing experience by gathering feedback from WordPress site builders. 

What led to this program being created?

For big picture context, Full Site Editing is a major part of Phase 2 of Gutenberg. Inspired by the constructive feedback following the 5.0 release, this experiment is an effort to elicit early and frequent feedback from users in advance of future major releases.

Why is it an experiment?

Because something like this has never been tried before for gathering feedback, and Full Site Editing itself is still in progress. This builds flexibility into the approach and lets the program evolve as it needs to alongside the software. 

How long will this experiment run for?

The ending point of this program isn’t decided yet, but it definitely will end. Nothing lasts forever! It’s important to note though that the program will err on the side of sticking around for too long rather than ending it early. 

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 feedback is this program looking for?

This program aims to get feedback on everything from workflow changes (ie something that used to take three clicks now takes six) to general bug reports to “wish list” items people want to see. 

What kind of users 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 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. 

Are there any other ways I can help with this program?

Outside of testing, a big way to help is to share the calls for testing with your networks! Otherwise, there are three additional “roles” that the program could use help with:

  • Help with writing the calls for testing and the summary posts.
  • Help with wrangling responses to the feedback received whether that means responding to comments, creating GitHubGitHub GitHub is a website that offers online implementation of git repositories that 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/ issues, etc.
  • Help with amplification by sharing the calls for testing and summary posts in appropriate channels.

If you’re interested in any of these roles, please pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” @annezazu in WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ 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/.! All help is appreciated.

What are the expectations of being a part of this program? 

You can expect this program to take up to 3 hours a week on average but ideally won’t require that much time. Don’t fret if that seems like more time than you can commit. The plan is to make involvement flexible enough for people with different levels of capacity to still be able to join the fun. 

What do I need to join this program?

All you need is time and a testing environment, which you can find more information here. If a testing environment is a blocker for you in any way, please contact @annezazu in WordPress slack. If time is a blocker, join the club and feel free to chat with @annezazu about how you  might still be able to help out. 

Where are decisions about Full Site Editing being made?

To get involved in decision making for Full Site Editing, jump into the weekly Core Editor meetings. Those meetings along with joining the discussions on GitHub are the best place to dive deep into the world of 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. https://wordpress.org/gutenberg/. 

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 will be shared on Make Test with a cross post to Make Core. 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.

For Full Site Editing in general, please review this post highlighting the different ways people can stay up to speed in a way that works for them. 

Last updated: