This post summarizes the latest weekly Editor meeting (agenda, slack transcript). This meeting was held in the #core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel on 2020-10-28 14:00 UTC and was moderated by @annezazu.
- Gutenberg 9.2.2 was released on October 26th.
- WordPress 5.6 Beta 2 was released on October 27th! Please install on a test site, play around, try to break everything, report bugs, and all that good stuff:
- WordPress 5.5.2 is coming to your WordPress site on October 29th.
Monthly Plan & Key Project Check-in
For context, here’s the overarching plan for October.
Widgets Screen Update shared by @andraganescu
The focus for the people previously working on this screen is now mostly on 5.6 efforts. However, there still is work around advancing various widgets project related issues. For example, @zieladam‘s PR about fixing concurrency related issues, something which became apparent while working on the widgets editor.
Reminder: the widget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. core sync chat is suspended until 5.6 has been released!
Global Styles Update shared by @nosolosw
Global styles has advanced nicely this month with @jorgefilipecosta doing great work related to user-provided color palettes, etc. We’re now going to have a stronger focus on tighten things up to work great with the TwentyTwentyOne block 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 theme. Some of the items in the first wave of work will also be moved to the “future” iteration at this point.
Full Site Editing Update shared by @vindl
Full Site Editing – Navigation update:
- Search feature for the navigation component has been merged. The next step is integrating it with the site editor.
- It’s now possible to create new templates from the navigation sidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. that correspond to default ones from template hierarchy.
- We shipped the RTL support for the navigation component.
- PR for creating template parts from multiple blocks selection has been merged.
- There is a proposed framework PR for introducing a custom status for templates provided by themes (or plugins) as HTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. files, which haven’t been customized by the user yet.
In other news:
Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something. Remember: don’t just focus on code contributions!
Mainly focused on fixing issues raised in Beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 and will continue to help with that, but will also come back at global styles work.
Was trying to verify whether Single Column Functionality, which looks like it made it into 9.2, is going into WP 5.6. As a result, this small screen display issue was put in the 5.6 must-have project board to be triaged.
Wrangled some quicker doc updates: glossary terms to include more block based items, triage instructions to include tables for clarity & reasons for closing, and updated the Versions in WordPress doc for 5.6 (need to do the same for 5.5.2). Outside of that, helped clear out a bit of a backlog for unlabeled items, did some FSE testing/bug 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. reporting, and started gathering resources for the contributor working group effort!
Starting to work on more FSE tasks: trying to streamline the flows to enable/disable FSE themes. Still working on documentation for 5.6 new APIs and dev notes 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.. Hoping to have time to chime in on this thread soon.
Has been working on improving e2e tests.
Should we bail on e2e tests after a single failure? Raised by @mkaz.
Marcus has been working on trying to improve tests and asked the group for thoughts on whether we should bail on e2e tests after a single failure as it’s not clear if there’s value in doing so. This is particularly the case for GitHub 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/ Actions to keep running all the tests after an error happens. After a quick discussion with people sharing their differing approaches to handling failures, @youknowriad summed up the root issue nicely: “I feel the issue is not that we run the whole suite on github but more that the tests actually fail…What we should do is actually take the time to fix the failures even if we’re not responsible for them”.
What should be included in the next “What’s Next” in Gutenberg 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/ post? Raised by @daisyolsen.
@nosolosw made sure to link to the previous update around Global Styles. @youknowriad mentioned both that writing Dev Notes should be mentioned for preparing for 5.6 and that he personally would like to see a greater focus on FSE related work.
Is the current plan to use PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher files instead of static HTML files for FSE? Raised by @johnstonphilip.
@youknowriad once more swooped in to share that there’s an exploration along those lines being done here.