Title: 2021 – Page 37 – Make WordPress Core

---

#  Yearly Archives: 2021

 [  ](https://profiles.wordpress.org/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
8:15 pm _on_ May 11, 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 May 12, 2021](https://make.wordpress.org/core/2021/05/11/dev-chat-agenda-for-may-12-2021/)󠁿

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

## Blogblog (versus network, site) Post Highlights

 * [A Week in Core – May 10, 2021](https://make.wordpress.org/core/2021/05/10/a-week-in-core-may-10-2021/)
 * [What’s next in Gutenberg? (May 2021)](https://make.wordpress.org/core/2021/05/07/whats-next-in-gutenberg-may-2021/)
 * [CSS Custom Properties Project Update](https://make.wordpress.org/core/2021/05/10/css-custom-properties-project-update/)
 * [Hosting Team](https://make.wordpress.org/hosting/2021/05/06/hosting-team-meeting-summary-2021-05-05/)
   and [Media Component](https://make.wordpress.org/core/2021/05/06/media-meeting-recap-may-6/)
   meeting summaries
 * [Helping beta test mobile apps](https://make.wordpress.org/updates/2021/05/04/mobile-team-update-may-3rd/)
 * [CC Search joins WP.org as Openverse](https://wordpress.org/news/2021/05/welcome-to-openverse/)(
   plus [related WP Briefing episode](https://wordpress.org/news/2021/05/the-commons-of-images/))

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

 * [Bug Scrub schedule](https://make.wordpress.org/core/2021/05/05/bug-scrub-schedule-for-5-8/)
   and [preparing for test scrubs](https://make.wordpress.org/core/2021/05/06/test-scrub-for-wordpress-5-8/)
 * Marketing schedule (based on [earlier plans](https://make.wordpress.org/updates/2021/03/12/full-site-editing-pre-merge-overview/))
 * Feature Freeze in 13 days on Tuesday, May 25th
 * 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 in 27 
   days on Tuesday, June 8th
 * 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/37/?output_format=md#alpha-beta).
   1 in 48 days on Tuesday, June 29th
 * 5.8 release in 69 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/).

_Props [@desrosj](https://profiles.wordpress.org/desrosj/) for peer review._

[#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/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/)
10:43 am _on_ May 11, 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 May 11th, 2021](https://make.wordpress.org/core/2021/05/11/upgrade-install-component-meeting-agenda-for-may-11th-2021/)󠁿

Next meeting is scheduled on [Tuesday May 11, 2021 at 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210511T1700)
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)
 * 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/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
10:39 pm _on_ May 10, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
meta5044, [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)

# 󠀁[A Week in Core – May 10, 2021](https://make.wordpress.org/core/2021/05/10/a-week-in-core-may-10-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 3 and May
10, 2021.

 * 32 commits
 * 42 contributors
 * 44 tickets created
 * 4 tickets reopened
 * 34 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=05%2F10%2F2021&daysback=7&authors=&ticket=on&sfp_email=&sfph_mail=&update=Update).
The following is a summary of commits, organized by component and/or focus.

## Code changes

### Bundled Themes

 * Twenty Twenty-One: Fix “Opening PHPPHP The web scripting language in which WordPress
   is primarily architected. WordPress requires PHP 7.4 or higher 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.) must be on a line by itself” WPCSWordPress Community
   Support A public benefit corporation and a subsidiary of the WordPress Foundation,
   [established](https://wordpressfoundation.org/news/2016/introducing-wordpress-community-support-a-public-benefit-subsidiary/)
   in 2016. issue – [#52938](https://core.trac.wordpress.org/ticket/52938)

### Coding Standards

 * Use strict comparison in `wp-admin/includes/screen.php` – [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Fix a whitespace at end of line issue in `wp-admin/includes/class-wp-comments-
   list-table.php` – [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Use strict comparison in `wp-admin/includes/class-wp-posts-list-table.php` – 
   [#52627](https://core.trac.wordpress.org/ticket/52627)

### Comments

 * Remove fourth parameter on `remove_filter` call – [#53113](https://core.trac.wordpress.org/ticket/53113)

### Docs

 * Correct `@since` tags for new properties and functions related to infinite scrolling
   in Media Library – [#50105](https://core.trac.wordpress.org/ticket/50105), [#40330](https://core.trac.wordpress.org/ticket/40330),
   [#52628](https://core.trac.wordpress.org/ticket/52628)
 * Miscellaneous docblockdocblock (phpdoc, xref, inline docs) updates – [#52628](https://core.trac.wordpress.org/ticket/52628)
 * Use correct `@since` tag notation – [#16401](https://core.trac.wordpress.org/ticket/16401)
 * Correct the `aria-current` array key in the documentation for two 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.
   filters – [#43522](https://core.trac.wordpress.org/ticket/43522), [#52628](https://core.trac.wordpress.org/ticket/52628)
 * Correct documentation for `wp_get_webp_info()` return results – [#35725](https://core.trac.wordpress.org/ticket/35725)
 * Further synchronize documentation for some 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. 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. functions – 
   [#50531](https://core.trac.wordpress.org/ticket/50531)

### Editor

 * Update WordPress packages from 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/)
   10.5 – [#52991](https://core.trac.wordpress.org/ticket/52991)

### Formatting

 * Verify emails with `+` characters are valid – [#53130](https://core.trac.wordpress.org/ticket/53130)

### General

 * Use correct escaping function for form `action` attributes – [#53150](https://core.trac.wordpress.org/ticket/53150)
 * Use correct escaping function for the plugin icon URLURL A specific web address
   of a website or web page on the Internet, such as a website’s URL www.wordpress.
   org – [#53151](https://core.trac.wordpress.org/ticket/53151)

### Media

 * Remove infinite scroll from media library and modal – [#50105](https://core.trac.wordpress.org/ticket/50105),
   [#40330](https://core.trac.wordpress.org/ticket/40330)
 * Avoid an infinite 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)
   between `wp_getimagesize()` and `wp_get_image_mime()` – [#35725](https://core.trac.wordpress.org/ticket/35725)
 * Remove an extra variable and a redundant check in `WP_Image_Editor_Imagick::set_quality()`–
   [#35725](https://core.trac.wordpress.org/ticket/35725)
 * Remove `_wp_webp_is_lossy()` for now – [#35725](https://core.trac.wordpress.org/ticket/35725)
 * Correct an early return condition in `wp_get_webp_info()` – [#35725](https://core.trac.wordpress.org/ticket/35725)
 * Move retrieving WebP image size information into `wp_getimagesize()` – [#35725](https://core.trac.wordpress.org/ticket/35725)
 * Some documentation and test improvements for WebP support – [#35725](https://core.trac.wordpress.org/ticket/35725)
 * Images: enable WebP support – [#35725](https://core.trac.wordpress.org/ticket/35725)

### Networknetwork (versus site, blog) and Sites

 * Display site icons in the My Sites menu – [#46657](https://core.trac.wordpress.org/ticket/46657)

### Permalinks

 * Add labels for permalink configuration fields – [#53142](https://core.trac.wordpress.org/ticket/53142)

### Plugins

 * Escape the currently installed version number on Add Plugins screen – [#53020](https://core.trac.wordpress.org/ticket/53020)
 * Standardize the terminology used for actions, filters, and callback functions–
   [#50531](https://core.trac.wordpress.org/ticket/50531)
 * Enable 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. for the `wp_block` post
   type – [#53072](https://core.trac.wordpress.org/ticket/53072)
 * Improve the appearance of Site Health Status dashboard widget – [#52966](https://core.trac.wordpress.org/ticket/52966)
 * Include more ImageMagick/Imagick information in the Media Handling section – 
   [#53022](https://core.trac.wordpress.org/ticket/53022)
 * Introduce the `delete_theme` and `deleted_theme` action 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. – [#16401](https://core.trac.wordpress.org/ticket/16401)
 * Remove the “Featured” tab on Add Themes screen – [#49487](https://core.trac.wordpress.org/ticket/49487),
   [#meta5044](https://meta.trac.wordpress.org/ticket/5044)

## Props

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

[@desrosj](https://profiles.wordpress.org/desrosj/) (5), [@audrasjb](https://profiles.wordpress.org/audrasjb/)(
5), [@Clorith](https://profiles.wordpress.org/clorith/) (3), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/)(
3), [@joemcgill](https://profiles.wordpress.org/joemcgill/) (2), [@afercia](https://profiles.wordpress.org/afercia/)(
2), [@chintan1896](https://profiles.wordpress.org/chintan1896/) (2), [@ayeshrajans](https://profiles.wordpress.org/ayeshrajans/)(
2), [@johnjamesjacoby](https://profiles.wordpress.org/johnjamesjacoby/) (2), [@matveb](https://profiles.wordpress.org/matveb/)(
1), @markoheijne (1), [@poena](https://profiles.wordpress.org/poena/) (1), [@kjellr](https://profiles.wordpress.org/kjellr/)(
1), [@celloexpressions](https://profiles.wordpress.org/celloexpressions/) (1), [@marylauc](https://profiles.wordpress.org/marylauc/)(
1), [@blobfolio](https://profiles.wordpress.org/blobfolio/) (1), [@atjn](https://profiles.wordpress.org/atjn/)(
1), [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) (1), [@mikeschroder](https://profiles.wordpress.org/mikeschroder/)(
1), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) (1), [@flixos90](https://profiles.wordpress.org/flixos90/)(
1), [@johnbillion](https://profiles.wordpress.org/johnbillion/) (1), [@diddledan](https://profiles.wordpress.org/diddledan/)(
1), [@youknowriad](https://profiles.wordpress.org/youknowriad/) (1), [@alexstine](https://profiles.wordpress.org/alexstine/)(
1), [@francina](https://profiles.wordpress.org/francina/) (1), [@rmccue](https://profiles.wordpress.org/rmccue/)(
1), [@mblach](https://profiles.wordpress.org/mblach/) (1), [@hedgefield](https://profiles.wordpress.org/hedgefield/)(
1), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) (1), [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/)(
1), [@joedolson](https://profiles.wordpress.org/joedolson/) (1), [@ocean90](https://profiles.wordpress.org/ocean90/)(
1), [@chetan200891](https://profiles.wordpress.org/chetan200891/) (1), [@scottconnerly](https://profiles.wordpress.org/scottconnerly/)(
1), [@ptahdunbar](https://profiles.wordpress.org/ptahdunbar/) (1), [@pbiron](https://profiles.wordpress.org/pbiron/)(
1), [@vetyst](https://profiles.wordpress.org/vetyst/) (1), [@m0ze](https://profiles.wordpress.org/m0ze/)(
1), [@bmcculley](https://profiles.wordpress.org/bmcculley/) (1), [@jnylen0](https://profiles.wordpress.org/jnylen0/)(
1), and [@jrf](https://profiles.wordpress.org/jrf/) (1).

**Congrats and welcome to our 6 new contributors of the week!** [@marylauc](https://profiles.wordpress.org/marylauc/),
[@atjn](https://profiles.wordpress.org/atjn/), [@mblach](https://profiles.wordpress.org/mblach/),
[@vetyst](https://profiles.wordpress.org/vetyst/), [@m0ze](https://profiles.wordpress.org/m0ze/),
[@bmcculley](https://profiles.wordpress.org/bmcculley/) ♥️

**Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)(
18), [@desrosj](https://profiles.wordpress.org/desrosj/) (8), [@joedolson](https://profiles.wordpress.org/joedolson/)(
2), [@johnbillion](https://profiles.wordpress.org/johnbillion/) (1), [@gziolo](https://profiles.wordpress.org/gziolo/)(
1), [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/) (1), and [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/)(
1).

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

 [  ](https://profiles.wordpress.org/itsjusteileen/) [Eileen Violini](https://profiles.wordpress.org/itsjusteileen/)
8:56 pm _on_ May 10, 2021      

# 󠀁[Core Editor Agenda 12 May, 2020](https://make.wordpress.org/core/2021/05/10/core-editor-agenda-12-may-2020/)󠁿

Facilitator: @itsjusteileen

This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, May 1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Chat&iso=20210512T14&p1=1440&ah=1)
[2](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Chat&iso=20210512T14&p1=1440&ah=1)
[, 2021, 02:00PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Chat&iso=20210512T14&p1=1440&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.5.4](https://github.com/WordPress/gutenberg/releases)
 * [Gutenberg 10.6](https://github.com/WordPress/gutenberg/releases/tag/v10.6.0-rc.1)
   due out on 12 May
 * [WordPress 5.8](https://make.wordpress.org/core/5-8/)
 * [What’s New in Gutenberg](https://make.wordpress.org/core/2021/04/30/whats-new-in-gutenberg-10-5-28-april/)
 * [What’s Next in Gutenberg](https://make.wordpress.org/core/2021/05/07/whats-next-in-gutenberg-may-2021/)
 * [Full Site Editing Upcoming Schedule](https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/)
 * 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
 * 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.

 [  ](https://profiles.wordpress.org/ryelle/) [Kelly Choyce-Dwan](https://profiles.wordpress.org/ryelle/)
3:44 pm _on_ May 10, 2021     
Tags: color-schemes, [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/)

# 󠀁[CSS Custom Properties Project Update](https://make.wordpress.org/core/2021/05/10/css-custom-properties-project-update/)󠁿

Based on the discussions in this [previous post](https://make.wordpress.org/core/2021/01/29/introducing-css-custom-properties/),
a few of us over in [#core-css](https://make.wordpress.org/core/tag/core-css/) have
made some demos and explored the technical details around using custom properties
with coreCore Core is the set of software required to run WordPress. The Core Development
Team builds WordPress. as part of the larger goal to implement dark mode in WP-Adminadmin(
and super admin), and allow for more sophisticated handling of color schemes (see
[#49999](https://core.trac.wordpress.org/ticket/49999)). The following post will
summarize those thoughts and lay out a possible roadmap.

Given [the IE11 phase-out plan](https://make.wordpress.org/core/2021/04/22/ie-11-support-phase-out-plan/),
fallbacks for custom properties are not needed. If for some reason that changes,
there are PostCSS tools for automating fallbacks.

Naming the custom properties – some demos to explore different naming schemes were
shared in the core-CSSCSS Cascading Style Sheets. meetings ([demo 1,](https://codepen.io/laras126/pen/wvgJgaQ)
[demo 2,](https://codepen.io/ryelle/project/full/AooEky) and [demo 3](https://ggm4x.csb.app/)).
The aim is to create a consistent and understandable “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.” for interacting
with colors (custom properties won’t be used for typography or layout). One formula
for creating names was decided on, `--[prefix]--[location]--[property]--[state]`.
Those tokens will be refined further in future Core CSS meetings. The next meeting
is [Thursday 21:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260820T2100).

## How it (could) work

 * [⌊The default admin color scheme design, white and light grey backgrounds with
   dark grey text, and a blue button.⌉⌊The default admin color scheme design, white
   and light grey backgrounds with dark grey text, and a blue button.⌉[
 * [⌊A light high contrast scheme design, with darker buttons, borders, and text
   against a white background.⌉⌊A light high contrast scheme design, with darker
   buttons, borders, and text against a white background.⌉[
 * [⌊A dark mode design, with dark grey background, white and light grey text, and
   bright blue buttons.⌉⌊A dark mode design, with dark grey background, white and
   light grey text, and bright blue buttons.⌉[
 * [⌊A dark high contrast design, with dark grey backgrounds, white text, and a 
   bright green button and link.⌉⌊A dark high contrast design, with dark grey backgrounds,
   white text, and a bright green button and link.⌉[

In this example, there are 4 screenshots of possible color schemes – default, light
high contrast, dark, and dark high contrast. Custom properties would be used to 
set the background colors, text colors, link, and button colors so that each theme
can set just what is needed. For example, the button’s CSS would look like this:

    ```wp-block-code
    .button {
        background: var(--wp-admin--button--background);
        color: var(--wp-admin--button--color);
    }
    ```

Then each theme would set those variables, inheriting from the default.

    ```wp-block-code
    body {
        --wp-admin--button--background: #2371b1;
        --wp-admin--button--color: #fff;
    }

    body.is-theme-dark {
        /* No change, the same button is used. */
    }

    body.is-theme-light-high-contrast {
        /* Inherits the text color, but darkens the button. */
        --wp-admin--button--background: #0b4b78;
    }

    body.is-theme-dark-high-contrast {
        /* Overrides both background and text. */
        --wp-admin--button--background: #68de7c;
        --wp-admin--button--color: #1d2327;
    }
    ```

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. authors will also be able to use
these colors in their CSS without creating separate rules for each color scheme.

    ```wp-block-code
    .my-fancy-button {
        background: var(--wp-admin--button--background);
        color: var(--wp-admin--button--color);
    }
    ```

Specific technical details – like how the schemes are registered & loaded, how to
work with the existing properties 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/),
whether there should be a “default dark” for schemes to inherit from, etc – are 
still in progress. If this sounds interesting to you, please join the conversation
in [#core-css](https://make.wordpress.org/core/tag/core-css/)!

This project will likely also tie into the CSS deprecation discussion in [#53070](https://core.trac.wordpress.org/ticket/53070).

## Next Steps

This is just a rough outline, and will depend on support and involvement across 
different teams.

**Phase 1** (eta: early 5.9)

 * Start creating custom properties with an `--experimental` prefix. This will allow
   for use in trunktrunk A directory in Subversion containing the latest development
   code in preparation for the next major release cycle. If you are running "trunk",
   then you are on the latest revision. without committing to forever supporting
   them.
 * This will need more input from designers and UIUI User interface folks to help
   identify colors and make sure the naming schemes are coherent in the design system
   of WordPress.
 * Once some color custom properties have been created, use these for the current
   core color schemes. Maybe make improvements to the color schemes.

**Phase 2** (eta: 6.0)

 * Remove the experimental prefix from the custom properties.
 * Create new color schemes for a dark mode, high contrast dark mode, and high contrast
   light mode.

+make.wordpress.org/design/

_Thanks to [@melchoyce](https://profiles.wordpress.org/melchoyce/) for quickly mocking
up some possible color schemes, and thanks to [@danfarrow](https://profiles.wordpress.org/danfarrow/),
[@notlaura](https://profiles.wordpress.org/notlaura/), & [@joyously](https://profiles.wordpress.org/joyously/)
for reviewing this post_.

[#color-schemes](https://make.wordpress.org/core/tag/color-schemes/)

 [  ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/)
8:28 pm _on_ May 7, 2021     
Tags: [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/),
[gutenberg ( 547 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-next ( 23 )](https://make.wordpress.org/core/tag/gutenberg-next/)

# 󠀁[What’s next in Gutenberg? (May 2021)](https://make.wordpress.org/core/2021/05/07/whats-next-in-gutenberg-may-2021/)󠁿

This monthly 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 May. Please join us in our efforts and let us know
in the comments if anything is blocking you from doing so.

The priorities for the month heavily focus on the [WordPress 5.8 Must Haves](https://github.com/WordPress/gutenberg/projects/55),
including [auditing Experimental APIs](https://github.com/WordPress/gutenberg/issues/31416)
and [merging Gutenberg into WordPress trunk](https://github.com/WordPress/gutenberg/issues/31322).

**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. 

## Widgets Editor

Work 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.-
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 is a continued focus for the month ahead. 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:

 * Audit and ensure [backward compatibility](https://github.com/WordPress/gutenberg/issues/28673).
 * Customizer block editor:
    - Enhance [legacy widgets fitting properly](https://github.com/WordPress/gutenberg/issues/31194).
    - Implement [a mobile responsive block toolbar](https://github.com/WordPress/gutenberg/pull/31589).
    - Implement [undo/redo](https://github.com/WordPress/gutenberg/issues/30400).
 * Add a [plugin to disable the block-based Widgets editor](https://github.com/WordPress/gutenberg/issues/31331).

**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 Widget 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 to
allow for more adoption and offer a more modern experience. Because the Navigation
Editor needs to work nicely with the Navigation Block (and vice versa), much of 
the current effort from contributors focus on the Navigation Block. With this in
mind, current efforts include:

 * Continue defining Navigation Editor architecture.
    - Discuss over [supporting future block types](https://github.com/WordPress/gutenberg/issues/30006)
      in the navigation editor.
    - Provide a better way to [disable/enable Navigation Block features](https://github.com/WordPress/gutenberg/issues/30007)
      for the Navigation Editor.
 * Reconsider [the placeholder state](https://github.com/WordPress/gutenberg/issues/23953)
   to make it easier to create a new menu.
 * Improve [handling unsaved changes](https://github.com/WordPress/gutenberg/issues/30322).
 * Add [a preview mode](https://github.com/WordPress/gutenberg/issues/31074) to 
   show how the menu would look once it’s published.
 * Add [visual cues](https://github.com/WordPress/gutenberg/issues/30659) for the
   menu and page list items and [always show the appender.](https://github.com/WordPress/gutenberg/issues/31276)

**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

As with the prior months, 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/).
Work this month will include the following focus areas:

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

 * Ongoing work on [phase 3 of the infrastructure](https://github.com/WordPress/gutenberg/issues/27814).
 * Explore how to expose [the new FSE editors to users](https://github.com/WordPress/gutenberg/issues/29630).
 * Try a [click-through-to-edit-children UX](https://github.com/WordPress/gutenberg/issues/29337)
   for reusable blocks and template parts.
 * Site/Template editor [welcome guide](https://github.com/WordPress/gutenberg/pull/31330).
 * Move post/page title [to the top bar](https://github.com/WordPress/gutenberg/issues/27093).
 * Make it possible to [delete new custom block templates](https://github.com/WordPress/gutenberg/issues/31076)
   and revert customized block templates in the template editor.
 * Improve the [persistent list view](https://github.com/WordPress/gutenberg/issues/29736),
   including [enabling it in the post editor](https://github.com/WordPress/gutenberg/issues/29470).

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

 * Iterate on the[ block supports mechanism](https://github.com/WordPress/gutenberg/issues/28913),
   including:
    - Add [margin block support](https://github.com/WordPress/gutenberg/pull/30608)
      with configurable sides.
    - Add [letter-spacing](https://github.com/WordPress/gutenberg/pull/31118).
    - Migrate more blocks to the 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. system: border for [Cover](https://github.com/WordPress/gutenberg/pull/31370)
      and [Image](https://github.com/WordPress/gutenberg/pull/31366) blocks, [the margin for Separator block](https://github.com/WordPress/gutenberg/pull/30609),
      and [border & color for Pullquote block](https://github.com/WordPress/gutenberg/pull/30951).
 * Add [CSS vars for root level settings](https://github.com/WordPress/gutenberg/pull/29714).

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

 * With most [theme blocks](https://github.com/WordPress/gutenberg/issues/28744)
   moved out of experimental, it’s time to polish the Site Logo block’s design and
   [bring feature parity with the Image ](https://github.com/WordPress/gutenberg/issues/30406)
   [B](https://github.com/WordPress/gutenberg/issues/30406)[lock](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.

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

 * A [collection of improvements](https://github.com/WordPress/gutenberg/issues/30910)
   to the block.
 * Revisit the bundled [Query Block Patterns](https://github.com/WordPress/gutenberg/issues/30508).
 * Create [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)

 * Make the navigation [mobile-responsive](https://github.com/WordPress/gutenberg/issues/22824)
   is an ongoing effort, collapsing it to a hamburger icon when on smaller viewports.
 * Option to render the block [using a classic navigation data source](https://github.com/WordPress/gutenberg/pull/30852).
 * Add a [home link block](https://github.com/WordPress/gutenberg/issues/20542).
 * Support [non-li inner blocks](https://github.com/WordPress/gutenberg/issues/29036).
 * Mark [invalid menu items](https://github.com/WordPress/gutenberg/issues/23573)
   and [links to draft pages](https://github.com/WordPress/gutenberg/issues/29417#issuecomment-790816305)
   for better editing UXUX User experience.

**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

**FSE Roadmap**

 * The [Full Site Editing Go/No Go demo took place a few weeks ago](https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/),
   and its summary, recording, and transcript published.
 * As a follow-up of the demo, [next steps towards 5.8](https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/)
   were determined.

**FSE Outreach Program**

 * The [schedule for the upcoming FSE calls for testing](https://make.wordpress.org/test/2021/04/22/upcoming-fse-outreach-program-schedule/)
   was announced.
 * The [summary of the 4th round](https://make.wordpress.org/test/2021/05/06/fse-program-query-quest-summary/)
   of the FSE Outreach Program is available as well. 
 * A [new round of general questions around Full Site Editing](https://make.wordpress.org/test/2021/04/28/fse-program-bring-your-questions-round-two/)
   can be submitted until May 12th.
 * Expect a call for testing this month on the Widgets Editor.

**Theme Developers**

 * The `theme.json` configuration file is becoming stable in the imminent Gutenberg
   10.6:
    - The [file structure change](https://github.com/WordPress/gutenberg/pull/30541)
      has been finished.
    - The file [has been renamed](https://github.com/WordPress/gutenberg/pull/29981)
      from `experimental-theme.json` to `theme.json`.

**Design**

 * To complement the [forthcoming Pattern Directory](https://make.wordpress.org/meta/2021/04/28/block-pattern-directory-update/)
   and similarly to [Query Block patterns](https://github.com/WordPress/gutenberg/issues/30508)
   being revisited, [Template Part patterns are being explored](https://github.com/WordPress/gutenberg/issues/31231).
 * A number of design explorations regarding [improvements to reusable blocks](https://github.com/WordPress/gutenberg/issues/27890)
   are in the works, including:
    - [Add more functionality to reusable block settings](https://github.com/WordPress/gutenberg/issues/30357).
    - [Add a menu in the isolated editing view top toolbar](https://github.com/WordPress/gutenberg/issues/30622)
      for navigating to usage locations.
    - [Show the Save button in the Reusable Block toolbar](https://github.com/WordPress/gutenberg/issues/29871)
      if there are changes.

**Other**

 * The [IE 11 Support Phase Out Plan](https://make.wordpress.org/core/2021/04/22/ie-11-support-phase-out-plan/)
   has been published and IE 11 support will be [removed from Gutenberg](https://github.com/WordPress/gutenberg/pull/31110)
   in 10.6.

## 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/), [needs 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 ](https://make.wordpress.org/chat/)[S](https://make.wordpress.org/chat/)
[lack account](https://make.wordpress.org/chat/) to participate:

 * CoreCore Core is the set of software required to run WordPress. The Core Development
   Team builds WordPress. 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 [@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/jeffpaul/) [Jeffrey Paul](https://profiles.wordpress.org/jeffpaul/)
10:13 pm _on_ May 6, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[accessibility ( 59 )](https://make.wordpress.org/core/tag/accessibility/), [dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/),
[docs ( 11 )](https://make.wordpress.org/core/tag/docs/), [FSE ( 5 )](https://make.wordpress.org/core/tag/fse/),
[full-site editing ( 15 )](https://make.wordpress.org/core/tag/full-site-editing/),
[github ( 9 )](https://make.wordpress.org/core/tag/github/), [LearnWP ( 2 )](https://make.wordpress.org/core/tag/learnwp/),
[summary ( 975 )](https://make.wordpress.org/core/tag/summary/), training, [updater ( 21 )](https://make.wordpress.org/core/tag/updater/)

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

[Agenda](https://make.wordpress.org/core/2021/05/04/dev-chat-agenda-for-may-5-2021/)
for the two meetings. Thanks to [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/)
and [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) for leading the 05:00 
and 20:00 UTC devchats respectively.

[Link to 05:00 UTC devchat meeting archive in Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1620190947133200)//
[Link to 20:00 UTC devchat meeting archive in Slack](https://wordpress.slack.com/archives/C02RQBWTW/p1620244839167800)

## **Announcements and news**

 * [@audrasjb](https://profiles.wordpress.org/audrasjb/) shares the [weekly recap of code changes and contributors in core](https://make.wordpress.org/core/2021/05/03/a-week-in-core-may-3-2021/)
 * [@desrosj](https://profiles.wordpress.org/desrosj/) reminds us to check that 
   your [GitHub account is linked to your WordPress.org profile](https://make.wordpress.org/core/2021/05/03/expired-github-and-wordpress-org-profile-connections/)(
   both to show that off on your WP.org profile, but more importantly to ensure 
   any contributions 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/) magically turn
   into correct props to your 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/)
   profile)
 * [@audrasjb](https://profiles.wordpress.org/audrasjb/) highlights specific [responsibilities, roles, and workflow for the Documentation focus](https://make.wordpress.org/core/2021/05/03/docs-focus-role-workflow-during-wordpress-release-cycle/)
   as part of the 5.8 release cycle (lead by [@milana_cap](https://profiles.wordpress.org/milana_cap/))
 * [@francina](https://profiles.wordpress.org/francina/) provides an [update on the Upgrade/Install component](https://make.wordpress.org/core/2021/05/03/feature-project-updates-on-updating-the-updaters/)
   goal to improve the updaters, some context on why, four expected outcomes, ways
   to contribute to the effort, details on their weekly meeting schedule, and [latest meeting notes](https://make.wordpress.org/core/2021/05/05/upgrade-install-component-meeting-agenda-for-may-4th-2021-2/)
 * [@lukecarbis](https://profiles.wordpress.org/lukecarbis/) published the [bug scrub schedule for 5.8](https://make.wordpress.org/core/2021/05/05/bug-scrub-schedule-for-5-8/),**
   so please add these to your calendar if you’re interested in helping scrub, also
   reach out to him if you’re interested in running a scrub as well**
 * [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) reminded that details on
   the Full Site Editing (“FSE”) tasks for 5.8 are described by [@priethor](https://profiles.wordpress.org/priethor/)
   in the [“go/no go: next steps” post](https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/)

## **These posts need your feedback:**

 * [@ryokuhi](https://profiles.wordpress.org/ryokuhi/) published a [proposal on Make/Accessibility about a new Trac workflow keyword](https://make.wordpress.org/accessibility/2021/04/29/proposal-new-workflow-keyword-to-exclude-tickets-until-review-is-needed/)
   that the 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) team would like to consider.  **If you feel particularly
   opinionated or passionate about this, please comment on the post.**
 * [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) and [@desrosj](https://profiles.wordpress.org/desrosj/)
   published a [request to Component Maintainers, Feature plugin authors, and the Gutenberg team](https://make.wordpress.org/core/2021/05/05/wordpress-5-8-whats-on-your-to-do-list/)
   to share plans / help needed for 5.8 (primary focus will be FSE).  **Please comment
   on the post to help ensure we’re tracking the right work for the release.**
    - [@youknowriad](https://profiles.wordpress.org/youknowriad/) noted that [required Gutenberg changes in Core](https://github.com/WordPress/gutenberg/issues/31322)
      are made as filters/extensions points and brought to coreCore Core is the 
      set of software required to run WordPress. The Core Development Team builds
      WordPress. as part of 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/)
      merge that happens regularly
    - [@mkaz](https://profiles.wordpress.org/mkaz/) shared the [WordPress 5.8 Must Haves project board on GitHub](https://github.com/WordPress/gutenberg/projects/55)
      as outline of Gutenberg work for 5.8

## 5.8 Review

 * [Schedule confirmed](https://make.wordpress.org/core/5-8/) including 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 schedule
 * [@youknowriad](https://profiles.wordpress.org/youknowriad/) shared that `trunk`
   is already on Gutenberg 10.4, [@gziolo](https://profiles.wordpress.org/gziolo/)
   is working on updating it to 10.5 and the big changes (Global styles infrastructure
   in `themes.json` and FSE blocks) are coming in 10.6
 * **Feature freeze on Tuesday May 25th (19 days from now) defined as “_During the
   following two weeks, there will be no commits for new enhancements or feature
   requests. Core contributorsCore Contributors Core contributors are those who 
   have worked on a release of WordPress, by creating the functions or finding and
   patching bugs. These contributions are done through Trac. [https://core.trac.wordpress.org](https://core.trac.wordpress.org)
   will focus on defect work (aka outstanding bugs)_“**
 * 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 on Tuesday
   June 8 (33 days)
 * 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/37/?output_format=md#alpha-beta).
   1 on Tuesday June 29 (54 days)
 * Release on Tuesday July 20 (75 days)
 * [Current list of tickets that are on the 5.8 milestone](https://core.trac.wordpress.org/tickets/major/workflow),
   [list of `good-first-bugs` tickets](https://core.trac.wordpress.org/query?status=accepted&status=assigned&status=new&status=reopened&status=reviewing&keywords=~good-first-bug&milestone=5.8&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority)

## **Component maintainers and committers update**

 * [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) shared `Plugins`
   update that Parameter names in 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. 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. functions now
   use consistent terminology when referring to actions, filters, and callback functions
   via [#50531](https://core.trac.wordpress.org/ticket/50531)
 * [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) shared `Themes`
   update that [#49487](https://core.trac.wordpress.org/ticket/49487) removes the“
   Featured” tab on Add Themes screen to match an earlier change in the Theme Directory
 * [@webcommsat](https://profiles.wordpress.org/webcommsat/) shared `About/Help`
   update that ticketticket Created for both bug reports and feature development
   on the bug tracker. triagetriage The act of evaluating and sorting bug reports,
   in order to decide priority, severity, and other factors. continues with [@marybaum](https://profiles.wordpress.org/marybaum/)
 * [@audrasjb](https://profiles.wordpress.org/audrasjb/) shared `Menus` update that
   [#21603](https://core.trac.wordpress.org/ticket/21603) is being reviewed
 * [@audrasjb](https://profiles.wordpress.org/audrasjb/) shared `Upgrade/Install`
   update that the [last meeting recap](https://make.wordpress.org/core/2021/05/05/upgrade-install-component-meeting-agenda-for-may-4th-2021-2/)
   includes a project for the next few releases

## **Open Floor**

 * [@chaion07](https://profiles.wordpress.org/chaion07/) shared [High-Level Roadmap to Learning WordPress Development](https://make.wordpress.org/training/2021/05/03/high-level-roadmap-to-learning-wordpress-development/)
   from [@courane01](https://profiles.wordpress.org/courane01/) and the [#training](https://make.wordpress.org/core/tag/training/)
   team
 * [@francina](https://profiles.wordpress.org/francina/) [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)
   discussed branching at Feature Freeze and agreed to get through that period and
   revisit the decision then. [@helen](https://profiles.wordpress.org/helen/) noted
   that the deciding factor will likely be “how much people think they’ll actually
   be mixing in work destined for post-5.8”
 * [@webcommsat](https://profiles.wordpress.org/webcommsat/) asked for input from
   Core team on workshop ideas and on-demand materials for contributors as part 
   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/).
   Europe’s contributing team; please share your ideas and resources with [@webcommsat](https://profiles.wordpress.org/webcommsat/)
   or [@marks99](https://profiles.wordpress.org/marks99/).
 * [@francina](https://profiles.wordpress.org/francina/) highlighted the [Yoast Diversity Fund](https://yoast.com/diversity-fund/).
   If you’re interested, contact [@francina](https://profiles.wordpress.org/francina/)
   or [@tacoverdo](https://profiles.wordpress.org/tacoverdo/)

_**Props to **_[@audrasjb](https://profiles.wordpress.org/audrasjb/), [@webcommsat](https://profiles.wordpress.org/webcommsat/)
and [@marybaum](https://profiles.wordpress.org/marybaum/)_** for reviewing this 
post.**_

[#5-8](https://make.wordpress.org/core/tag/5-8/), [#accessibility](https://make.wordpress.org/core/tag/accessibility/),
[#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#docs](https://make.wordpress.org/core/tag/docs/),
[#fse](https://make.wordpress.org/core/tag/fse/), [#full-site-editing](https://make.wordpress.org/core/tag/full-site-editing/),
[#github](https://make.wordpress.org/core/tag/github/), [#learnwp](https://make.wordpress.org/core/tag/learnwp/),
[#summary](https://make.wordpress.org/core/tag/summary/), [#updater](https://make.wordpress.org/core/tag/updater/)

 [  ](https://profiles.wordpress.org/hongnizzle/) [Hong Nga Nguyen](https://profiles.wordpress.org/hongnizzle/)
7:30 pm _on_ May 6, 2021     
Tags: [core ( 745 )](https://make.wordpress.org/core/tag/core/),
[core-media ( 116 )](https://make.wordpress.org/core/tag/core-media/), [media ( 93 )](https://make.wordpress.org/core/tag/media/),
[summary ( 975 )](https://make.wordpress.org/core/tag/summary/)   

# 󠀁[Media Meeting Recap – May 6, 2021](https://make.wordpress.org/core/2021/05/06/media-meeting-recap-may-6/)󠁿

The following is a summary of the weekly Media component meeting that occurred on
Thursday, May 6, 2021 at 14:00 UTC. Weekly media meetings are held every Thursday
at 14:00 UTC. A full transcript can be found [here](https://wordpress.slack.com/archives/C02SX62S6/p1620309628063400)
in the [#core-media](https://make.wordpress.org/core/tag/core-media/) room in the
[ Make WordPress Slack](https://make.wordpress.org/chat/).

Attendees: [@antpb](https://profiles.wordpress.org/antpb/), [@mista-flo](https://profiles.wordpress.org/mista-flo/),
[@chaion07](https://profiles.wordpress.org/chaion07/), [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/),
[@paaljoachim](https://profiles.wordpress.org/paaljoachim/), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/),
[@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/), [@desrosj](https://profiles.wordpress.org/desrosj/)

## Media 5.8 tickets

This meeting’s discussion focused around WebP and 5.8 Media features.

[[[#35725:](https://core.trac.wordpress.org/ticket/35725) _Add WebP support_ – WebP
support has been merged! Please test on all configurations possible to ensure there
are no edge case issues. Big props to [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/) and all
who helped make this happen! Adam mentioned that a post is in progress that will
provide an overview to the new WebP supports.

[#52876](https://core.trac.wordpress.org/ticket/52867) _Add capabilitycapability
A **capability** is permission to perform one or more types of task. Checking if
a user has a capability is performed by the `current\_user\_can` function. Each 
user of a WordPress site might have some permissions but not others, depending on
their role. For example, users who have the Author role usually have permission 
to edit their own posts (the “edit\_posts” capability), but not permission to edit
other users’ posts (the “edit\_others\_posts” capability). to set default format
for image sub-sizes. _– This ticketticket Created for both bug reports and feature
development on the bug tracker. is in progress and adds a new 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. where people can set a default image type such as WebP. [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/)
has asked for some testing assistance to ensure everything works as intended. Testing
instructions can be found [here](https://core.trac.wordpress.org/ticket/52867#comment:26).

[#50105](https://core.trac.wordpress.org/ticket/50105): _Remove infinite scrolling
behavior from the Media grid – _It was agreed during the meeting that for the button
that moves focus to the first newly loaded media item_, “Jump to first loaded item”
_is a great way to make this not focus on images or any other specific media type
and still be clear. [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/)
mentioned in the meeting on the pending count issue, “I think it would be a better
experience for users if we could solve it before 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.. That said, it would be good to get the patchpatch A special
text file that describes changes to code, by identifying the files and lines which
are added, removed, and altered. It may also be referred to as a **diff**. A patch
can be _applied_ to a codebase for testing. committed and then work on that specific
issue as a follow-up.” It was agreed by multiple participants in the meeting that
landing this sooner and iterating is ideal.

[#37255](https://core.trac.wordpress.org/ticket/37255): _Update attachment functions
to accept a post object in addition to ID_ – [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/)
mentioned keeping this ticket focused on resolving the issues that were identified
and moving any broader scope to a separate issue to avoid this being punted to a
future release again.

_Props [@antpb](https://profiles.wordpress.org/antpb/) for proofreading and final
review_.

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

 [  ](https://profiles.wordpress.org/boniu91/) [Piotrek Boniu](https://profiles.wordpress.org/boniu91/)
6:54 pm _on_ May 6, 2021     
Tags: [core-test ( 12 )](https://make.wordpress.org/core/tag/core-test/),
[testing ( 25 )](https://make.wordpress.org/core/tag/testing/)   

# 󠀁[Test scrub for WordPress 5.8](https://make.wordpress.org/core/2021/05/06/test-scrub-for-wordpress-5-8/)󠁿

As a part of the 5.8 release, we’ll be hosting test scrub for WordPress 5.8 on [2021-05-07 13:15](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210507T1315)
in the [core-test](https://app.slack.com/client/T024MFP4J/C02RQBWTW) channel. 
We’ll
do manual testing of the below tickets: https://core.trac.wordpress.org/ticket/43697https://
core.trac.wordpress.org/ticket/50866 We’ll appreciate your participation and feedback!**
What you need**

 * [WordPress Develop environment](https://meta.trac.wordpress.org/ticket/5581#comment:3),
   PHP8 will be an advantage

## How to apply a patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a **diff**. A patch can be _applied_ to a codebase for testing.

TracTrac An open source project by Edgewall Software that serves as a bug tracker
and project management tool for WordPress. ticketticket Created for both bug reports
and feature development on the bug tracker., for example `35449`

    ```wp-block-preformatted
    npm run grunt patch:35449
    ```

How to fetch and then checkout a PR, for example, PR 828

    ```wp-block-preformatted
    git fetch upstream pull/828/head:pr-828git checkout pr-828
    ```

or for PR:

    ```wp-block-preformatted
    npm run grunt patch:https://github.com/WordPress/wordpress-develop/pull/828
    ```

Check the handbook for more ways to [test patches](https://make.wordpress.org/core/handbook/testing/patch/).

Looking forward to seeing you!

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

 [  ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/)
3:44 pm _on_ May 6, 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: May 6, 2021](https://make.wordpress.org/core/2021/05/06/css-chat-agenda-may-6-2021/)󠁿

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled
for [Thursday, May 6, at 5:00 PM EDT](https://www.timeanddate.com/worldclock/fixedtime.html?msg=WordPress+CSS+Core+Chat&iso=20210506T17&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, or if you have suggestions for discussion
questions, please leave a comment below!

 * Housekeeping
    - Check in 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. scrub frequency
 * Project Updates
    - CSS Audit ([#49582](https://core.trac.wordpress.org/ticket/49582))
    - 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))
 * Open Floor + CSS Link Share

[#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/38/?output_format=md)

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