Summary for April 15th Support Team Meeting

Headlines / Community Updates

WordPress 5.8 preparations

With Full Site Editing making it’s initial appearance in WordPress 5.8, the support team have started to prepare actionable items to get ready for it’s arrival.

Under are some thoughts and concerns that came up in that discussion, and which we’ll try to address moving forward up to the release date.

If there are other concerns or talking points, please feel free to provide them in a comment on the original summary post (where you can also enjoy this weeks artist), or raise them in an upcoming support meeting!

  • Coordinate with docs to make sure relevant documentation is ready before release so that support can familiarize them selves with it.
  • Coordinate with the 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. team, how do they want to get feedback, and issues, reported in a sensible way. Support shouldn’t have to create tickets, but pushing users away and telling them to go to 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. is also a terrible experience.
  • Make sure Gutenberg team has people on hand and we know who is available to help on complex issues the team may not know the answers to.
  • This may be another scenario like the 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. editor release where we see The Good, The Bad, and The Ugly. How do we support those who land in the thick of it with negatively inclined users. All while also trying to show understanding and compassion where it should be, not everyone is inherently bad, and may be concerned or scared users as well.
  • Likely a focus on existing users and how this affects them, more so than new users without existing themes and content.