Full Site Editing Outreach Experiment

For context on this program, please review this post shared on May 1st kicking off this experiment

Program Goal: 

Help improve the Full Site Editing experience by gathering feedback from WordPress site builders. This program does not replace sharing feedback on GitHub so, whether you’re a part of this program or not, please keep sharing there.

Approach: 

We’ll start with more limited common user experiences and, over time, will move to more complex testing (adding in different themes, plugins, etc). For example, this means that we won’t be testing across a wide range of themes, but will start with a fairly simple setup 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/ and a FSE ready theme. 

Communication:

As much as possible, please communicate in #fse-outreach-experiment. While you can always DM @annezazu separately, it’s preferred to communicate in the open. When you ask your question in the open channel, it helps everyone learn, even the people who might have been too shy to ask the same thing.

To help stay up to date on the project itself, please review this post on ways to keep up with FSE

Format: 

Each week, there will be a flowFlow Flow is the path of screens and interactions taken to accomplish a task. It’s an experience vector. Flow is also a feeling. It’s being unselfconscious and in the zone. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it.

Flow is the actual user experience, in many ways. If you like, you can think of flow as a really comprehensive set of user stories. When you think about user flow, you’re thinking about exactly how a user will perform the tasks allowed by your product.Flow and Context
to focus on. The flow to test will be shared on Monday with feedback due that following Friday. This gives a 5-day turnaround to go through the process and share feedback directly. Feedback collected in the first week will be reviewed over the following week and turned into 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/ issues as appropriate. Every two weeks, a summary post will be shared on WordPress Core team blog about the focus of the program, flows worked on, and the results.

Feedback Form (linked here);

Please submit feedback to this form. If you feel comfortable filing GitHub issues, you’re welcome to do so, but this isn’t required as part of this experiment. 

Tools: 

While you are free to use your own testing environment and follow these instructions, we wanted to share basic tools you’ll need to get started:

  • Gutenberg.run: The tool to spin up and test Gutenberg PRs. 
  • Theme Experiments: A repository of 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. based themes to use for testing. We ask that you use one of these themes for consistency.
  • GIPHY Capture or LICEcap: Tools to capture GIFs to better highlight any bugs you might run into.

Last updated: