Title: 2021 – Page 3 – Make WordPress Core --- # Yearly Archives: 2021 [ ](https://profiles.wordpress.org/justinahinon/) [Justin Ahinon](https://profiles.wordpress.org/justinahinon/) 1:20 pm _on_ December 15, 2021 Tags: [core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [performance ( 413 )](https://make.wordpress.org/core/tag/performance/), [performance-chat ( 340 )](https://make.wordpress.org/core/tag/performance-chat/), [summary ( 974 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Performance team meeting summary – December, 14 2021](https://make.wordpress.org/core/2021/12/15/performance-team-meeting-summary-december-14-2021/)󠁿 [This is the agenda for the meeting](https://make.wordpress.org/core/2021/12/13/performance-chat-agenda-december-14-2021/). You can read the logs [here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1639497644493700). ## Focus groups updates ### Images _If you want to have an overview of the work being done for this focus, this [GitHub project](https://github.com/WordPress/performance/projects/1) is the right place to look at._ The Images focus group has had some interesting updates in the last few days. [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) shared some of them. First [@mikeschroder](https://profiles.wordpress.org/mikeschroder/) is working on [this issue](https://github.com/WordPress/performance/issues/7) about determining the best quality level to use when compressing images in newer formats like WebP. On this topic, [@mihai2u](https://profiles.wordpress.org/mihai2u/) mentionned that there could be a second approach to compress 2x+ retina images. Read the full comment [here](https://github.com/WordPress/performance/issues/7#issuecomment-993711137), and feel free to add your ideas as well. Another good new for the Images focus, [this module](https://github.com/WordPress/performance/pull/32) by [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) has recently been merged into the Performance pluginPlugin 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.. When enabled, uploaded JPEG images are saved as WebP sub-sizes. Please feel free to test it and add your feedbacks in the PR comments. Complete testing instructions will follow soon. There was also an interesting discussion about using the `` markup to serve images in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and the potential plan to support the` avif` format. Find the entire discussion [here](https://wordpress.slack.com/archives/C02KGN5K076/p1639498602016700) on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). ### Site Health [@furi3r](https://profiles.wordpress.org/furi3r/) is working on porting the work done by [@audrasjb](https://profiles.wordpress.org/audrasjb/) to a performance module. Follow [this issue](https://github.com/WordPress/performance/issues/25) for updates about the progress. ### Object caching As for the Object caching focus, [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) has done some work on this [pull request](https://github.com/WordPress/wordpress-develop/pull/2018) about some enhancements to the cache APIAPI 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. component. Feel free to leave a review on the pull request of the related ticketticket Created for both bug reports and feature development on the bug tracker.. ### Measurement [@wp-source](https://profiles.wordpress.org/wp-source/) has on schedule to create the issues for the focus group in the following days. Keep an eye on the [performance plugin repository](https://github.com/WordPress/performance) to know when these go live. [@josephscott](https://profiles.wordpress.org/josephscott/) announced that the folks at [WebPageTest.org](http://webpagetest.org/) have donated to the performance team an API key that is good for 1,000 tests per month. There have been also some progress for the Blackfire and Platform.sh accounts for the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) project; and we can expect start using them soon. Here are also the [log on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1639500109063200) for a discussion about defining what a minimal viable performant environment looks like. [#core-media](https://make.wordpress.org/core/tag/core-media/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#performance](https://make.wordpress.org/core/tag/performance/), [#performance-chat](https://make.wordpress.org/core/tag/performance-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/paaljoachim/) [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/) 1:27 pm _on_ December 14, 2021 Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-agenda ( 189 )](https://make.wordpress.org/core/tag/core-editor-agenda/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/)    # 󠀁[Editor Chat Agenda: 15 December 2021](https://make.wordpress.org/core/2021/12/14/editor-chat-agenda-15-december-2021/)󠁿 Facilitator and notetaker: [@andraganescu](https://profiles.wordpress.org/andraganescu/) This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, December 15 2021, 03:00 PM GMT+1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Chat&iso=20211215T15&p1=187&ah=1). _This meeting is held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)._ * 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/](https://wordpress.org/gutenberg/) 12.2 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)](https://make.wordpress.org/core/2021/page/3/?output_format=md#alpha-beta). * [What’s new in Gutenberg 12.1 ( 8 December)](https://make.wordpress.org/core/2021/12/08/whats-new-in-gutenberg-12-1-8-december/) * [WordPress 5.9](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/) - [revised release schedule](https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/). - BetaBeta 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. 3 release 14 December. - [“Must Haves” review](https://github.com/WordPress/gutenberg/projects/62) – what’s left? * Updates based on [updated scope for site editing projects](https://github.com/WordPress/gutenberg/issues/33094): - Navigation 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.. - Template editor. - Patterns. - Styling. - Mobile Team. - Components Team. * Task Coordination. * Open Floor. If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion: * If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself. * If you have anything to share for the Task Coordination section, please leave it as a comment on this post. * If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below. [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-agenda](https://make.wordpress.org/core/tag/core-editor-agenda/), [#meeting](https://make.wordpress.org/core/tag/meeting/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 10:51 pm _on_ December 13, 2021 Tags: [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [core ( 743 )](https://make.wordpress.org/core/tag/core/), [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/) # 󠀁[A Week in Core – December 13, 2021](https://make.wordpress.org/core/2021/12/13/a-week-in-core-december-13-2021/)󠁿 Welcome back to a new issue of _Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress._. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between December 6 and December 13, 2021. * 19 commits * 23 contributors * 35 tickets created * 13 tickets reopened * 33 tickets closed The Core team is currently working on the [next major release, WordPress 5.9](https://make.wordpress.org/core/5-9/), and [the beta 2 was released last week](https://wordpress.org/news/2021/12/wordpress-5-9-beta-2/) 🛠 Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the [Trac timeline for the period above](https://core.trac.wordpress.org/timeline?from=12%2F13%2F2021&daysback=7&authors=&ticket=on&changeset=on&repo-=on&repo-design=on&repo-tests=on&sfp_email=&sfph_mail=&update=Update). The following is a summary of commits, organized by component and/or focus. ## Code changes ### Build/Test Tools * Disable WP Cron when installing PHPUnit tests – [#54612](https://core.trac.wordpress.org/ticket/54612) ### Coding Standards * Correct alignment in `blocks.php` and `class-wp-rest-templates-controller` – [#53359](https://core.trac.wordpress.org/ticket/53359) * Remove a trailing comma from a `compact()` call in `_wp_customize_include()` – [#53359](https://core.trac.wordpress.org/ticket/53359) * Simplify or wrap some long conditions in `wp-includes/theme.php` for better readability– [#53359](https://core.trac.wordpress.org/ticket/53359), #53399 * Use camel case with a lowercase first letter for the `blockTheme` array key – [#54578](https://core.trac.wordpress.org/ticket/54578), [#53359](https://core.trac.wordpress.org/ticket/53359) ### Docs * Capitalize “ID”, when referring to a post ID, term ID, etc. in a more consistent way – [#53399](https://core.trac.wordpress.org/ticket/53399) * Capitalize “ID”, when referring to a sidebarSidebar 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. ID in a more consistent way – [#53399](https://core.trac.wordpress.org/ticket/53399) * Capitalize “ID”, when referring to a widgetWidget 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. ID or sidebar ID, in a more consistent way – [#53399](https://core.trac.wordpress.org/ticket/53399) * Correct the format of some comments per the documentation standards – [#53399](https://core.trac.wordpress.org/ticket/53399) * Docblockdocblock (phpdoc, xref, inline docs) adjustments in some 5.9 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. related functions – [#53359](https://core.trac.wordpress.org/ticket/53359) * Document the global used in `upgrade_590()` function – [#53399](https://core.trac.wordpress.org/ticket/53399) * Update a comment in `wp-admin/load-styles.php` per the documentation standards– [#53399](https://core.trac.wordpress.org/ticket/53399) * Update some `@var` tags per the documentation standards – [#53399](https://core.trac.wordpress.org/ticket/53399) ### Editor * Add an editor settings flag to enable the new gallery for mobile apps for 5.9– [#54583](https://core.trac.wordpress.org/ticket/54583) ### General * Mark the recommended MariaDB version number in `readme.html` with a `` tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) – [#41490](https://core.trac.wordpress.org/ticket/41490) ### REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) 󠀁[https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/)󠁿 * Ensure that the parent link, uses the rest_get_route_for_post function – [#53656](https://core.trac.wordpress.org/ticket/53656) ### Themes * Auto-enable block-templates support for all block themes – [#54335](https://core.trac.wordpress.org/ticket/54335) * Show only “Customize” or “Activate” button in block theme’s Theme Details modal– [#54578](https://core.trac.wordpress.org/ticket/54578) ### Upgrade/install * Revert upgrader rollback features – [#54543](https://core.trac.wordpress.org/ticket/54543), [#54166](https://core.trac.wordpress.org/ticket/54166), [#51857](https://core.trac.wordpress.org/ticket/51857) ## Props **Thanks to the 23 people who contributed to WordPress Core on Trac last week:** [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/) (3), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 3), [@costdev](https://profiles.wordpress.org/costdev/) (2), [@noisysocks](https://profiles.wordpress.org/noisysocks/)( 2), [@Spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) (1), [@bronsonquick](https://profiles.wordpress.org/bronsonquick/)( 1), [@glendaviesnz](https://profiles.wordpress.org/glendaviesnz/) (1), [@Boniu91](https://profiles.wordpress.org/boniu91/)( 1), [@francina](https://profiles.wordpress.org/francina/) (1), [@TobiasBg](https://profiles.wordpress.org/tobiasbg/)( 1), [@desrosj](https://profiles.wordpress.org/desrosj/) (1), [@aristath](https://profiles.wordpress.org/aristath/)( 1), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (1), [@afragen](https://profiles.wordpress.org/afragen/)( 1), [@galbaras](https://profiles.wordpress.org/galbaras/) (1), [@dlh](https://profiles.wordpress.org/dlh/)( 1), [@pbiron](https://profiles.wordpress.org/pbiron/) (1), [@antonvlasenko](https://profiles.wordpress.org/antonvlasenko/)( 1), [@kafleg](https://profiles.wordpress.org/kafleg/) (1), [@ryelle](https://profiles.wordpress.org/ryelle/)( 1), [@poena](https://profiles.wordpress.org/poena/) (1), [@Chouby](https://profiles.wordpress.org/chouby/)( 1), and [@ocean90](https://profiles.wordpress.org/ocean90/) (1). **Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 11), [@audrasjb](https://profiles.wordpress.org/audrasjb/) (4), [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/)( 1), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) (1), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/)( 1), and [@youknowriad](https://profiles.wordpress.org/youknowriad/) (1). [#5-9](https://make.wordpress.org/core/tag/5-9/), [#core](https://make.wordpress.org/core/tag/core/), [#week-in-core](https://make.wordpress.org/core/tag/week-in-core/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 8:13 pm _on_ December 13, 2021 Tags: [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [dev-notes ( 646 )](https://make.wordpress.org/core/tag/dev-notes/)    # 󠀁[Posts, Post types and Taxonomy changes in WordPress 5.9](https://make.wordpress.org/core/2021/12/13/posts-post-types-and-taxonomy-changes-in-wordpress-5-9/)󠁿 In WordPress 5.9, new hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. and functions are added to help developers to work with Posts, Post types and Taxonomies. ## `is_post_type_viewable` filterFilter Filters are one of the two types of Hooks 󠀁[https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks)󠁿. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. WP 5.9 introduces the new `is_post_type_viewable` filter to allow developers to hook into `is_post_type_viewable()` to override the check performed by this function. This filter exposes the `$post_type` object to allow to return either `true` or ` false` depending on their needs. The expected filtered value is a boolean. As filtered values can change, including the data type, this commit includes a `is_bool()` check, thus ensuring backwards-compatibility and guard against potential type errors in PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.1+. Non-boolean values (even falsey and truthy values) will result in the function returning `false`. Usage: ```notranslate /** * Override is_post_type_viewable() value for the "Books" custom post type. */ function wporg_books_is_not_a_viewable_post_type( $is_viewable, $post_type ) { if ( __( 'Books', 'my-plugin' ) === $post_type->label ) { return false; } return $is_viewable; } add_filter( 'is_post_type_viewable', 'wporg_books_is_not_a_viewable_post_type', 10, 2 ); ``` Related ticketticket Created for both bug reports and feature development on the bug tracker. on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.: [#49628](https://core.trac.wordpress.org/ticket/49628). ## `is_post_status_viewable` filter Similarly to `is_post_type_viewable`, the `is_post_status_viewable` filter allow developers to hook into the related PHP function. This filter exposes the `$post_status` object to allow to return either `true` or `false` depending on their needs. Usage: ```notranslate /** * Override is_post_status_viewable() value for the "Unread" custom post status. */ function wporg_unread_is_not_a_viewable_post_status( $is_viewable, $post_status ) { if ( __( 'Unread', 'my-plugin' ) === $post_status->label ) { return false; } return $is_viewable; } add_filter( 'is_post_status_viewable', 'wporg_unread_is_not_a_viewable_post_status', 10, 2 ); ``` Related ticket on Trac: [#54375](https://core.trac.wordpress.org/ticket/54375). ## `post_thumbnail_url` filter WP 5.9 Introduces the new filter `post_thumbnail_url` which allows overriding the default url returned from `wp_get_attachement_image_url()` function. It passes the following parameters: * `$thumbnail_url`: The Post thumbnail URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org (or false if the post does not exist) * `$post`: The Post ID or WP_Post object. Default is global `$post` * `$size`: The Registered image size to retrieve the source for or a flat array of height and width dimensions. Default value: `post-thumbnail` Usage: ```notranslate /** * Override the post thumbnail URL for a specific template. */ function wporg_change_post_thumbnail_url_for_about_template( $thumbnail_url, $post, $size ) { if ( 'templates/about.php' !== get_page_template_slug( $post ) ) { return wp_get_attachment_image_url( get_template_directory . '/images/my-specific-image.png' ); } return $thumbnail_url; } add_filter( 'post_thumbnail_url', 'wporg_change_post_thumbnail_url_for_about_template', 10, 3 ); ``` Related ticket on Trac: [#40547](https://core.trac.wordpress.org/ticket/40547). ## `post_thumbnail_id` filter Similarly, WP 5.9 introduces the new `post_thumbnail_id` filter which allows overriding the default id returned from `get_post_thumbnail_id()`. It passes the following parameters: * `$thumbnail_id`: The Post thumbnail ID (or false if the post does not exist) * `$post`: The Post ID or WP_Post object. Default is global `$post` Related ticket on Trac: [#23983](https://core.trac.wordpress.org/ticket/23983). ## New labels available in `register_taxonomy()` In WP 5.9, some static strings were replaced with additional label options to allow developers further flexibility for customizing the **Edit {taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. [https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies).}** screen. The following labels were added: * `name_field_description`: Description for the Name field on Edit Tags screen. Default: “The name is how it appears on your site.” * `parent_field_description`: Description for the Parent field on Edit Tags screen. Default: “Assign a parent term to create a hierarchy. The term Jazz, for example, would be the parent of Bebop and Big Band.” * `slug_field_description`: Description for the Slug field on Edit Tags screen. Default: “The « slug » is the URL-friendly version of the name. It is usually all lowercase and contains only letters, numbers, and hyphens.” * `desc_field_description`: Description for the Description field on Edit Tags screen. Default: “The description is not prominent by default; however, some themes may show it.” Related ticket on Trac: [#43060](https://core.trac.wordpress.org/ticket/43060). ## New function to get the URL for existing revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. of a post: `wp_get_post_revisions_url()` Since WP 5.9, the `wp_get_post_revisions_url()` function can be used to get a link to a given post’s revisions. Parameters: * `$post_id` (optional): Post `ID` or `WP_Post` object. Default is global `$post`. This function returns the URL for editing revisions on the given post (or `null` otherwise). Related ticket on Trac: [#39062](https://core.trac.wordpress.org/ticket/39062). ## New built-in post types in WP 5.9 Please note that WordPress 5.9 introduces four new built-in post types related to the new full site editing experience and are used when a 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. Theme is activated. * `wp_template`: The templates to include in your theme. * `wp_template_part`: The template parts to include in your templates. * `wp_global_styles`: The styles created and saved by the site adminadmin (and super admin) for the current theme. * `wp_navigation`: The navigation menus that can be inserted into the site. Additional 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, 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. will be published to introduce the new full site editing experience. Note the above post types are `reserved terms` for WordPress internal usage. _Thanks [@mkaz](https://profiles.wordpress.org/mkaz/) for proofreading._ [#5-9](https://make.wordpress.org/core/tag/5-9/), [#dev-notes](https://make.wordpress.org/core/tag/dev-notes/) [ ](https://profiles.wordpress.org/fabiankaegy/) [Fabian Kaegy](https://profiles.wordpress.org/fabiankaegy/) 4:15 pm _on_ December 13, 2021 Tags: [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-summary ( 185 )](https://make.wordpress.org/core/tag/core-editor-summary/), [gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/), [meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/), [summary ( 974 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Editor chat summary: 8 December, 2021](https://make.wordpress.org/core/2021/12/13/editor-chat-summary-8-december-2021/)󠁿 This post summarizes the weekly editor chat meeting [(agenda here)](https://make.wordpress.org/core/2021/12/06/editor-chat-agenda-8-december-2021/) held on [Wednesday, December 8 2021, 03:00 PM CET](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Chat&iso=20211208T15&p1=37&ah=1) in [Slack](https://wordpress.slack.com/messages/C02QB2JS7). Moderated by [@fabiankaegy](https://profiles.wordpress.org/fabiankaegy/). ## 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/](https://wordpress.org/gutenberg/)󠁿 pluginPlugin 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/](https://wordpress.org/plugins/)󠁿 or can be cost-based plugin from a third-party. releases: [Gutenberg 12.1](https://github.com/WordPress/gutenberg/releases/tag/v12.1.0) was released. [What’s new in Gutenberg 12.1.0](https://make.wordpress.org/core/). Parts of 12.0 and 12.1 were backported into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and will be part of WP 5.9. ## WordPress 5.9 [Beta 2 ](https://wordpress.org/news/2021/12/wordpress-5-9-beta-2/)was released on December 7. You can get an overview of how to help test WordPress 5.9 Features in this helpful post: [https://make.wordpress.org/test/2021/11/30/help-test-wordpress-5-9-features/](https://make.wordpress.org/test/2021/11/30/help-test-wordpress-5-9-features/) [@noisysocks](https://profiles.wordpress.org/noisysocks/) shared the following update: * This ticketticket Created for both bug reports and feature development on the bug tracker. needs a dev: [Update the Dashboard welcome banner for 5.9](https://core.trac.wordpress.org/ticket/54489) * There’s lots of PRs to review and bugs to squash in the [5.9 Must Haves project board](https://github.com/WordPress/gutenberg/projects/62) * This 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. is particularly annoying and would be good to fix: [Site Editor: Template part is missing after exiting focus mode](https://github.com/WordPress/gutenberg/issues/36937) [@mkaz](https://profiles.wordpress.org/mkaz/) shared that there are lots of 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, 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. that need writing here: [https://github.com/orgs/WordPress/projects/11/](https://github.com/orgs/WordPress/projects/11/) ## Key project updates Based on the scope for [Site Editing projects](https://github.com/WordPress/gutenberg/issues/33094). ### Template Editor [@paaljoachim](https://profiles.wordpress.org/paaljoachim/) & [@mamaduka](https://profiles.wordpress.org/mamaduka/) * [Templates list screen overview](https://github.com/WordPress/gutenberg/issues/36597) * [Site Editor: Template part is missing after exiting focus mode](https://github.com/WordPress/gutenberg/issues/36937) * [“Site” menu item is active when editing a template](https://github.com/WordPress/gutenberg/issues/36821) * [client side routing for Template List view](https://github.com/WordPress/gutenberg/pull/36488) ### Global Styles [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) * We are working on a redesign of how colors appear on 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. inspector [https://github.com/WordPress/gutenberg/pull/37067](https://github.com/WordPress/gutenberg/pull/37067) To make the UIUI User interface simpler and less poluted ### Mobile: [@Antonis](https://profiles.wordpress.org/antonis/) Lilis Fixes: * Fixed parsing issues on generating the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. bundle by using a newer version of the WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is [http://wp-cli.org/](http://wp-cli.org/) [https://make.wordpress.org/cli/](https://make.wordpress.org/cli/) command Finalizing: * Upgrade to ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. [https://reactjs.org](https://reactjs.org/) Native v0.66. * GSS Font size, line height and selected text color ### Components Package [@Marco](https://profiles.wordpress.org/marco/) Ciampini Shipping: * Some design [polish was applied to both ](https://github.com/WordPress/gutenberg/pull/37028)` ColorIndicator`[ and ](https://github.com/WordPress/gutenberg/pull/37028)`ItemGroup`, which are both used extensively in the new Styles sidebarSidebar 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.. Fixes: * Support for the `extraSmall`[ size variant for ](https://github.com/WordPress/gutenberg/pull/37097)` Card`[ was reintroduced](https://github.com/WordPress/gutenberg/pull/37097), fixing an inadvertent backward compatibility issue. * By [reintroducing debouncing when using the new ](https://github.com/WordPress/gutenberg/pull/36941)` ColorPicker`[ as a controlled component](https://github.com/WordPress/gutenberg/pull/36941), we avoid the component throwing an error in some situations (e.g. when used within the gradient picker) In Progress: * We’re exploring approaches for [maintaining focus when using components like ](https://github.com/WordPress/gutenberg/issues/37063)` Navigator` (used, for example, in the Styles sidebar).  * We’re updating the `LineHeightControl` used in typography tools to use `NumberControl` internally instead of `TextControl`, which should provide more consistent [styles](https://github.com/WordPress/gutenberg/pull/37160) and [behavior](https://github.com/WordPress/gutenberg/pull/37164). * There are a number of open PRs being discussed involving more consistent support for size variants across components, including `CustomSelectControl`, `FontSizePicker`, and `LineHeightControl`. ## Task Coordination: _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._ [@mamaduka](https://profiles.wordpress.org/mamaduka/) * I’m primarily focused on Site Editor bug fixes and remaining items from WP 5.9 Must-Have list. * Trying to help with PR reviews. * Currently trying to track down cause of the [two](https://github.com/WordPress/gutenberg/issues/36937) [issues](https://github.com/WordPress/gutenberg/issues/36788) (probably related) with Template Parts. [@veminom](https://profiles.wordpress.org/veminom/) If someone would like to help me with a review on this one, I’d be grateful!  [https://github.com/WordPress/gutenberg/pull/35616](https://github.com/WordPress/gutenberg/pull/35616) [https://github.com/WordPress/gutenberg/issues/36864](https://github.com/WordPress/gutenberg/issues/36864) [@paaljoachim](https://profiles.wordpress.org/paaljoachim/) I am been testing WP 5.9 and will continue with testing. Giving feedback to various Template Editor PRs.I worry a bit about not having [Custom templates](https://github.com/WordPress/gutenberg/issues/36860#issuecomment-987189021) included in WP 5.9, as it can create some confusion that one is not able to add a template.I also think about the Preview control drop down in the Post Editor and Site Editor. These are too similar but not identical. We need a [better diffraction between the two](https://github.com/WordPress/gutenberg/issues/29398#issuecomment-988859368). [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/) My main priority is finishing the color UI redesign and address some of the issues we found during the process. ## Open Floor: [@paaljoachim](https://profiles.wordpress.org/paaljoachim/) I am wondering if we still have time to get [Custom Templates](https://github.com/WordPress/gutenberg/issues/36860#issuecomment-987189021) into WP 5.9? _This discussion was continued here: [https://github.com/WordPress/gutenberg/issues/36860#issuecomment-987189021](https://github.com/WordPress/gutenberg/issues/36860#issuecomment-987189021)_ [@welcher](https://profiles.wordpress.org/welcher/) Just wondering if theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. schema is still open for PRs. I have noticed that the `appearanceTools` is marked as a valid option but when added, triggers an error  – I need to open a ticket about it still _[@mkaz](https://profiles.wordpress.org/mkaz/) and [@oandregal](https://profiles.wordpress.org/oandregal/)_ chimed in here and deemed this to be a documentation change which is still ok to merge [@veminom](https://profiles.wordpress.org/veminom/) I was wondering if this could be considered for WP 5.9? [https://github.com/WordPress/gutenberg/pull/35616](https://github.com/WordPress/gutenberg/pull/35616) [https://github.com/WordPress/gutenberg/issues/36864](https://github.com/WordPress/gutenberg/issues/36864) [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/justinahinon/) [Justin Ahinon](https://profiles.wordpress.org/justinahinon/) 3:05 pm _on_ December 13, 2021 Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [performance ( 413 )](https://make.wordpress.org/core/tag/performance/), [performance-chat ( 340 )](https://make.wordpress.org/core/tag/performance-chat/) # 󠀁[Performance Chat Agenda: December 14, 2021](https://make.wordpress.org/core/2021/12/13/performance-chat-agenda-december-14-2021/)󠁿 Here is the agenda for this week’s performance team meeting to occur on [December 14, 2021, at 16:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211214T1600). * **Focus group projects discussion** * **Performance features development coordination** * **Open Floor** --- _This meeting happens in the_[_ __#performance_](https://wordpress.slack.com/archives/C02KGN5K076)_ channel. To join the meeting, you’ll need an account on the _[_Making WordPress Slack_](https://make.wordpress.org/chat/)_._ [#agenda](https://make.wordpress.org/core/tag/agenda/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#performance](https://make.wordpress.org/core/tag/performance/), [#performance-chat](https://make.wordpress.org/core/tag/performance-chat/) [ ](https://profiles.wordpress.org/webcommsat/) [Abha Thakor](https://profiles.wordpress.org/webcommsat/) 2:56 pm _on_ December 10, 2021 Tags: [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [core-auto-updates ( 37 )](https://make.wordpress.org/core/tag/core-auto-updates/), [dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/)    # 󠀁[DevChat meeting summary – December 8, 2021](https://make.wordpress.org/core/2021/12/10/devchat-summary-december-8-2021/)󠁿 Agenda written by [@estelaris](https://profiles.wordpress.org/estelaris/). Dev chat Notes by [@webcommsat](https://profiles.wordpress.org/webcommsat/). Meeting facilitated by [@marybaum](https://profiles.wordpress.org/marybaum/) [Start of the DevChat meeting](https://wordpress.slack.com/archives/C02RQBWTW/p1638993623306500), in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel [Agenda](https://make.wordpress.org/core/2021/12/08/dev-chat-agenda-for-december-8-2021/) ## **BetaBeta 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. 3** **Update from [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/)** Beta 3 is next week in 6 days, i.e. December 14, 2021. Efforts are focused on fixing bugs identified in the beta cycle. There are some new bugs identified where tickets were reopened or new ones created. Help in testing and fixing is greatly appreciated in: – [Milestone’s report for Core specifically](https://core.trac.wordpress.org/tickets/major/workflow)– [List of items for Gutenberg](https://github.com/WordPress/gutenberg/issues/36556) Overall, progress looks to be on track. Not currently seeing any red flags. Thank you to everyone who has contributed to 5.9. [@mkaz](https://profiles.wordpress.org/mkaz/): The list of 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, 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. relating to the release is on [GitHub](https://github.com/orgs/WordPress/projects/11/) rather than as a spreadsheet. ## Blogblog (versus network, site) posts to note [WordPress 5.9 Beta 2 ](https://wordpress.org/news/2021/12/wordpress-5-9-beta-2/) fixed 24 bugs reported by contributors and needs testing. If you can help, please report your findings on the announcement post. [The Editor Chat Summary](https://make.wordpress.org/core/2021/12/07/editor-chat-summary-1-december-2021/) highlights improvements made by the team. [Gutenberg 12.1 RC1](https://github.com/WordPress/gutenberg/releases/tag/v12.1.0-rc.1) was released. [@audrasjb](https://profiles.wordpress.org/audrasjb/) published the latest issue of [A Week in Core](https://make.wordpress.org/core/2021/12/07/a-week-in-core-december-6-2021/)( 6 December 2021). And remember that [the release schedule has been revised.](https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/) [WordPress 5.9 Beta 2](https://wordpress.org/news/2021/12/wordpress-5-9-beta-2/)– Can you help test the latest software version of WordPress? 5.9 Beta 2 was published on 7 December 2021, please help find any bugs. ## Update from Component Maintainers ### **Build/Test Tools, Date/Time, General, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see 󠀁[localization](https://make.wordpress.org/core/2021/page/3/?output_format=md#l10n)󠁿. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks** **Update from [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/):** no major news this week.  ### **Help/About** **Update from [@webcommsat](https://profiles.wordpress.org/webcommsat/): **About Page and related materials. * Monday 6 December 2021 20:30 UTC collaboration - Key areas covered: sections, video options, discussion on the navigation 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.. * Wednesday 8 December 2021, 15:00 UTC plus async - Start of the more detailed exploration of key benefits by audience and messaging for social media . - Also provided an earlier time for anyone wishing to collaborate than the Monday 20:30 UTC sessions. * **Follow the discussions:** Links to all of these sessions are in the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. [ticket](https://core.trac.wordpress.org/ticket/54270) and in the [Marketing Team GitHub](https://github.com/wpmarketingteam/Marcomms-WP-Releases/issues/15) card to help people follow along and get involved, especially those less familiar with Trac. * **Next live collaboration session on slack: **this will take place on Monday13 December 2021, at 20:30 UTC in core. * Over the next few days, [@marybaum](https://profiles.wordpress.org/marybaum/) and [@webcommsat](https://profiles.wordpress.org/webcommsat/) will continue to bring together the different suggestions. Please do continue to add to the documents and spreadsheet asynchronously or reach out if you have a query. Thanks so much and to everyone from core, marketing, training and documentation that have been contributing. * **Request for input: **Dev and extenders insights are particularly needed. - You can also contribute to the [spreadsheet](https://docs.google.com/spreadsheets/d/1S2QU4K6aYMoaNuiDu1lEf9r2hOzHQgsUzMgZcTxdPgg/edit#gid=0) created by [@webcommsat](https://profiles.wordpress.org/webcommsat/) for marcomms. This has different tabs for major audience groups, and information will be broken down by subject in each tab, eg Navigation Block. If you have a suggestion, please add it to the sheet and include the feature area in brackets to help us categorize them. To avoid the problems of internet spamming, [@vimes1984](https://wordpress.slack.com/team/U0337R5K8) after testing has set the spreadsheet to comment mode. Anyone can add insights by opening the link, and clicking on ‘comment’ in the relevant tab. If anyone has difficulty with using it or has a query, please let us know on Slack ( abhanonstopnewsuk). We have options for those who need an alternative format for accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access”( i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia. org/wiki/Accessibility). A post with more information to help contributors will be published later today and a link added to this post. [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) suggested making it available on the core blog too. - **[@marybaum](https://profiles.wordpress.org/marybaum/):** One question we want to answer now is, think of the times you’ve been working on the front end of a site, going back and forth between your code and the block editor. - How does 5.9 make your life easier? For instance, almost every time I do a redesign, I forget I have to rebuild the menus until the last minute. Now the Nav Block means menus stay intact) - **[@costdev](https://profiles.wordpress.org/costdev/):** Also another way to think about it for non-dev users: * Install 5.8.2 and try to create a site. At what points would you need to install another theme, a pluginPlugin 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party., or hire a developer to make a change? * Install 5.9.0 Beta 2. What items are no longer on that list? * 5.9 benefits both dev and non-dev users, so this is a great way to highlight where non-dev users get “stuck” without extenders. - Further insight on the dev benefits from 5.9 requested. This will be the focus of the session on **Monday 13 December 2021, 20:30 UTC in the core slack channel**. [@costdev](https://profiles.wordpress.org/costdev/) hopes to attend and bring a list from testing. ## Open Floor ### Upgrade issue 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/](https://wordpress.org/gutenberg/)󠁿 12/1 and 5.9 Beta 2 @nickdiego: Raised a [Gutenberg issue](https://github.com/WordPress/gutenberg/issues/37232) that he and @ Brian Gardner found after upgrading to 12.1 and 5.9 Beta 2. They have been exploring the issue and wanted to get visibility for it before raising a Trac ticketticket Created for both bug reports and feature development on the bug tracker.. Nick highlighted that the issue has a big impact, and is likely to do with merging code from Gutenberg to Core. He can create a ticket if needed. [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/): A Trac ticket isn’t necessary as once it’s fixed it will get backported with each Monday’s updates. She also highlighted the issue in the core-editor channel for suggestions and adding to the 5.9 project board. She thanked Nick and Brian for testing and identifying the issue. [@jeffpaul](https://profiles.wordpress.org/jeffpaul/): requested view from [@oandregal](https://profiles.wordpress.org/oandregal/) on the ticket. ### Plugin upgrader [@costdev](https://profiles.wordpress.org/costdev/): In [#core-auto-updates](https://make.wordpress.org/core/tag/core-auto-updates/), they have been running through an issue with changes to the plugin upgrader. There’s been a lot of investigation done so far. They will make a decision on Friday about whether we can get this into 5.9 or whether it will need to puntpunt Contributors sometimes use the verb "punt" when talking about a ticket. This means it is being pushed out to a future release. This typically occurs for lower priority tickets near the end of the release cycle that don't "make the cut." In this is colloquial usage of the word, it means to delay or equivocate. (It also describes a play in American football where a team essentially passes up on an opportunity, hoping to put themselves in a better position later to try again.) to 6.0. Request: additional contributors to join the conversation, particularly if they use VVV or Chassis [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/): The issue so far is impacting Vagrant environments, though wider testing on shared hosts, etc. is also needed. If you can help test or contribute, please join in the [#core-auto-updates](https://make.wordpress.org/core/tag/core-auto-updates/) channel. [@marybaum](https://profiles.wordpress.org/marybaum/): Is it okay on Local and the AMPs? [@pbiron](https://profiles.wordpress.org/pbiron/): to be more specific: 5.9 beta2 includes a feature that ‘does a backup’ of the currently installed plugin before the update happens. If the update fails, then it ‘rolls back’ the previously installed version. This feature seems to work fine in every environment in which it has been tested except for VVV/Chassis [@costdev](https://profiles.wordpress.org/costdev/): So far, we haven’t been able to reproduce the issue on Local or other Docker environments (right [@pbiron](https://profiles.wordpress.org/pbiron/)?) or in WSL2 (Hyper-V). (edited)  [@pbiron](https://profiles.wordpress.org/pbiron/): in VVV/Chassis , the plugin actually gets deleted after the update. [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/):  final comment on 5.9 release: The team is working on identifying and resolving this issue this week before Beta 3. If it can’t be resolved, then a hard decision will need to be made. 5.9 will not be at risk. The team is asking for help to join in the effort. ## Target release dates for 2022 Post dev chat announcement from the core slack. [@chanthaboune](https://profiles.wordpress.org/chanthaboune/): I have been in meetings two weeks in a row during core chat time but I have a very important topic, so I’m just going to drop it in here anyway. We’ve got to talk about target release dates for 2022. As I see it we have some options: 1. Four releases, essentially quarterly 2. Three releases, essentially….trimester-ly? 3. Start with Two for the first half and see how we feel about the second half I have suggested schedules for all of those options (and will post about it to [make.wordpress.org/core](https://make.wordpress.org/core)), but meant to open the discussion here first. [@audrasjb](https://profiles.wordpress.org/audrasjb/): In my opinion, with the first update on January, we can probably target 4 releases in 2022. I’d say it’s _currently_ a bit difficult to target 4 full release cycles in one year, but since most of the work for 5.9 was done in 2021, I do think it’s realistic to aim for a 4-release year in 2022. [@joyously](https://profiles.wordpress.org/joyously/) : I’d vote for as few majors as possible, and focus on 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. [@pbearne](https://profiles.wordpress.org/pbearne/): With the work on performance ramping up will at least one release for that work that will/maybe short on UIUI User interface features [#5-9](https://make.wordpress.org/core/tag/5-9/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/justinahinon/) [Justin Ahinon](https://profiles.wordpress.org/justinahinon/) 6:05 am _on_ December 9, 2021 Tags: [core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/), [performance ( 413 )](https://make.wordpress.org/core/tag/performance/), [performance-chat ( 340 )](https://make.wordpress.org/core/tag/performance-chat/), [summary ( 974 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Performance team meeting summary – December, 7 2021](https://make.wordpress.org/core/2021/12/09/performance-team-meeting-summary-december-7-2021/)󠁿 [This is the agenda for the meeting](https://make.wordpress.org/core/2021/12/06/performance-chat-agenda-december-7-2021/). You can read the logs [here on Slack](https://wordpress.slack.com/archives/C02KGN5K076/p1638892814340900). ## **Focus group projects discussion** ### Site Health This is an asynchronous update about the progress for the Site Health group, shared by [@audrasjb](https://profiles.wordpress.org/audrasjb/): * The existing and future Site Health checks will be moved to the Performance mono repo * We received some feedback, the idea is to create issues to discuss them on 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 by the repository owner. [https://github.com/](https://github.com/) * [@audrasjb](https://wordpress.slack.com/team/U161T4P0U) will be available to work on this after 5.9 second betaBeta 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. [@furi3r](https://profiles.wordpress.org/furi3r/) also offered to bring the work done [here](https://github.com/audrasjb/site-health-audit-enqueued-assets/blob/master/site-health-audit-enqueued-assets.php) in a module, on the performance pluginPlugin 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. repository. ### JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. 󠀁[https://www.javascript.com](https://www.javascript.com/)󠁿 There has been no major progress for this group since the last discussions. Hopefully we will see more after the 5.9 release. ### Images [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) shared that the team is continuing the Asia/Pacific timezone friendly meetings Thursdays at +02:00 UTC. They’ve started work on some initial tickets related to WebP: creating an [initial module for WebP on Uploads](https://github.com/WordPress/performance/pull/32), and researching optimal compression/quality settings for WebP (and eventually AVIF) images in [this issue](https://github.com/WordPress/performance/issues/7). About this top, [@blogaid](https://profiles.wordpress.org/blogaid/) expresses some serious concerns they have about creating WebP on uploads. This is being discussed in [this issue](https://github.com/WordPress/performance/issues/22). Please leave a comment there if you have an opinion about this. ### Object Caching [@tillkruess](https://profiles.wordpress.org/tillkruess/) migrated the POC document for this group to a [dedicated project](https://github.com/WordPress/performance/projects/6) on the GitHub repository. In addition to that, more details were added on the issues, based on the feedbacks of the focus group members. ### Measurement We have discussed the offer to use Platform.sh and Blackfire for being able to run automated performance tests against pulls requests and branches. Discussions on this are happening on [this issue](https://github.com/WordPress/performance/issues/44). There is also a suggestion by [@wp-source](https://profiles.wordpress.org/wp-source/) to use Lighthouse CI and CrUX to make synthetic tests on PRs. You can read the discussions about this proposal [here](https://wordpress.slack.com/archives/C02KGN5K076/p1638894187367900) on SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). See also [this issue](https://github.com/WordPress/performance/issues/45) about creating a standard VM for performance testing of WordPress. ### Open Floor [@tweetythierry](https://profiles.wordpress.org/tweetythierry/) proposed a discussion topic for the next meeting. About how we could improve the theme checker (and introduce a plugin check) with some performance “warning”. It could start simple by warning about enqueueing best practice or checking the number of assets enqueued and their sizes. [#core-media](https://make.wordpress.org/core/tag/core-media/), [#meeting](https://make.wordpress.org/core/tag/meeting/), [#performance](https://make.wordpress.org/core/tag/performance/), [#performance-chat](https://make.wordpress.org/core/tag/performance-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/youknowriad/) [Riad Benguella](https://profiles.wordpress.org/youknowriad/) 8:27 pm _on_ December 8, 2021 Tags: [block-editor ( 139 )](https://make.wordpress.org/core/tag/block-editor/), [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-new ( 216 )](https://make.wordpress.org/core/tag/gutenberg-new/)    # 󠀁[What’s new in Gutenberg 12.1 ( 8 December)](https://make.wordpress.org/core/2021/12/08/whats-new-in-gutenberg-12-1-8-december/)󠁿 _“What’s new in 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/](https://wordpress.org/gutenberg/)…” posts (labeled with the [#gutenberg-new](https://href.li/?https://make.wordpress.org/core/tag/gutenberg-new/) tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)) are published following every Gutenberg release on a biweekly basis, discovering new features included in each release. As a reminder, [here’s](https://href.li/?https://make.wordpress.org/core/2020/05/20/ways-to-keep-up-with-full-site-editing-fse/) an overview of different ways to keep up with Gutenberg and the Full Site Editing project._ --- Gutenberg 12.1 is here! the contributors continue to work tirelessly to prepare WordPress 5.9 and fix the remaining flows and bugs for the release. ## Table of Contents * [Template List View](https://make.wordpress.org/core/2021/page/3/?output_format=md#template-list-view) * [Global Styles](https://make.wordpress.org/core/2021/page/3/?output_format=md#global-styles-1) * [Navigation block](https://make.wordpress.org/core/2021/page/3/?output_format=md#navigation-block) * [Miscellaneous editor improvements](https://make.wordpress.org/core/2021/page/3/?output_format=md#miscellaneous-editor-improvements) * [Block themes](https://make.wordpress.org/core/2021/page/3/?output_format=md#block-themes) * [Changelog](https://make.wordpress.org/core/2021/page/3/?output_format=md#changelog) * [Performance Benchmark](https://make.wordpress.org/core/2021/page/3/?output_format=md#performance-benchmark) ## Template List View This release marks the return of the template list view allowing users to navigate between the home page and the different templates and template parts in the site editor. It’s an important piece of the site editor puzzle. The current iteration of the design favors simplicity and usability. Iterations implementing client side navigation and mosaic view might be added in the future. [[ ## Global Styles The global styles panel saw a big number of improvements in this cycle including: * The typography panel has been updated to show a simplified elements view allowing users to switch easily between text and link elements typography styles. [[ * The color palette views now show the duotone presets. Also, users can now define custom gradients to be made available throughout the website. [[ * Transparency support for the different color pickers in the Global Styles panel. ## Navigation 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. Gutenberg 12.1 includes several Navigation block improvements once again. For starters, users are not prompted to name their menus when adding starting a new one, as it is generated automatically, although the name can still be edited in the sidebarSidebar 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.. Also, the UXUX User experience around configuring the menu dropdown options has been improved, only displaying the options when the selected menu actually has submenus, and disabling toggling the `Show arrow` option when `Open on click` is enabled, to avoid confusion. Ensuring a frontend fallback in case no menu is selected in the Navigation block has received lots of thought in the last weeks. Thanks to this, the Navigation block will now render a Page List block when visiting a page with empty navigation. However, this default behavior can be changed by developers via the new `block_core_navigation_render_fallback` filterFilter Filters are one of the two types of Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks). They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output., and completely opt-out by simply adding: ```wp-block-code add_filter('block_core_navigation_render_fallback', '__return_false'); ``` Last, but not least, as the block becomes stable for its release in WordPress 5.9, an APIAPI 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. change should be noted: the `menuId` attribute has been renamed to` ref` to better align with other blocks’ attribute names. A new deprecation has been added to accommodate this change and existing Navigation blocks will get migrated to the new version. ## Miscellaneous editor UX improvements If you ever tested the editor, you’ve probably already noticed these little plus buttons or what we call **block appenders** that appear as you navigate and click throughout the editor. These appenders would often create layout shifts and jumps as you select different blocks. The issue is now finally resolved as the behavior of the block appenders has been changed to rely on fixed positioning. [[ Another small but important change to the user experience in the editor is the addition of a new keyboard shortcut to unselect all blocks. Users could hit Escape to enter navigation mode for better keyboard navigation in the canvas, and starting in Gutenberg 12.1, you can also Escape a second time when in navigation mode to unselect all blocks. ## Block Themes The contributors also focused on improving the developer experience for block themes. If you’re a block theme author, there are two important changes that you should be aware of in Gutenberg 12.1. First, the **`block-templates`** and **`block-template-parts`** folders [have been renamed](https://make.wordpress.org/themes/2021/12/03/new-directory-names-for-block-based-fse-themes/) to just **`templates`** and **`parts`** respectively in preparation for upcoming features, like the addition of **`styles`** and **`patterns`** folders. Existing block themes will continue to work without any change, the former folders are still supported but we encourage you to use the updated names from now on. The documentation has been updated to reflect that change. The second is the addition of a new flag to the `theme.json` settings section called**` appearanceTools`**. Theme authors can set this flag to **true** to opt-in into all the various appearance tools available including border color, radius and width, link color, block gap, margin, padding, line height and any appearance tool that might be added in the future. Generic block themes in the repository may consider enabling this flag automatically to avoid having to keep track of all the additions that come over time. ## Changelog ### Enhancements #### Site Editor * Add Template List View. ([36379](https://github.com/WordPress/gutenberg/pull/36379)) - Show theme, pluginPlugin 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/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. or author in Added By column with appropriate icon or avatarAvatar An avatar is an image or illustration that specifically refers to a character that represents an online user. It’s usually a square box that appears next to the user’s name.. ([36763](https://github.com/WordPress/gutenberg/pull/36763)) - Add success and error snackbars. ([36808](https://github.com/WordPress/gutenberg/pull/36808)) - Implement “Add New”. ([36592](https://github.com/WordPress/gutenberg/pull/36592)) - Use table layout. ([36707](https://github.com/WordPress/gutenberg/pull/36707)) - Set the document title properly. ([36805](https://github.com/WordPress/gutenberg/pull/36805)) - Add rename action. ([36879](https://github.com/WordPress/gutenberg/pull/36879)) - Update delete template button. ([36815](https://github.com/WordPress/gutenberg/pull/36815)) * Make Reusable blocks available in the Site Editor. ([36511](https://github.com/WordPress/gutenberg/pull/36511)) * Remove the Styles link in Site Editor. ([36637](https://github.com/WordPress/gutenberg/pull/36637)) * Update and align template descriptions. ([36000](https://github.com/WordPress/gutenberg/pull/36000)) * Add icons to navigation sidebar items. ([36893](https://github.com/WordPress/gutenberg/pull/36893)) * Allow editing custom template title. ([36933](https://github.com/WordPress/gutenberg/pull/36933)) * Only render the site editor canvas when the global styles are loaded. ([36643](https://github.com/WordPress/gutenberg/pull/36643)) * Remove extra border radius from the canvas. ([37022](https://github.com/WordPress/gutenberg/pull/37022)) * Update navigation sidebar responsiveness. ([36638](https://github.com/WordPress/gutenberg/pull/36638)) * Update resize handle styling in template part focus mode. ([36410](https://github.com/WordPress/gutenberg/pull/36410)) #### Global Styles * Add elements support to the typography panel. ([36718](https://github.com/WordPress/gutenberg/pull/36718)) * Add the gradient palette editor. ([36820](https://github.com/WordPress/gutenberg/pull/36820)) * Add transparency support to the colors panel. ([36840](https://github.com/WordPress/gutenberg/pull/36840)) * Add read-only duotone palette. ([36920](https://github.com/WordPress/gutenberg/pull/36920)) * Do not show default palette if theme opts-out. ([36639](https://github.com/WordPress/gutenberg/pull/36639)) * Make user able to change all color palette origins. ([36674](https://github.com/WordPress/gutenberg/pull/36674))( [36747](https://github.com/WordPress/gutenberg/pull/36747)) ([36817](https://github.com/WordPress/gutenberg/pull/36817)) * Rename `core` origin key to `default` for presets. ([36645](https://github.com/WordPress/gutenberg/pull/36645)) * Count all color palette origins on the palette counter. ([36922](https://github.com/WordPress/gutenberg/pull/36922)) * Add `appearanceTools` flag in theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. to opt-in into appearance UIUI User interface controls. ([36646](https://github.com/WordPress/gutenberg/pull/36646)) * Switch the borders panel to ToolsPanel for displaying UI. ([33743](https://github.com/WordPress/gutenberg/pull/33743)) * Improve the design and copy of the color panels. ([36959](https://github.com/WordPress/gutenberg/pull/36959))( [36994](https://github.com/WordPress/gutenberg/pull/36994)) ([37015](https://github.com/WordPress/gutenberg/pull/37015))( [37016](https://github.com/WordPress/gutenberg/pull/37016)) ([36921](https://github.com/WordPress/gutenberg/pull/36921))( [36963](https://github.com/WordPress/gutenberg/pull/36963)) ([36622](https://github.com/WordPress/gutenberg/pull/36622))( [36965](https://github.com/WordPress/gutenberg/pull/36965)) ([36819](https://github.com/WordPress/gutenberg/pull/36819))( [36748](https://github.com/WordPress/gutenberg/pull/36748)) ([36940](https://github.com/WordPress/gutenberg/pull/36940))( [36684](https://github.com/WordPress/gutenberg/pull/36684)) * Schemas: Allow custom blocks in theme.json styles. ([36411](https://github.com/WordPress/gutenberg/pull/36411)) #### Block Editor * Improve the position of the block appenders and behavior. ([36656](https://github.com/WordPress/gutenberg/pull/36656))( [36605](https://github.com/WordPress/gutenberg/pull/36605)) * Keyboard shortcuts: Double escape unselects all blocks. ([36945](https://github.com/WordPress/gutenberg/pull/36945)) * Adjust order of theme blocks and reorder inserter items. ([36719](https://github.com/WordPress/gutenberg/pull/36719)) * Block Editor List View: Use anchor elements instead of buttons. ([35655](https://github.com/WordPress/gutenberg/pull/35655)) #### Block Library * Block Library: Add the Comments Pagination block. ([36872](https://github.com/WordPress/gutenberg/pull/36872)) * Comment Author Avatar block: Add spacing support. ([36322](https://github.com/WordPress/gutenberg/pull/36322)) * Navigation block: Only show submenu options and Show arrow button when relevant.( [36826](https://github.com/WordPress/gutenberg/pull/36826)) * Navigation block: Implement suitable fallback for Nav block on front end of site when no menu selected. ([36849](https://github.com/WordPress/gutenberg/pull/36849))( [36724](https://github.com/WordPress/gutenberg/pull/36724)) ([36850](https://github.com/WordPress/gutenberg/pull/36850))( [36854](https://github.com/WordPress/gutenberg/pull/36854)) ([36740](https://github.com/WordPress/gutenberg/pull/36740)) * Navigation block: Rename navigationMenuId to ref. ([36739](https://github.com/WordPress/gutenberg/pull/36739)) * Navigation block: Automatically generate navigation post title. ([36760](https://github.com/WordPress/gutenberg/pull/36760)) * Template Part block: Remove color, spacing, layout options and reusable block conversion. ([36571](https://github.com/WordPress/gutenberg/pull/36571)) ([36918](https://github.com/WordPress/gutenberg/pull/36918)) * Gallery block: Turn on auto-migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of v1 Gallery blocks to v2 format when edited.( [36191](https://github.com/WordPress/gutenberg/pull/36191)) * Update featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. placeholder graphic. ([36712](https://github.com/WordPress/gutenberg/pull/36712)) * Post Featured Image: Move width and height controls into the Dimensions panel via SlotFill. ([36540](https://github.com/WordPress/gutenberg/pull/36540)) #### Components * Font Size Picker: Allow non-integers as simple CSSCSS Cascading Style Sheets. values and in hints. ([36636](https://github.com/WordPress/gutenberg/pull/36636)) * Divider: Improve `vertical` and RTL support. ([36579](https://github.com/WordPress/gutenberg/pull/36579)) * ItemGroup: Experimenting with chevron icon. ([36654](https://github.com/WordPress/gutenberg/pull/36654)) * Toggle Group Control: Add tooltip. ([36726](https://github.com/WordPress/gutenberg/pull/36726)) * Modal: Support ref forwarding. ([36831](https://github.com/WordPress/gutenberg/pull/36831)) * ZStack: Support RTL layouts when applying `offset`. ([36769](https://github.com/WordPress/gutenberg/pull/36769)) #### Themes * Move the theme editor under tools for FSE themes. ([36723](https://github.com/WordPress/gutenberg/pull/36723)) * Update the block theme folders to templates and parts. ([36647](https://github.com/WordPress/gutenberg/pull/36647)) ### Bug Fixes #### Global Styles * Make the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. color palette opt-in for themes with not `theme.json`. ([36496](https://github.com/WordPress/gutenberg/pull/36496)) * Fix: Apply by slug on all origins. ([36841](https://github.com/WordPress/gutenberg/pull/36841)) * Fix: Theme colors cannot override defaults. ([36811](https://github.com/WordPress/gutenberg/pull/36811)) #### Block Library * Cover block: Fix undo trap. ([36807](https://github.com/WordPress/gutenberg/pull/36807)) * Navigation block: Add page list to navigation direct insert conditions. ([36591](https://github.com/WordPress/gutenberg/pull/36591)) * Navigation block: Fix Nav block editing wrong entity on creation of new Menu.( [36880](https://github.com/WordPress/gutenberg/pull/36880)) * Navigation block: Scale submenu icon. ([36714](https://github.com/WordPress/gutenberg/pull/36714))( [36948](https://github.com/WordPress/gutenberg/pull/36948)) * Navigation block: Fix non existent menu handling. ([36507](https://github.com/WordPress/gutenberg/pull/36507)) * Navigation block: Fix page list missing button styles when set to open on click.( [36601](https://github.com/WordPress/gutenberg/pull/36601)) * Navigation block: Include cascading properties in deprecation. ([36432](https://github.com/WordPress/gutenberg/pull/36432)) * Navigation block: Remove absorb toolbar prop. ([36990](https://github.com/WordPress/gutenberg/pull/36990)) * Navigation block: Add accessible labelling to submenu buttons. ([36631](https://github.com/WordPress/gutenberg/pull/36631)) * Navigation block: Fix space-between. ([36441](https://github.com/WordPress/gutenberg/pull/36441)) * Template Part block: Fix slug generation when creating through the block placeholder.( [36764](https://github.com/WordPress/gutenberg/pull/36764)) * Gallery block: Allow clicks within replace media placeholder state. ([36804](https://github.com/WordPress/gutenberg/pull/36804)) * Gallery block: Fix stuck image size options loader. ([36806](https://github.com/WordPress/gutenberg/pull/36806)) * Post Featured Image: Add a “Reset” button. ([36572](https://github.com/WordPress/gutenberg/pull/36572)) * Post Title block: Fix render error when setting Page to homepage. ([36786](https://github.com/WordPress/gutenberg/pull/36786)) * Query Pagination Next/Previous blocks: Remove text and link color support. ([36954](https://github.com/WordPress/gutenberg/pull/36954)) #### Site Editor * Stabilize theme export Rest APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) [https://developer.wordpress.org/rest-api/](https://developer.wordpress.org/rest-api/) endpoint. ([36559](https://github.com/WordPress/gutenberg/pull/36559)) ([36908](https://github.com/WordPress/gutenberg/pull/36908)) * Template list view fixes. ([36947](https://github.com/WordPress/gutenberg/pull/36947))( [36822](https://github.com/WordPress/gutenberg/pull/36822)) ([36705](https://github.com/WordPress/gutenberg/pull/36705)) * Templates Rest API endpoint: Add missing ‘is_custom’ prop. ([36911](https://github.com/WordPress/gutenberg/pull/36911)) * Templates Rest API endpoint: Add origin and author. ([36896](https://github.com/WordPress/gutenberg/pull/36896)) * Validate the postType query argument. ([36706](https://github.com/WordPress/gutenberg/pull/36706)) * Fix site editor region navigation. ([36709](https://github.com/WordPress/gutenberg/pull/36709)) * Navigation Sidebar: Add aria-current=”page” to active navigation item. ([36946](https://github.com/WordPress/gutenberg/pull/36946)) * Navigation Sidebar: Highlight “Site” in the navigation panel. ([36762](https://github.com/WordPress/gutenberg/pull/36762)) * Navigation Sidebar: Show all templates and template parts on the site editor list screens. ([36761](https://github.com/WordPress/gutenberg/pull/36761)) #### Components * Color Picker: Re-instate debounce and controlled value to fix issue with gradient picker. ([36941](https://github.com/WordPress/gutenberg/pull/36941)) * ColorPicker: Replace hardcoded “blue” with theme color. ([36153](https://github.com/WordPress/gutenberg/pull/36153)) * Tools Panel: Fix race conditions caused by conditionally displayed ToolsPanelItems.( [36588](https://github.com/WordPress/gutenberg/pull/36588)) * DateTimePicker: Set PM hours correctly. ([36878](https://github.com/WordPress/gutenberg/pull/36878)) * LinkControl: Fix wordbreak for URLs. ([36993](https://github.com/WordPress/gutenberg/pull/36993)) * Offset the parent iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser. when computing Popover position. ( [36876](https://github.com/WordPress/gutenberg/pull/36876)) * ToolsPanel: Prevent tools panel menu increasing empty panel height. ([36895](https://github.com/WordPress/gutenberg/pull/36895)) * Update destructive tertiary button styles, and template list. ([36915](https://github.com/WordPress/gutenberg/pull/36915)) #### Themes * Block Templates: Fix PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher notices on WP 5.8.( [36964](https://github.com/WordPress/gutenberg/pull/36964)) * Don’t try and render unstable location if Nav block has ID. ([36863](https://github.com/WordPress/gutenberg/pull/36863)) #### Design Tools * Border panel: Update to display multiple palette origins. ([36753](https://github.com/WordPress/gutenberg/pull/36753)) * Cover: Move BoxControlVisualizer in the markup to make it visible. ([36635](https://github.com/WordPress/gutenberg/pull/36635)) * Fix duotone first render in Safari. ([36754](https://github.com/WordPress/gutenberg/pull/36754)) #### Icons * [Icons]: Fix Comment Author Name icon. ([36738](https://github.com/WordPress/gutenberg/pull/36738)) * [Icons]: Fix property names for Comment Author Avatar icon. ([36737](https://github.com/WordPress/gutenberg/pull/36737)) #### Milaceanous * Block Styles: Add a separating margin to the default picker. ([36976](https://github.com/WordPress/gutenberg/pull/36976)) * Block Styles: Check for existence of scroll container. ([37010](https://github.com/WordPress/gutenberg/pull/37010)) * Data package: Update types and fix type error. ([36190](https://github.com/WordPress/gutenberg/pull/36190)) * Writing Flow Multi-select: Ensure post title content editable after multi-select.( [36843](https://github.com/WordPress/gutenberg/pull/36843)) * Insertion point bar: Hide onBlur and onMouseLeave. ([36798](https://github.com/WordPress/gutenberg/pull/36798)) * Dependency Extraction Webpack Plugin: Make the plugin work when using `optimizations. runtimeChunk = 'single'`. ([26214](https://github.com/WordPress/gutenberg/pull/26214)) * Fix document typo. ([36776](https://github.com/WordPress/gutenberg/pull/36776)) * Prevent CleanWebpackPlugin webpack plugin from deleting webpack assets. ([35986](https://github.com/WordPress/gutenberg/pull/35986)) * Hide the columns inserter in pattern previews. ([36626](https://github.com/WordPress/gutenberg/pull/36626)) * Update theme.json version. ([36917](https://github.com/WordPress/gutenberg/pull/36917)) * Multi-entity save: Only set site entity to pending if really saving. ([36573](https://github.com/WordPress/gutenberg/pull/36573)) * Widgets Editor: Add CSS fix for wp_footer called multiple times. ([36759](https://github.com/WordPress/gutenberg/pull/36759)) * Fix the templates REST API endpoint for the almost pretty permalink config. ( [36881](https://github.com/WordPress/gutenberg/pull/36881)) ### Performance * Improve performance of wp_navigation lookup. ([36891](https://github.com/WordPress/gutenberg/pull/36891)) ### Experiments * Add `__unstable-large` size variant on `InputControl` `SelectControl` `UnitControl`.( [35646](https://github.com/WordPress/gutenberg/pull/35646)) * Add experimental `ConfirmDialog`. ([34153](https://github.com/WordPress/gutenberg/pull/34153)) ### Documentation * Add brief information about blockGap to the theme.json how-to guide. ([36558](https://github.com/WordPress/gutenberg/pull/36558)) * Add placeholder in URLInput documentation. ([36799](https://github.com/WordPress/gutenberg/pull/36799)) * Block Supports: Update block supports documentation after typography reshaping.( [36894](https://github.com/WordPress/gutenberg/pull/36894)) * Alphabetize the How to Guides section. ([35904](https://github.com/WordPress/gutenberg/pull/35904)) * Fix broken link to wordpress/stylelint-config. ([36936](https://github.com/WordPress/gutenberg/pull/36936)) * Improvements on `Create a Block Tutorial` from `Block Editor handbook`. ([36553](https://github.com/WordPress/gutenberg/pull/36553)) * Update history.md with description of the page. ([36888](https://github.com/WordPress/gutenberg/pull/36888)) * Update Getting Started with info to stay informed. ([36498](https://github.com/WordPress/gutenberg/pull/36498)) * Update Pattern block categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. and add documentation. ([36144](https://github.com/WordPress/gutenberg/pull/36144)) * Various inline docblockdocblock (phpdoc, xref, inline docs) corrections. ([36793](https://github.com/WordPress/gutenberg/pull/36793)) * ToolsPanel: Update panel readme and stories. ([36557](https://github.com/WordPress/gutenberg/pull/36557)) * Change .nvmrc and documentation for Node.js version (LTS to 14.18.1). ([36744](https://github.com/WordPress/gutenberg/pull/36744)) ### Code Quality * Blocks: Refactor generator-based actions to thunks. ([36468](https://github.com/WordPress/gutenberg/pull/36468)) * Remove useless bubblesVirtually prop from BlockInspector. ([37024](https://github.com/WordPress/gutenberg/pull/37024)) * Remove EditPostSettings context provider. ([36949](https://github.com/WordPress/gutenberg/pull/36949)) * Report dependencies externalized with Dependency Extraction Plugin. ([35106](https://github.com/WordPress/gutenberg/pull/35106)) * Comment Author Avatar block: Escape styles attribute. ([36988](https://github.com/WordPress/gutenberg/pull/36988)) * Clarify i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/2021/page/3/?output_format=md#l10n). Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. context for PostTemplateActions’s “New” label. ([36679](https://github.com/WordPress/gutenberg/pull/36679)) * Data: Remove usage of deprecated register methods. ([36344](https://github.com/WordPress/gutenberg/pull/36344)) #### Global Styles * Move Global Styles code to `lib/compat/wordpress-5.9` folder. ([36978](https://github.com/WordPress/gutenberg/pull/36978)) * Rename `gutenberg_` to `wp_` for some functions that land in WordPress 5.9. ( [36913](https://github.com/WordPress/gutenberg/pull/36913)) * Update global styles public API. ([36610](https://github.com/WordPress/gutenberg/pull/36610)) * Update the `WP_Theme_JSON_Gutenberg` class to be like the core one. ([36973](https://github.com/WordPress/gutenberg/pull/36973)) * Update the `WP_Theme_JSON_Resolver_Gutenberg` class to be like the core one. ( [36974](https://github.com/WordPress/gutenberg/pull/36974)) * `theme.json`: Sort keys alphabetically. ([36968](https://github.com/WordPress/gutenberg/pull/36968)) * Update function names for the public global styles API functions. ([36907](https://github.com/WordPress/gutenberg/pull/36907)) #### Block Library * Navigation: Remove outdated separate “Home” link styles. ([36608](https://github.com/WordPress/gutenberg/pull/36608)) * Post Featured Image: Remove withNotices HOC. ([36596](https://github.com/WordPress/gutenberg/pull/36596)) * [Comment Author Avatar]: Remove extraneous color link support flag. ([36956](https://github.com/WordPress/gutenberg/pull/36956)) * Deprecate navigation areas. ([36981](https://github.com/WordPress/gutenberg/pull/36981))( [36727](https://github.com/WordPress/gutenberg/pull/36727)) * Remove unstable max pages attribute from Nav block. ([36877](https://github.com/WordPress/gutenberg/pull/36877)) * Remove reference to gutenberg_, swap with wp_. ([36652](https://github.com/WordPress/gutenberg/pull/36652)) * Add plugin metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. data to Nav Area block deprecation notice. ([36777](https://github.com/WordPress/gutenberg/pull/36777)) #### Testing * Reorganize end-to-end tests folders and files. ([36734](https://github.com/WordPress/gutenberg/pull/36734)) * Scripts: Upgrade Puppeteer to v11. ([36040](https://github.com/WordPress/gutenberg/pull/36040)) * Update template controller unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see [regression](https://make.wordpress.org/core/2021/page/3/?output_format=md#regression). now that author support is in WP core. ([36987](https://github.com/WordPress/gutenberg/pull/36987)) * end-to-end Tests: Fix failing image end-to-end test by waiting for required element.( [36982](https://github.com/WordPress/gutenberg/pull/36982)) * Remove block template resolution unit tests. ([36855](https://github.com/WordPress/gutenberg/pull/36855)) ## Performance  Benchmark | Version | Time to Render First Block | KeyPress Event (typing) | | Gutenberg 12.1 | 7.22s | 38.68ms | | Gutenberg 12.0 | 6.96s | 38.34ms | | WordPress 5.8 | 7.46s | 48.96ms | Thank you to [@critterverse](https://profiles.wordpress.org/critterverse/) for the assets included in this post, [@priethor](https://profiles.wordpress.org/priethor/) for coordinating the release process and proofreading and to all those who contributed to this release! [#block-editor](https://make.wordpress.org/core/tag/block-editor/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#gutenberg-new](https://make.wordpress.org/core/tag/gutenberg-new/) [ ](https://profiles.wordpress.org/estelaris/) [Estela Rueda](https://profiles.wordpress.org/estelaris/) 12:11 pm _on_ December 8, 2021 Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/)    # 󠀁[Dev chat agenda for December 8, 2021](https://make.wordpress.org/core/2021/12/08/dev-chat-agenda-for-december-8-2021/)󠁿 ## Announcements The WordPress 5.9 BetaBeta 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. 2 has landed, after a lot of very hard work by a lot of very dedicated contributors. [Please download and test!](https://wordpress.org/wordpress-5.9-beta2.zip) Also, in the beta period, work pivots to focus only on bugs that have shown up since feature freeze on November 9. ## Blogblog (versus network, site) posts of note [WordPress 5.9 Beta 2 ](https://wordpress.org/news/2021/12/wordpress-5-9-beta-2/) fixed 24 bugs reported by contributors and needs testing. If you can help, please report your findings on the announcement post. [The Editor Chat Summary](https://make.wordpress.org/core/2021/12/07/editor-chat-summary-1-december-2021/) highlights improvements made by the team. [Gutenberg 12.1 RC1 ](https://github.com/WordPress/gutenberg/releases/tag/v12.1.0-rc.1) was released. [@audrasjb](https://profiles.wordpress.org/audrasjb/) has the latest issue of [A Week in Core](https://make.wordpress.org/core/2021/12/07/a-week-in-core-december-6-2021/). And remember that [the release schedule has been revised.](https://make.wordpress.org/core/2021/11/22/wordpress-5-9-revised-release-schedule/) Got other posts that should get the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team’s attention? Please add them in the comments. ## Upcoming releases The current upcoming major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. is version 5.9. Beta 2 was launched and [Beta 3 is scheduled for 14 December](https://make.wordpress.org/core/5-9/). So far, 305 tickets were fixed and more bugs should arise with testing. ## Component Maintainers If you maintain a component and need help with beta fixes or other blockers as the 5.9 release moves forward, please plan to join the chat and update the group. ## Open Floor Add your topic to the comments, and enjoy priority for your topic at the beginning of Open Floor. ### See you Wednesday at 20:00 UTC! [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core](https://make.wordpress.org/core/tag/core/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [#agenda](https://make.wordpress.org/core/tag/agenda/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) # Post navigation [← Older posts](https://make.wordpress.org/core/2021/page/4/?output_format=md) [Newer posts →](https://make.wordpress.org/core/2021/page/2/?output_format=md)