This post summarizes the weekly editor chat meeting (agenda here) held on 2022-04-06 14:00 UTC in Slack. Moderated by @zieladam.
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/ 13.0 RC 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).
The next release of the Gutenberg Plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party is 13.0.0 and will be the last Gutenberg release included in WordPress 6.0. For this reason, the Release 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). will be published on Friday 8th April, instead of Wednesday, giving a couple of extra days for PRs to be included in WordPress 6.0.
This release is managed by the Editor Tech Leads @zieladam and @gziolo.
The RC will shortly be followed by the WordPress feature freeze schedule in conjunction with Beta 1 on April 12th – it’s the Tuesday next week! Once that happens, new features will no longer be merged to the 6.0 release. Instead, it will be all about stabilizing the release and fixing the bugs.
The current efforts are tracked on the Project Board. Note that it is not a list of must-haves. Rather, it is a tracker that reflects the status of current developments. The remaining in progress Pull Requests can use all the help they can get!
The Backport PHP changes for WordPress 6.0 release tracking issue prepared by @gziolo reflects the status of backporting the PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes from the Gutenberg repository to the WordPress SVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. trunk 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.. If you’ve worked on one of the pull requests listed in there – your help and feedback will help smoothly merge them into WordPress 6.0!
Finally, there is a tracking issue for all the APIs marked as
__experimental. This is the longest list so far! If you’ve worked on any experimental API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., your participation in that issue will help stabilize it.
Key project updates
- Releasing Gutenberg 13.0 and leading merging it to WordPress 6.0 with @gziolo
- Worked with @dmsnell on bringing the TypeScript support to the
@wordpress/core-data modules. This effort is tracked in the following two PRs:
- The WordPress 6.0 DevNote 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, and 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. tracking issue is now updated. https://github.com/WordPress/gutenberg/issues/39654. Everyone pinged there is invited to write their 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, and 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. and connect with me if there are blockers or questions
Announcements, questions and discussions.
Asked what kind of issues are fit for being added to the 6.0 Project Board. The answer was to focus more on PRs than issues as, at this stage, it’s like the sprint before the 13.0 is released. Also, adding something to the board is not a permanent commitment so adding something extra is fine. A new column called “After Gutenberg 13.0” was added.
Asked if PRs stabilising experimental features should be landed today. The answer was to merge them before Friday for the purposes of WordPress 6.0, and after Friday for the purposes of WordPress 6.1. Notably, the number of experimental features increased greatly since the previous WordPress release, and @zieladam will start a discussion to find the solution.
@gziolo also noted that experimental features like new core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks need to be promoted to stable as otherwise their code gets removed during the build process in WordPress core,
Brought two Pull Requests to everyone’s attention:
[Block Library – Post Terms]: Add dynamic variations of custom taxonomies that makes the Custom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. terms show in the Query Loop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. 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.. Unfortunately, it isn’t merged right now and would benefit greatly from all the reviews it can get.
Add: Option to pick a pattern on page creation that displays a new patterns modal whenever a new page is created. Paal hoped to find an alternative, more subtle solution.
To get more details go directly to the Open Floor discussions in the Core 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.
Props to @paaljoachim for reviewing!
#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary