Title: 2021 – Page 32 – Make WordPress Core

---

#  Yearly Archives: 2021

 [  ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
5:08 pm _on_ June 8, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/), [dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/)

# 󠀁[Dev Chat Agenda for June 9, 2021](https://make.wordpress.org/core/2021/06/08/dev-chat-agenda-for-june-9-2021/)󠁿

Here is the agenda for this week’s developer meetings to occur at the following 
times: [June 9, 2021 at 5:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210609T0500)
and [June 9, 2021 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210609T2000).

## Blogblog (versus network, site) Post Highlights

 * [A Week in Core – June 7, 2021](https://make.wordpress.org/core/2021/06/08/a-week-in-core-june-7-2021/)
 * [Editor](https://make.wordpress.org/core/2021/06/03/editor-chat-summary-2-june-2021/),
   [CSS](https://make.wordpress.org/core/2021/06/04/css-chat-summary-03-june-2021/)
   chat summaries
 * [What’s next in Gutenberg? (June 2021)](https://make.wordpress.org/core/2021/06/04/whats-next-in-gutenberg-june-2021/)
 * [WebP dev note](https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/)
 * [New Make/Project site](https://make.wordpress.org/project/2021/06/03/welcome-to-make-wordpress-org-project/)
 * [A New Design is Coming to WordPress News](https://wordpress.org/news/2021/06/a-new-design-is-coming-to-wordpress-news/)

## 󠀁[5.8 Schedule Review](https://make.wordpress.org/core/5-8/)󠁿

 * **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. 1 released
   yesterday, so now in Beta window with Beta 2 in 6 days on Tuesday, June 15th**
 * _Focus now fully on [tasks](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&type=task+(blessed)&milestone=5.8&col=id&col=summary&col=type&col=status&col=milestone&col=owner&col=priority&col=component&col=changetime&order=changetime)
   in the milestone and regressions found in Beta releases_
 * Next [Beta Scrub](https://make.wordpress.org/core/tag/bug-scrub+5-8/) before 
   Beta 2 is [Monday, June 14th 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210614T2000)
 * 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/32/?output_format=md#alpha-beta).
   1 in 20 days on Tuesday, June 29th
 * 5.8 release in 41 days on Tuesday, July 20th

## Components check-in and status updates

 * 5.8 plans and help needed
 * Check-in with each component for status updates.
 * Poll for components that need assistance.

## Open Floor

Do you have something to propose for the agenda, or a specific item relevant to 
the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group
can either give you the floor or bring up your topic for you accordingly.

This meeting happens in the [#core](https://wordpress.slack.com/messages/C02RQBWTW)
channel. To join the meeting, you’ll need an account on the [Making WordPress Slack](https://make.wordpress.org/chat/).

[#5-8](https://make.wordpress.org/core/tag/5-8/), [#agenda](https://make.wordpress.org/core/tag/agenda/),
[#dev-chat](https://make.wordpress.org/core/tag/dev-chat/)

 [  ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
10:43 am _on_ June 8, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[meta2952 ( 2 )](https://make.wordpress.org/core/tag/meta2952/), [meta4514 ( 2 )](https://make.wordpress.org/core/tag/meta4514/),
[meta4621 ( 2 )](https://make.wordpress.org/core/tag/meta4621/), [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)

# 󠀁[A Week in Core – June 7, 2021](https://make.wordpress.org/core/2021/06/08/a-week-in-core-june-7-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 May 31 and June
7, 2021.

 * 40 commits
 * 72 contributors
 * 53 tickets created
 * 5 tickets reopened
 * 77 tickets closed

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=06%2F07%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

### Administration

 * List Tables: Update spacing in action items on small screens – [#48546](https://core.trac.wordpress.org/ticket/48546),
   [#47895](https://core.trac.wordpress.org/ticket/47895)

### Application Passwords

 * Allow enter key to submit profile form – [#52849](https://core.trac.wordpress.org/ticket/52849)

### BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. Editor

 * Add a type property to allow Core to identify the source of the editor styles–
   [#53175](https://core.trac.wordpress.org/ticket/53175)
 * Add the Site Logo block’s server implementation – [#53247](https://core.trac.wordpress.org/ticket/53247)
 * Load the `WP_Theme_JSON_Resolver` class in `wp-admin/load-styles.php` – [#53175](https://core.trac.wordpress.org/ticket/53175)
 * Package updates for 5.8 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. 1 – [#52991](https://core.trac.wordpress.org/ticket/52991)
 * Update script versions – [#52991](https://core.trac.wordpress.org/ticket/52991)
 * Correct some docblocks added in [[50836]](https://core.trac.wordpress.org/changeset/50836)–
   [#50328](https://core.trac.wordpress.org/ticket/50328), [#52620](https://core.trac.wordpress.org/ticket/52620)
 * Fix failing block editor test – [#53301](https://core.trac.wordpress.org/ticket/53301)

### Boostrap/Load

 * Add 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. to allow disabling of object cache – [#53322](https://core.trac.wordpress.org/ticket/53322)
 * Only reference recovery mode email when it can be sent – [#52560](https://core.trac.wordpress.org/ticket/52560)

### Build/Test tools

 * Remove the `::append_to_selector()` method from `Tests_Theme_wpThemeJson` – [#52991](https://core.trac.wordpress.org/ticket/52991)
 * Use `assertSame()` in some newly introduced tests – [#52482](https://core.trac.wordpress.org/ticket/52482)

### Bundled Themes

 * Twenty Twenty-One: Check for navigation element before using it – [#52773](https://core.trac.wordpress.org/ticket/52773)

### Coding Standards

 * Extraneous white space at end of line – [#51189](https://core.trac.wordpress.org/ticket/51189)
 * Simplify a condition in `wp-admin/admin-footer.php` – [#53306](https://core.trac.wordpress.org/ticket/53306)
 * Simplify the logic in `WP_Widget::get_field_name()` and `::get_field_id()` – 
   [#16773](https://core.trac.wordpress.org/ticket/16773), [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Use strict comparison in `wp-admin/options-media.php` – [#52627](https://core.trac.wordpress.org/ticket/52627)

### Comments

 * Escape comment author’s email in the Edit Comment form – [#53349](https://core.trac.wordpress.org/ticket/53349)
 * Return valid comment reply link if comments are paginated – [#51189](https://core.trac.wordpress.org/ticket/51189)

### Documentation

 * Add a `@since` note to `wp_parse_id_list()` and `wp_parse_slug_list()` about 
   using `wp_parse_list()` – [#52628](https://core.trac.wordpress.org/ticket/52628)
 * Correct type for the `$widget` parameter of the `widget_block_content` filter–
   [#51566](https://core.trac.wordpress.org/ticket/51566)

### External Libraries

 * Update the Requests library to version 1.8.1 – [#53334](https://core.trac.wordpress.org/ticket/53334)

### Plugins

 * Make sure Hello Dolly translations are deleted when the 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. is deleted – [#52817](https://core.trac.wordpress.org/ticket/52817)

### 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/)󠁿

 * Add ‘delete_widget’ action to delete 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. endpoint – [#53289](https://core.trac.wordpress.org/ticket/53289)
 * Delete fresh_site option when updating widgets via REST API – [#53317](https://core.trac.wordpress.org/ticket/53317)
 * Fix delete widget endpoint – [#53313](https://core.trac.wordpress.org/ticket/53313)
 * Rename the `$creating` parameter of `rest_after_save_widget` action to `$update`–
   [#53317](https://core.trac.wordpress.org/ticket/53317)
 * Restore the `$creating` parameter of `rest_after_save_widget` action – [#53317](https://core.trac.wordpress.org/ticket/53317)

### Site Health

 * Conditionally run Authorization headerHeader The header of your site is typically
   the first thing people will experience. The masthead or header art located across
   the top of your page is part of the look and feel of your website. It can influence
   a visitor’s opinion about your content and you/ your organization’s brand. It
   may also look different on different screen sizes. test – [#52642](https://core.trac.wordpress.org/ticket/52642)
 * Remove unnecessary `function_exists()` checks from `WP_Site_Health::get_tests()`–
   [#52642](https://core.trac.wordpress.org/ticket/52642)

### Themes

 * Fix 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) issues with controls in themes screen – [#52649](https://core.trac.wordpress.org/ticket/52649)

### TinyMCE

 * Don’t attempt to initialize the same instance twice. Follow up to [[51082]](https://core.trac.wordpress.org/changeset/51082)–
   [#52133](https://core.trac.wordpress.org/ticket/52133), [#52050](https://core.trac.wordpress.org/ticket/52050)
 * Fix initialization when the editor is in a postbox by delaying it until `document.
   readyState === 'complete'` – [#52133](https://core.trac.wordpress.org/ticket/52133),
   [#52050](https://core.trac.wordpress.org/ticket/52050)

### Upgrade/Install

 * Remove parsing of `readme.txt` files for plugin or theme requirements – [#48520](https://core.trac.wordpress.org/ticket/48520),
   [#48515](https://core.trac.wordpress.org/ticket/48515), [#meta2952](https://meta.trac.wordpress.org/ticket/2952),
   [#meta4514](https://meta.trac.wordpress.org/ticket/4514), [#meta4621](https://meta.trac.wordpress.org/ticket/4621)

### Users

 * Add user’s localeLocale A locale is a combination of language and regional dialect.
   Usually locales correspond to countries, as is the case with Portuguese (Portugal)
   and Portuguese (Brazil). Other examples of locales include Canadian English and
   U.S. English. to password reset link to ensure login screen matches the language
   of the email – [#34281](https://core.trac.wordpress.org/ticket/34281), [#52605](https://core.trac.wordpress.org/ticket/52605),
   [#53321](https://core.trac.wordpress.org/ticket/53321)

### Widgets

 * Add `widget_block_content` filter – [#51566](https://core.trac.wordpress.org/ticket/51566)
 * Add missing actions to widgets block editor – [#53288](https://core.trac.wordpress.org/ticket/53288)
 * Enable 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. and Nav Menu widgets in Legacy Widget block – [#53301](https://core.trac.wordpress.org/ticket/53301)
 * Make new WordPress installations use blocks in widget areas instead of widgets–
   [#53324](https://core.trac.wordpress.org/ticket/53324)

## Props

**Thanks to the 72 people who contributed to WordPress Core on Trac last week:**

[@TimothyBlynJacobs](https://profiles.wordpress.org/timothyblynjacobs/) (4), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/)(
3), [@nosolosw](https://profiles.wordpress.org/nosolosw/) (3), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/)(
3), [@andraganescu](https://profiles.wordpress.org/andraganescu/) (3), [@alexstine](https://profiles.wordpress.org/alexstine/)(
3), [@costdev](https://profiles.wordpress.org/costdev/) (3), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/)(
2), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) (2), [@joyously](https://profiles.wordpress.org/joyously/)(
2), [@audrasjb](https://profiles.wordpress.org/audrasjb/) (2), [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)(
2), [@justinahinon](https://profiles.wordpress.org/justinahinon/) (1), [@jipmoors](https://profiles.wordpress.org/jipmoors/)(
1), [@westonruter](https://profiles.wordpress.org/westonruter/) (1), @drebbits.web(
1), [@afragen](https://profiles.wordpress.org/afragen/) (1), [@stevenkword](https://profiles.wordpress.org/stevenkword/)(
1), [@jorbin](https://profiles.wordpress.org/jorbin/) (1), [@lukecarbis](https://profiles.wordpress.org/lukecarbis/)(
1), [@jdgrimes](https://profiles.wordpress.org/jdgrimes/) (1), [@tamlyn](https://profiles.wordpress.org/tamlyn/)(
1), [@solarissmoke](https://profiles.wordpress.org/solarissmoke/) (1), [@5ubliminal](https://profiles.wordpress.org/5ubliminal/)(
1), [@helen](https://profiles.wordpress.org/helen/) (1), [@celloexpressions](https://profiles.wordpress.org/celloexpressions/)(
1), [@Mte90](https://profiles.wordpress.org/mte90/) (1), [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/)(
1), [@kevin940726](https://profiles.wordpress.org/kevin940726/) (1), [@garrett-eclipse](https://profiles.wordpress.org/garrett-eclipse/)(
1), [@y_kolev](https://profiles.wordpress.org/y_kolev/) (1), [@Clorith](https://profiles.wordpress.org/clorith/)(
1), [@Otshelnik-Fm](https://profiles.wordpress.org/otshelnik-fm/) (1), [@JeffPaul](https://profiles.wordpress.org/jeffpaul/)(
1), [@talldanwp](https://profiles.wordpress.org/talldanwp/) (1), [@WebDragon](https://profiles.wordpress.org/webdragon/)(
1), [@dlh](https://profiles.wordpress.org/dlh/) (1), [@pbiron](https://profiles.wordpress.org/pbiron/)(
1), [@jamil95](https://profiles.wordpress.org/jamil95/) (1), [@sushmak](https://profiles.wordpress.org/sushmak/)(
1), [@stevegrunwell](https://profiles.wordpress.org/stevegrunwell/) (1), [@aliveic](https://profiles.wordpress.org/aliveic/)(
1), [@mkdgs](https://profiles.wordpress.org/mkdgs/) (1), [@williampatton](https://profiles.wordpress.org/williampatton/)(
1), [@aristath](https://profiles.wordpress.org/aristath/) (1), [@timothyblynjacobs](https://profiles.wordpress.org/timothyblynjacobs/)(
1), [@ocean90](https://profiles.wordpress.org/ocean90/) (1), [@noisysocks](https://profiles.wordpress.org/noisysocks/)(
1), [@promz](https://profiles.wordpress.org/promz/) (1), [@poena](https://profiles.wordpress.org/poena/)(
1), [@metalandcoffee](https://profiles.wordpress.org/metalandcoffee/) (1), [@desrosj](https://profiles.wordpress.org/desrosj/)(
1), [@patkemper](https://profiles.wordpress.org/patkemper/) (1), [@herrvigg](https://profiles.wordpress.org/herrvigg/)(
1), [@spikeuk1](https://profiles.wordpress.org/spikeuk1/) (1), [@dway](https://profiles.wordpress.org/dway/)(
1), [@azaozz](https://profiles.wordpress.org/azaozz/) (1), [@notlaura](https://profiles.wordpress.org/notlaura/)(
1), [@MrPauloEn](https://profiles.wordpress.org/mrpauloen/) (1), [@paaggeli](https://profiles.wordpress.org/paaggeli/)(
1), [@engahmeds3ed](https://profiles.wordpress.org/engahmeds3ed/) (1), [@utsav72640](https://profiles.wordpress.org/utsav72640/)(
1), [@kapilpaul](https://profiles.wordpress.org/kapilpaul/) (1), [@jrf](https://profiles.wordpress.org/jrf/)(
1), [@schlessera](https://profiles.wordpress.org/schlessera/) (1), [@mbabker](https://profiles.wordpress.org/mbabker/)(
1), [@walbo](https://profiles.wordpress.org/walbo/) (1), [@reynhartono](https://profiles.wordpress.org/reynhartono/)(
1), [@Otto42](https://profiles.wordpress.org/otto42/) (1), [@arunsathiya](https://profiles.wordpress.org/arunsathiya/)(
1), [@danfarrow](https://profiles.wordpress.org/danfarrow/) (1), and [@mukesh27](https://profiles.wordpress.org/mukesh27/)(
1).

**Congrats and welcome to our 12 new contributors of the week!** [@costdev](https://profiles.wordpress.org/costdev/),
[@5ubliminal](https://profiles.wordpress.org/5ubliminal/), [@WebDragon](https://profiles.wordpress.org/webdragon/),
[@sushmak](https://profiles.wordpress.org/sushmak/), [@mkdgs](https://profiles.wordpress.org/mkdgs/),
[@patkemper](https://profiles.wordpress.org/patkemper/), [@herrvigg](https://profiles.wordpress.org/herrvigg/),
[@spikeuk1](https://profiles.wordpress.org/spikeuk1/), [@dway](https://profiles.wordpress.org/dway/),
[@MrPauloEn](https://profiles.wordpress.org/mrpauloen/), [@kapilpaul](https://profiles.wordpress.org/kapilpaul/),
and [@reynhartono](https://profiles.wordpress.org/reynhartono/). ♥️

**Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)(
15), [@noisysocks](https://profiles.wordpress.org/noisysocks/) (8), [@joedolson](https://profiles.wordpress.org/joedolson/)(
4), [@youknowriad](https://profiles.wordpress.org/youknowriad/) (3), [@jorbin](https://profiles.wordpress.org/jorbin/)(
2), [@azaozz](https://profiles.wordpress.org/azaozz/) (2), [@ryelle](https://profiles.wordpress.org/ryelle/)(
2), [@ocean90](https://profiles.wordpress.org/ocean90/) (1), [@johnbillion](https://profiles.wordpress.org/johnbillion/)(
1), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (1), and [@clorith](https://profiles.wordpress.org/clorith/)(
1).

[#5-8](https://make.wordpress.org/core/tag/5-8/), [#meta2952](https://make.wordpress.org/core/tag/meta2952/),
[#meta4514](https://make.wordpress.org/core/tag/meta4514/), [#meta4621](https://make.wordpress.org/core/tag/meta4621/),
[#week-in-core](https://make.wordpress.org/core/tag/week-in-core/)

 [  ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/)
9:34 am _on_ June 8, 2021     
Tags: [core-auto-updates ( 37 )](https://make.wordpress.org/core/tag/core-auto-updates/),
[updater ( 21 )](https://make.wordpress.org/core/tag/updater/), [upgrade-install ( 32 )](https://make.wordpress.org/core/tag/upgrade-install/)

# 󠀁[Upgrade/Install component meeting agenda for June 8th, 2021](https://make.wordpress.org/core/2021/06/08/upgrade-install-component-meeting-agenda-for-june-1st-2021-2/)󠁿

The next meeting is scheduled on [Tuesday, June 8th, 2021, at 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210608T1700)
and will take place on [#core-auto-updates](https://wordpress.slack.com/archives/CULBN711P/p1583863308013300)
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 with the following agenda:

 * Triagetriage The act of evaluating and sorting bug reports, in order to decide
   priority, severity, and other factors. of the tickets in the [spreadsheet](https://docs.google.com/spreadsheets/d/19A4D_nIbC_hJCnBZeJxAbfZjbwqsZ3Z_YgzToey0R5Y/edit#gid=0)(
   they all refer to Outcome 1 of the [Updater](https://make.wordpress.org/core/2021/05/03/feature-project-updates-on-updating-the-updaters/#comment-41272)
   initiative)
 * Status update on the [rollback for failed plugin/theme updates](https://core.trac.wordpress.org/ticket/51857)
 * Open floor/tickets awaiting review

Got something to propose for the agenda? Please leave a comment below.

[#core-auto-updates](https://make.wordpress.org/core/tag/core-auto-updates/), [#updater](https://make.wordpress.org/core/tag/updater/),
[#upgrade-install](https://make.wordpress.org/core/tag/upgrade-install/)

 [  ](https://profiles.wordpress.org/adamsilverstein/) [Adam Silverstein](https://profiles.wordpress.org/adamsilverstein/)
8:22 pm _on_ June 7, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[core-images ( 9 )](https://make.wordpress.org/core/tag/core-images/), [dev-notes ( 647 )](https://make.wordpress.org/core/tag/dev-notes/),
[images ( 10 )](https://make.wordpress.org/core/tag/images/)   

# 󠀁[WordPress 5.8 adds WebP support](https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/)󠁿

[WebP](https://developers.google.com/speed/webp) is a modern image format that provides
improved lossless and lossy compression for images on the web. WebP images are around
30% smaller on average than their JPEG or PNG equivalents, resulting in sites that
are faster and use less bandwidth. WebP is supported in all modern browsers [according to caniuse](https://caniuse.com/webp).

From WordPress version 5.8 forward, you can upload and use WebP images in WordPress
like you would a JPEG or PNG image today (as long as your hosting service supports
WebP). Switching to the WebP format for your images will improve your site’s performance
and your site visitor’s experience. 

## How WebP Helps You

WebP images are significantly smaller than their JPEG equivalents, so visitors to
your site will see the complete page loaded more quickly. Smaller images take less
bandwidth to transmit, and your images still get all of the responsive benefits 
of `srcset` and lazy loading by default. Finally, WebP is supported in all major
browsers, so most sites can start using them today.

## Creating WebP images

Image editing tools support exporting in WebP, or you can also use command line 
[conversion tools](https://developers.google.com/speed/webp/docs/precompiled) or
web based tools like [Squoosh](https://squoosh.app). Once you save your images as
WebP, upload them to WordPress and use them like you would any other image. 

## Using WebP images

WebP images work like any other image in WordPress with some small caveats. 

WebP images support lossy and lossless compression, as well as an animated format
and support for transparent images. In WordPress, the _lossless WebP_ format is 
only supported when the hosting server uses Imagick (the PHPPHP The web scripting
language in which WordPress is primarily architected. WordPress requires PHP 7.4
or higher library) until LibGD [adds support](https://github.com/libgd/libgd/pull/698).
In addition, animated and alpha formats are not yet supported for resized images(
lossy images are created instead when you upload in these formats).

WebP support in the media library requires that your web server’s image processing
library (WordPress supports both Imagick and LibGD) supports the WebP format. Fortunately
these libraries have supported WebP for quite a while so support is widely available.
If your web server does not support WebP, you will see an error message when you
try to upload a WebP image.

If your audience includes a significant number of users on an unsupported browser(
IE11 for example), either avoid using WebP images, or  enqueue a [browser polyfill](https://github.com/chase-moskal/webp-hero).

## Plans for the future

The media component team is also exploring the option of having WordPress perform
the image format conversion on uploaded images – using WebP as the default output
format for sub-sized images. You can track progress and test this feature on the
[trac ticket](https://core.trac.wordpress.org/ticket/52867). We are also keeping
our eyes on even more modern formats like AVIF and JPEGXL that will both improve
compression and further reduce resources required for compression.

## FAQ

### How can I fine tune the compression quality setting used for WebP images?

Developers or plugins can use the `wp_editor_set_quality` 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. to set the quality setting. The passed mime type enables setting by type,
for example:

    ```notranslate
    // Use a quality setting of 75 for WebP images.
    function filter_webp_quality( $quality, $mime_type ) {
      if ( 'image/webp' === $mime_type ) {
         return 75;
      }
      return $quality;
    }
    add_filter( 'wp_editor_set_quality', 'filter_webp_quality', 10, 2 );
    ```

### What happens if I enable the filter to use WebP sub-sizes, but upload JPEG? Do the sub-sizes have to match the original?

By default, WordPres creates the sub-sized images of the same type as the uploaded
file, so uploaded WebP files to get WebP files on your site. If you want to experiment
with uploading JPEG and having WordPress auto-convert these to WebP for your sub-
sized images, check out this [plugin](https://github.com/adamsilverstein/wordpress-modern-images)(
related [trac ticket](https://core.trac.wordpress.org/ticket/52867)).

### If I use WordPress multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also **network**, **blog**, **site**, will all my sites work with WebP images?

No. Multisite stores the file types that users are allowed to upload when a site
is created. We are working on improving this in [#53167](https://core.trac.wordpress.org/ticket/53167).
In the meantime, to ensure all existing sites on a networknetwork (versus site, 
blog) allow WebP files, you can use the `site_option` filter in a network mu-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. to add `webp` to the allowed file
types for all network sites:

    ```notranslate
    // Ensure all network sites include WebP support.
    add_filter(
      'site_option_upload_filetypes',
      function ( $filetypes ) {
        $filetypes = explode( ' ', $filetypes );
        if ( ! in_array( 'webp', $filetypes, true ) ) {
          $filetypes[] = 'webp';
        }
        $filetypes   = implode( ' ', $filetypes );

        return $filetypes;
      }
    );
    ```

[#5-8](https://make.wordpress.org/core/tag/5-8/), [#core-images](https://make.wordpress.org/core/tag/core-images/),
[#dev-notes](https://make.wordpress.org/core/tag/dev-notes/), [#images](https://make.wordpress.org/core/tag/images/)

 [  ](https://profiles.wordpress.org/paaljoachim/) [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)
6:59 pm _on_ June 7, 2021     
Tags: [agenda ( 1,142 )](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/),
[meetings ( 14 )](https://make.wordpress.org/core/tag/meetings/)   

# 󠀁[Editor Chat Agenda: 10 June 2021](https://make.wordpress.org/core/2021/06/07/editor-chat-agenda-9-june-2021/)󠁿

**Moved to Thursday 10th June same time because of WordCampWordCamp WordCamps are
casual, locally-organized conferences covering everything related to WordPress. 
They're one of the places where the WordPress community comes together to teach 
one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/).
EU.**

Facilitator and notetaker: [@ajitbohra](https://profiles.wordpress.org/ajitbohra/)

This is the agenda for the weekly _editor chat_ scheduled for [Thursday, June 10, 2021, 0](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210610T16&p1=187&ah=1)
[4:00 PM GMT+1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210331T10&p1=2157&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/)._

 * [Gutenberg 10.7](https://github.com/WordPress/gutenberg/releases/tag/v10.7.0)
   final release for WordPress 5.8.
 * [WordPress 5.8 project board](https://github.com/WordPress/gutenberg/projects/55)
 * [Help Test the Widgets Editor for WordPress 5.8](https://make.wordpress.org/core/2021/05/12/help-test-the-widgets-editor-for-wordpress-5-8/)
 * [Monthly Plan for June 2021](https://make.wordpress.org/core/2021/06/04/whats-next-in-gutenberg-june-2021/)
   and key project updates:
    - Global Styles.
 *  - 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. based 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. Editor.
    - Navigation block.
    - Full Site Editing.
    - Mobile
 * 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 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/), 
[#meetings](https://make.wordpress.org/core/tag/meetings/)

 [  ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
8:09 am _on_ June 5, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/)

# 󠀁[DevChat meeting Summary – June 2, 2021](https://make.wordpress.org/core/2021/06/05/devchat-meeting-summary-june-2-2021/)󠁿

[@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) and [@jeffpaul](https://profiles.wordpress.org/jeffpaul/)
led the weekly meetings of the WordPress CoreCore Core is the set of software required
to run WordPress. The Core Development Team builds WordPress. team, respectively
at 05:00 UTC and 20:00 UTC. Here is the [meeting agenda](https://make.wordpress.org/core/2021/06/01/dev-chat-agenda-for-june-2-2021/).

[Link to 05:00 UTC devchat meeting on the core channel on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1622610252216600)

[Link to 20:00 UTC devchat meeting on the core channel on Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1622664004255100)

## Blogblog (versus network, site) post hightlights

In the last [“Week in Core” issue](https://make.wordpress.org/core/2021/06/01/a-week-in-core-may-31-2021/),
[@audrasjb](https://profiles.wordpress.org/audrasjb/) featured 98 contributors, 
13 new contributors to WordPress source code and 12 core committers.

[@priethor](https://profiles.wordpress.org/priethor/) [shared details on Gutenberg 10.7](https://make.wordpress.org/core/2021/05/27/whats-new-in-gutenberg-10-7-26-may/)
including new features like the persistent List View in the Post Editor, responsive
navigation menus, many design tools for blocks, and enhancements to the top toolbar,
as well as iterative performance improvements and a lot of 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.

[@danfarrow](https://profiles.wordpress.org/danfarrow/) shared CSSCSS Cascading 
Style Sheets. team updates on color scheming, CSS audit, and CSS deprecation path
from their last two meetings. For more information, see CSS chat summaries for [May 20th](https://make.wordpress.org/core/2021/05/27/css-chat-summary-20-may-2021/)
and [May 27th](https://make.wordpress.org/core/2021/05/28/css-chat-summary-27-may-2021/).

## Blog posts that need feedback

[@annezazu](https://profiles.wordpress.org/annezazu/) extended the [FSE Program Testing Call #7](https://make.wordpress.org/test/2021/05/26/fse-program-testing-call-7-polished-portfolios/)
from June 9th to June 16th, so please check the post to learn about the feature 
overview, how to set up your testing environment, and the desired testing flow to
help out on this.

[@webcommsat](https://profiles.wordpress.org/webcommsat/) has a related ask ahead
of Friday’s deadline for [suggestions of external channels for the promotion/info share on FSE to various audiences](https://make.wordpress.org/marketing/2021/06/02/suggestions-for-external-channels-on-fse-info/).
Everyone is welcome to review and add suggestions in the comments.

[@meaghanthompson](https://profiles.wordpress.org/meaghanthompson/) shared a [call for testing the WordPress iOS 17.5 beta](https://make.wordpress.org/mobile/2021/06/01/call-for-testing-wordpress-for-ios-17-5/),
so please check the post to learn about what’s new in the release, what’s most in
need of testing, how to set up the test app, and how to report issues you find.

## WordPress 5.8 update

[@jeffpaul](https://profiles.wordpress.org/jeffpaul/) shared a **5.8 schedule reminder**:
we are now in the **Feature Freeze period** where focus shifts away from enhancements
and feature requests to **defects and tasks**.

[@chaion07](https://profiles.wordpress.org/chaion07/) and [@francina](https://profiles.wordpress.org/francina/)
led different bug scrubs this past week. There’s a final bug scrub on Monday, June
7th at 20:00 UTC to work to clear the milestone before the 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. 1 release the next day. Here is the [full bug scrubs schedule](https://make.wordpress.org/core/2021/05/05/bug-scrub-schedule-for-5-8/).

The next milestone will be **Beta 1 on Tuesday June 8, 2021** after which point 
the focus will shift to testing and fixing bugs discovered during the 3 weeks beta
period.

There are two “big” remaining tasks and a call for help from [@youknowriad](https://profiles.wordpress.org/youknowriad/):

 * The Query blockBlock Block is the abstract term used to describe units of markup
   that, composed together, form the content or layout of a webpage using the WordPress
   editor. The idea combines concepts of what in the past may have achieved with
   shortcodes, custom HTML, and embed discovery into a single consistent API and
   user experience. where the GutenbergGutenberg The Gutenberg project is the new
   Editor Interface for WordPress. The editor improves the process and experience
   of creating new content, making writing rich content much simpler. It uses ‘blocks’
   to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
   team had some feedback about it being too powerful (need to find better heuristics
   to disable editing there). Feel free to [contribute to the discussion](https://github.com/WordPress/gutenberg/issues/30910).
   There is also [a subset of this issue](https://github.com/WordPress/gutenberg/issues/32317).
 * [A proposal](https://github.com/WordPress/gutenberg/pull/31971) to change in 
   how edited block templates are linked to themes (using theme mod instead of taxonomies).
   The Gutenberg team would appreciate some thoughts here from Core folks familiar
   with these APIs (theme mods, performance, database).

Also, these are [the dev notes that need to be written for the editor](https://github.com/WordPress/gutenberg/issues/32365).

[@youknowriad](https://profiles.wordpress.org/youknowriad/) shared that he consider
that the Core team is ready for Beta 1, ideally, we’d have some improvements for
the Query block by then but not sure if it’s necessary for beta 1.

### WP 5.8 Docs focus update

[@milana_cap](https://profiles.wordpress.org/milana_cap/) shared that out of 165
tickets, 35 (Gutenberg excluded) are marked for some sort of documentation:

 * 28 for 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.
 * 5 for updating DevHub
 * 12 for updating HelpHub

Gutenberg will have:

 * 10 dev notes (as per the list shared by [@youknowriad](https://profiles.wordpress.org/youknowriad/))
 * 12 updates for dev docs
 * many updates for end user docs

Everything except block editor end user updates can be found [in this spreadsheet](https://docs.google.com/spreadsheets/d/1RS0BEwy8pNNHR7P_nZ3yKcgWKVABbEn9RMjja-wkJwY/edit?usp=sharing).
Block editor end user updates can be found [in this Drive folder](https://drive.google.com/drive/folders/1RH4hDt-ZL2LJJIj9SevGSWaU2Fs7jjOy).

Docs needs the most help with end user documentation. For block editor in particular.
Some changes from 5.6 and 5.7 are still not published and we had a significant drop
in number of contributors due to pandemic situation. Anyone interested in getting
involved please pingPing The act of sending a very small amount of data to an end
point. Ping is used in computer science to illicit a response from a target server
to test it’s connection. Ping is also a term used by Slack users to @ someone or
send them a direct message (DM). Users might say something along the lines of “Ping
me when the meeting starts.” [@milana_cap](https://profiles.wordpress.org/milana_cap/)(**
zzap** 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/)).

## Components check-in and status updates

Build/Test Tools, Date/Time, 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/32/?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 ([@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)):
No major news this week.

Upgrade/Install ([@audrasjb](https://profiles.wordpress.org/audrasjb/)): [@francina](https://profiles.wordpress.org/francina/)
hosted the weekly meeting and [posted the meeting notes](https://make.wordpress.org/core/2021/06/01/upgrade-install-component-meeting-notes-from-june-1st-2021/).

Menus, Widgets ([@audrasjb](https://profiles.wordpress.org/audrasjb/)): no major
news this week.

## Open floor

[@poena](https://profiles.wordpress.org/poena/) [has a request on the agenda post](https://make.wordpress.org/core/2021/06/01/dev-chat-agenda-for-june-2-2021/#comment-41373)
for anyone with knowledge on adminadmin (and super admin) pointers:

> Theme Check is 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. used to analyze themes submitted
> to the theme directory. I’m looking for someone who knows about admin pointers
> and if [this issue from 2016](https://github.com/WordPress/theme-check/issues/126)
> is still valid. Does the core team want themes with `wp_enqueue_script( ‘wp-pointer’);`
> or `wp_enqueue_style( ‘wp-pointer’ );` to be blocked from the theme directory?
> The theme would not be able to be uploaded.

If you’re experienced with admin pointers, please respond to the comment on the 
agenda post or respond in the linked 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/)
issue above.

[@webcommsat](https://profiles.wordpress.org/webcommsat/) pointed out that [WordCamp Europe is Monday to Wednesday next week!](https://europe.wordcamp.org/2021/schedule/)

[#5-8](https://make.wordpress.org/core/tag/5-8/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/),
[#summary](https://make.wordpress.org/core/tag/summary/)

 [  ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/)
9:27 pm _on_ June 4, 2021     
Tags: [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/),
[gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-next ( 23 )](https://make.wordpress.org/core/tag/gutenberg-next/)

# 󠀁[What’s next in Gutenberg? (June 2021)](https://make.wordpress.org/core/2021/06/04/whats-next-in-gutenberg-june-2021/)󠁿

This monthly status update contains the high-level items that 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/) contributors
are focusing on for June. Please join us in our efforts and let us know in the comments
if anything is blocking you from doing so.

**How to follow along with Gutenberg:**

[Here’s an overview of different ways](https://make.wordpress.org/core/2020/05/20/ways-to-keep-up-with-full-site-editing-fse/)
to keep up with Gutenberg and the Full Site Editing project. There is also an index
page of [Gutenberg development-related posts](https://make.wordpress.org/core/handbook/references/keeping-up-with-gutenberg-index/)
and a [Site Editing Milestone overview issue](https://github.com/WordPress/gutenberg/issues/24551)
that breaks down the upcoming work into more concrete next steps.

## WordPress 5.8 focuses

With [WordPress 5.8 Beta 1 planned for June 8](https://make.wordpress.org/core/2021/03/30/5-8-pre-planning/),**
the priorities for the month heavily focus on stabilizing, testing, 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. fixing, and documenting the features recently merged in coreCore Core 
is the set of software required to run WordPress. The Core Development Team builds
WordPress.**, which can be followed in the [WordPress 5.8 project board](https://github.com/WordPress/gutenberg/projects/55).
However, design and development in other Gutenberg areas continue as well, and contributions
are welcome!

The remaining tasks for 5.8 include:

 * Audit correct [editability of content with FSE blocks](https://github.com/WordPress/gutenberg/issues/26573#issuecomment-848582711)
 * [Use theme mods for templates and template parts](https://github.com/WordPress/gutenberg/pull/31971)
 * Polish some Query BlockBlock Block is the abstract term used to describe units
   of markup that, composed together, form the content or layout of a webpage using
   the WordPress editor. The idea combines concepts of what in the past may have
   achieved with shortcodes, custom HTML, and embed discovery into a single consistent
   API and user experience. aspects, including:
    - Prevent editing post content by mistake in a query loopLoop The Loop is PHP
      code used by WordPress to display posts. Using The Loop, WordPress processes
      each post to be displayed on the current page, and formats it according to
      how it matches specified criteria within The Loop tags. Any HTML or PHP code
      in the Loop will be processed on each post. [https://codex.wordpress.org/The_Loop](https://codex.wordpress.org/The_Loop)
      by [disabling editing content by default](https://github.com/WordPress/gutenberg/issues/32317).
    - [Clarify the “inherit query” setting](https://github.com/WordPress/gutenberg/issues/31113)
      and [set its default value according to the context](https://github.com/WordPress/gutenberg/pull/32230).
    - [Rename the Query and Loop blocks](https://github.com/WordPress/gutenberg/pull/32283).
 * [Write Dev Notes](https://github.com/WordPress/gutenberg/issues/32365)

## Widgets Editor

Work on the block-based Widgets Editor is a continued focus. The main efforts target
stabilizing and documenting the editor and the customizerCustomizer Tool built into
WordPress core that hooks into most modern themes. You can use it to preview and
modify many of your site’s appearance settings. block editor, as well as deciding
[whether the Widgets Editor should be enabled by default](https://github.com/WordPress/gutenberg/issues/26154).

If you want to help us test the block-based Widgets Editor, drop by the [Widgets Editor Call for Testing](https://make.wordpress.org/core/2021/05/12/help-test-the-widgets-editor-for-wordpress-5-8/)
and report on your experience!

**Follow along:**

You can find more information about the current work in progress in this [tracking issue](https://github.com/WordPress/gutenberg/issues/24687),
as well as[ on this project board](https://github.com/WordPress/gutenberg/projects/27).
Moreover, you can join [#feature-widgets-block-editor](https://make.wordpress.org/core/tag/feature-widgets-block-editor/)
in 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/) 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/)
for future 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. Editor-focused meetings.

## Navigation Editor

Like the Widgets Editor, the Navigation Editor aims to help expand what’s possible
with menus while bringing block functionality to yet another part of WordPress and
offer a more modern experience. Current efforts include:

 * Continue defining Navigation Editor architecture.
 * Provide a [better way to disable/enable Navigation block features](https://github.com/WordPress/gutenberg/issues/30007)
   for the Navigation editor by [defining allowed inner blocks in the Navigation block via the block supports mechanism](https://github.com/WordPress/gutenberg/pull/32426).

**Follow along:**

You can follow the progress of this project [on this project board](https://github.com/WordPress/gutenberg/projects/31)
or review the new [Navigation Editor tracking issue](https://github.com/WordPress/gutenberg/issues/29102)
and join[ #feature-navigation-block-editor](https://wordpress.slack.com/archives/C01KDAZJMQ9)
in WordPress.org Slack.

## Full Site Editing

Work on this major focus for phase 2 is ongoing and is expected to [continue as a big-picture goal for 2021](https://make.wordpress.org/updates/2021/01/21/big-picture-goals-2021/).
Apart from all the features making it into 5.8, this is the status of the different
FSE areas and their upcoming work:

Milestone 1 – [Site Editing Infrastructure and UI](https://github.com/WordPress/gutenberg/issues/24818)

 * As the Template Editing Mode is landing in 5.8, efforts focus on testing and 
   stabilizing this feature. If you would like to help, check the [current FSE Outreach Program round](https://make.wordpress.org/test/2021/05/26/fse-program-testing-call-7-polished-portfolios/)
   focused on Template Editing Mode!

Milestone 3 – [Global Styles](https://github.com/WordPress/gutenberg/issues/20331)

 * The first version of Global Styles has been merged in core, and focuses need 
   to be revisited. Any relevant update will be posted in [this GitHub issue](https://github.com/WordPress/gutenberg/issues/20331#issuecomment-848685044)
   on demand.

Milestone 4 – [Theme Blocks](https://github.com/WordPress/gutenberg/issues/22724)

 * With most [theme blocks](https://github.com/WordPress/gutenberg/issues/28744)
   merged in core, it’s time to polish the Site Logo block’s design and [bring feature parity with the Image block](https://github.com/WordPress/gutenberg/issues/30406).
 * Similarly, the [Site Title](https://github.com/WordPress/gutenberg/issues/30918)
   and [Site Tagline](https://github.com/WordPress/gutenberg/issues/30921) blocks
   require varnishing to bring feature parity with other text blocks.
 * Because Post-related blocks (Post Title, Post Date, etc.) behavior varies depending
   on the context they are in (post, template, or Query), it would be nice to [make their descriptions context-aware](https://github.com/WordPress/gutenberg/issues/32319).

Milestone 5 – [Query Block](https://github.com/WordPress/gutenberg/issues/24762)

 * With great power comes great responsibility; because the Query Block is so powerful,
   contributors are making sure it lands in the best status possible in 5.8 as mentioned
   in the [“WordPress 5.8 focuses” section above](https://make.wordpress.org/core/2021/page/32/?output_format=md#wordpress-58-focuses).

Further work on the Query block not limited to 5.8 includes:

 * [Refine the Posts List block](https://github.com/WordPress/gutenberg/issues/32268)(
   Query block variation)
 * To improve the user experience when inserting and modifying an existing Query
   block, creating [a UI that suggests patterns that are contextual](https://github.com/WordPress/gutenberg/issues/28736)
   to the currently selected block

Milestone 6 – [Navigation Block](https://github.com/WordPress/gutenberg/issues/27593)

 * The main focus within the Navigation Block is to support [non-li inner blocks](https://github.com/WordPress/gutenberg/issues/29036)
   generating valid, semantic, accessible markup. There is a [discussion regarding the best approach for solving the navigation markup challenges](https://github.com/WordPress/gutenberg/issues/31951),
   and contributors are moving forward with having a [different markup in the frontend and the editor](https://github.com/WordPress/gutenberg/pull/30551).
 * Add an option to render the block [using a classic navigation data source](https://github.com/WordPress/gutenberg/pull/30852).

**Follow along:**

You can follow the progress of this project with this overview issue showing [key milestones for site editing](https://github.com/WordPress/gutenberg/issues/24551).
For each major milestone, there are related issues you can follow if you want a 
more granular look at each next step.

If you’re interested in testing Full Site Editing, check out the [FSE Outreach Program to learn more](https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/).
If you have questions about Full Site Editing, [check out this recent effort to offer answers.](https://make.wordpress.org/test/tag/fse-answers/)

## Areas to be aware of

**WCEU 2021**

[WordCamp Europe 2021 is scheduled for 7 to 9 June 2021](https://europe.wordcamp.org/2021/)
as an online event and will include several sessions related to Gutenberg, such 
as:

 * Full Site Editing (Discussion Panel)
 * A walkthrough of Full Site Editing (Workshop)
 * The Future of Themes in WordPress (Discussion Panel)
 * Blazing fast block development (Talk)

Make sure to [register](https://europe.wordcamp.org/2021/registration/) if you haven’t
already!

**Theme Developers**

 * The Themes team held a [“Universal Themes” Hallway Hangout](https://make.wordpress.org/themes/2021/05/10/friday-may-14th-at-14utc/).
   Check out the [summary and recording of the event](https://make.wordpress.org/themes/2021/05/10/friday-may-14th-at-14utc/#comment-44246)
   to know more about this upcoming way to build themes that work both with the 
   Site Editor and the Customizer as a fallback, not simultaneously, if the former
   is not available.

**Calls for testing**

 * Help test the [Widgets Editor for WordPress 5.8](https://make.wordpress.org/core/2021/05/12/help-test-the-widgets-editor-for-wordpress-5-8/).
 * Help with the [seventh FSE Outreach Program call for testing](https://make.wordpress.org/test/2021/05/26/fse-program-testing-call-7-polished-portfolios/)
   by building a polished portfolio. This has been **extended to June 16th** to 
   give folks more time to respond!

**Block Patterns**

 * Since [Gutenberg 10.7](https://make.wordpress.org/core/2021/05/27/whats-new-in-gutenberg-10-7-26-may/),
   block patterns displayed in the inserter are fetched from the [WordPress.org Pattern Directory](https://wordpress.org/patterns/).
   This opens the door to having a big amount of wonderful patterns available in
   the inserter, which will require [iterating on the pattern insertion experience](https://github.com/WordPress/gutenberg/issues/31153).
   For more updates on the Pattern Directory, stay tuned for [Block Pattern Directory updates](https://make.wordpress.org/meta/2021/04/28/block-pattern-directory-update/)
   and check the most recent [design iterations for the Pattern Directory](https://make.wordpress.org/design/tag/patterns-directory/).

## Ways to Get Involved

While the above items are our focuses, don’t forget that you can always help with
[triage](https://developer.wordpress.org/block-editor/contributors/triage/), [testing issues](https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is%3Aissue+label%3A%22Needs+Testing%22),
[good first issues](https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is%3Aissue+label%3A%22Good+First+Issue%22),
and [reviewing PRs](https://github.com/WordPress/gutenberg/tree/master/packages/env).
In particular, if you’re interested in helping with triagetriage The act of evaluating
and sorting bug reports, in order to decide priority, severity, and other factors.
but don’t know where to start, there’s a course on Learn WordPress for [how to do triage in GitHub!](https://learn.wordpress.org/workshop/how-to-do-triage-on-github/)
Check it out and join us.

If there’s anything we can do to make contributing easier, let us know in the comments
or in [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7) chats. While
we can’t promise to fix everything, we’d appreciate being aware of any blockers.

**Meetings to join:**

While you can [view all meetings here](https://make.wordpress.org/meetings/), here
are specific meetings to join depending on your interest. Remember that you need
a [WordPress.org slack account](https://make.wordpress.org/chat/) to participate:

 * Core Editor weekly Wednesdays @ 14:00 UTC in [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7)
   focused on all things Gutenberg.
 * Block Themes meeting twice monthly on Wednesday @ 16:00 UTC in [#themereview](https://wordpress.slack.com/archives/C02RP4Y3K)
   focused on preparing for Full Site Editing.

_Thanks [@andreamiddleton](https://profiles.wordpress.org/andreamiddleton/)_ and_
[@cbringmann](https://profiles.wordpress.org/cbringmann/) for reviewing this post._

[#core-editor](https://make.wordpress.org/core/tag/core-editor/) [#gutenberg-next](https://make.wordpress.org/core/tag/gutenberg-next/)
[#gutenberg](https://make.wordpress.org/core/tag/gutenberg/)

 [  ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/)
9:05 am _on_ June 4, 2021     
Tags: [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/),
[summary ( 975 )](https://make.wordpress.org/core/tag/summary/)   

# 󠀁[CSS Chat Summary: 03 June 2021](https://make.wordpress.org/core/2021/06/04/css-chat-summary-03-june-2021/)󠁿

[The meeting took place here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1622754351165200).
[@notlaura](https://profiles.wordpress.org/notlaura/) facilitated and [@danfarrow](https://profiles.wordpress.org/danfarrow/)
wrote up these notes.

## Housekeeping

 * [@danfarrow](https://profiles.wordpress.org/danfarrow/) offered to run the next
   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. scrub ([01 July @ 20:00UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+CSS+bug+scrub&iso=20210701T20&p1=1440&ah=1))–
   thanks me!

## Project updates

### Color Scheming (󠀁[#49999](https://core.trac.wordpress.org/ticket/49999)󠁿)

 * We now have [a public shared doc](https://docs.google.com/document/d/1Z0Wo1W0ZQwFJYPcJ8GlsubA9uKhcFdT8ifYnso82z9I/edit?usp=sharing)
   in which to begin documenting naming conventions for custom properties
 * [@colorful-tones](https://profiles.wordpress.org/colorful-tones/) noticed that
   [#49999](https://core.trac.wordpress.org/ticket/49999) doesn’t have a link to
   the Make posts about the project. [@notlaura](https://profiles.wordpress.org/notlaura/)
   suggested adding a link to the [Introducing CSS Custom Properties](https://wp.me/p2AvED-mAu)
   Make post, as well as the current status of the project
 * [@colorful-tones](https://profiles.wordpress.org/colorful-tones/) initiated a
   discussion about the choice of hexadecimal colour definitions vs RGB(a) and/or
   HSL(a). This has been discussed on several previous occasions (e.g. [by me a year ago today!](https://wordpress.slack.com/archives/CQ7V4966Q/p1591307914306200))
   and circles back to [this comment from @joen](https://github.com/WordPress/wordpress-develop/pull/386#issuecomment-658895328):

> HSL works but it would force us to have 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. based on HSL colors, we
> want to have a more generic API where users just define a single variable.

### CSSCSS Cascading Style Sheets. Audit (󠀁[#49582](https://core.trac.wordpress.org/ticket/49582)󠁿)

 * [@danfarrow](https://profiles.wordpress.org/danfarrow/) reported having made 
   progress on the 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/) actions to autogenerate
   the report. There are now two actions, one to [merge updates to `trunk` into the `report` branch](https://github.com/WordPress/css-audit/actions/workflows/merge-trunk-to-report.yml)(
   which appears to be working), and the [Build Report action](https://github.com/WordPress/css-audit/actions/workflows/build-report.yml)
   which now generates the report once a day from the `report` branchbranch A directory
   in Subversion. WordPress uses branches to store the latest development code for
   each major release (3.9, 4.0, etc.). Branches are then updated with code for 
   any minor releases of that branch. Sometimes, a major version of WordPress and
   its minor versions are collectively referred to as a "branch", such as "the 4.0
   branch".. TBC if it now works as expected…
 * [@colorful-tones](https://profiles.wordpress.org/colorful-tones/) offered to 
   add a link to the CSS Audit report into the [CSS Coding Standards docs](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/css/)[
   UPDATE] Now done, thanks [@colorful-tones](https://profiles.wordpress.org/colorful-tones/)!

### CSS deprecation path (󠀁[#53070](https://core.trac.wordpress.org/ticket/53070)󠁿)

 * The next step is a Make post from @tellthemachines, probably on hold until after
   the upcoming 5.8 release

## Open floor / CSS link share

 * [@colorful-tones](https://profiles.wordpress.org/colorful-tones/) shared a CSS-
   Tricks article [Are Custom Properties a “Menu of What Will Change”?](https://css-tricks.com/are-custom-properties-a-menu-of-what-will-change/)
   which resonates with the goal of creating a scalable CSS API for CoreCore Core
   is the set of software required to run WordPress. The Core Development Team builds
   WordPress. custom properties
 * [@colorful-tones](https://profiles.wordpress.org/colorful-tones/) expressed a
   strong desire to see Sass removed from core blocks and suggested a future discussion.
   [@notlaura](https://profiles.wordpress.org/notlaura/) agreed that it could go
   on the agenda for a future meeting and suggested a Make post outlining the proposal.
   Example Make post proposals include [Proposal: a new color palette for WordPress](https://make.wordpress.org/design/2019/11/26/proposal-a-new-color-palette-for-wordpress/)&
   [Proposal: Test Badges for the FSE Outreach Program](https://make.wordpress.org/test/2021/05/21/proposal-test-badges-for-the-fse-outreach-program/)

Thanks everyone!

[#core-css](https://make.wordpress.org/core/tag/core-css/), [#summary](https://make.wordpress.org/core/tag/summary/)

 [  ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/)
9:01 pm _on_ June 3, 2021     
Tags: [make.wordpress.org/project ( 18 )](https://make.wordpress.org/core/tag/make-wordpress-org-project/),
[p2-xpost ( 212 )](https://make.wordpress.org/core/tag/p2-xpost/)   

# 󠀁[X-post: Welcome to make.wordpress.org/project](https://make.wordpress.org/core/2021/06/03/xpost-welcome-to-make-wordpress-org-project/)󠁿

X-comment from [+make.wordpress.org/project](https://make.wordpress.org/project/):
Comment on [Welcome to make.wordpress.org/project](https://make.wordpress.org/project/2021/06/03/welcome-to-make-wordpress-org-project/#comment-2)

 [  ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/)
7:34 pm _on_ June 3, 2021     
Tags: [agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/),
[core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/)   

# 󠀁[CSS Chat Agenda: June 3, 2021](https://make.wordpress.org/core/2021/06/03/css-chat-agenda-june-3-2021/)󠁿

_Note: 1 hour before the meeting this week, [@sabernhardt](https://profiles.wordpress.org/sabernhardt/)
will lead a CSSCSS Cascading Style Sheets. 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. scrub looking at 
5.8 tickets_.

This is the agenda for the upcoming CSS meeting scheduled for [Thursday, June 3, at 5:00 PM EDT](https://www.timeanddate.com/worldclock/fixedtime.html?msg=WordPress+CSS+Core+Chat&iso=20210603T17&p1=418&ah=1).
This meeting will be held in the [#core-css](https://make.wordpress.org/core/tag/core-css/)
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/).

If there’s any topic you’d like to discuss, please leave a comment below!

 * Housekeeping
 * Project Updates
    - Color Scheming ([#49999](https://core.trac.wordpress.org/ticket/49999))
    - CoreCore Core is the set of software required to run WordPress. The Core Development
      Team builds WordPress. CSS deprecation path ([#53070](https://core.trac.wordpress.org/ticket/53070))
    - CSS Audit ([#49582](https://core.trac.wordpress.org/ticket/49582))
 * Open Floor + CSS Link Share

[#agenda](https://make.wordpress.org/core/tag/agenda/), [#core-css](https://make.wordpress.org/core/tag/core-css/)

[#agenda](https://make.wordpress.org/core/tag/agenda/), [#core-css](https://make.wordpress.org/core/tag/core-css/)

# Post navigation

[← Older posts](https://make.wordpress.org/core/2021/page/33/?output_format=md)

[Newer posts →](https://make.wordpress.org/core/2021/page/31/?output_format=md)