Editor chat summary: 2 June, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on 2021-06-2 14:00 UTC in Slack. Moderated by @annezazu.

Announcements

WordPress 5.8 project board update

The link to the Project Board can be found here. @youknowriad shared both that progress is continuing with the number of issues going down and that there are a number of important dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. to write. He asked for ideas around how best to coordinate this work. @mkaz chimed in to share that he added the Dev Notes to a tracking spreadsheet for the docs team and that he can help wrangle people for this work. Both @annezazu and @daisyo raised their hands to help with this effort.

In terms of next steps, triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. needs to be done before confirming what needs docs and creating individual tickets to then 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.” volunteers about.

Monthly Priorities & Key Project Updates

The June edition of the “What’s Next” post hasn’t been shipped yet but efforts are clearly planned to focus around 5.8. Outside of that, folks still shared some updates in line with last month’s priorities:

Full Site Editing

@youknowriad shared two things on his mind that likely need some help:

  • An interesting proposal to change a bit how we tie templates to themes.
  • Potential iterations on the Query 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. to add a bit of friction to editing posts.

Navigation Block

@mkaz shared that the Navigation block is stalling a little with a big next step revolving around a larger decision around the markup. A few minor updates for design and performance improvements over the last week.

Mobile

@hypest shared the following:

  • Shipped the Inserter tooltip + Audio block fixes
  • In Progress: Editor onboarding, Block picker search, Embeds block 
  • ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native 0.64.x upgrade around the corner, including upgrade to React v17!

Block Based Widgets Editor

After the meeting, @andraganescu shared that the focus is currently on shipping as many bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes as possible!

Task Coordination

@youknowriad

  • Update packages on trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.
  • Reviewing PRs that are targeted for 5.8
  • Small fixes (Patterns, Template Mode)
  • Coordination work

@joen

  • Landed a navigation block refactor to enable global-styles-controlled padding and more theme control.
  • Keeping an eye out for any followups on that, as well as on the hamburger menu.
  • My focus remains on enabling patterns (which means also refining social links and search). At the moment that means exploring what it means for the setup state to enable a crazy pattern like this one.
  • List view as a user experience improvement is also on my radar.

@annezazu

  • Solely focused on FSE Outreach Program work mainly in the form of triaging feedback, sharing summaries, and coordinating with others. I have some time off this week/next so trying to stay as focused as possible.
  • There is a proposal around having profile badges as part of the program which would be great to get more thoughts on.

@toro_unit

@aristath

  • This past week mostly 5.8-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/ tasks and lots of PR reviews to move things forward.
  • Highlights: backporting the site-logo block to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. & landed a PR to allow using non-latin characters in slugs 

@daisyo

  • Running a three hour workshop on creating block themes tomorrow for WordSesh.

Open Floor

Can someone take a look at a PR to make templates more extendable? From @janwoostendorp.

Last week, the same PR was shared and it was suggested to add a use case to make it clearer what the PR is attempting to accomplish. This week, @janwoostendorp was hoping to get a review of the same PR now that the use case has been elaborated upon. @youknowriad chimed in say that the use case seems legit and the proposed solution for it seems sane. However, he was concerned about introducing filters that are low level at this stage in development.

Next Step: @youknowriad pinged folks on the PR who have experience with backend filters to give a more informed opinion and perhaps move this forward.

Is anyone willing to take on leading the 10.8 RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). release today? From @youknowriad.

To help ease concerns a few folks had, Riad shared a link to the release wrangling documentation. For anyone interested, check it out and know this is a highly valued way to contribute back to WordPress!

Next step: Sandip Mondal volunteered after the meeting was over and will help with the stable release next week while other folks took care of the RC due to timezones.