Title: 2021 – Page 23 – Make WordPress Core

---

#  Yearly Archives: 2021

 [  ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/)
10:13 am _on_ August 3, 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: 29 July 2021](https://make.wordpress.org/core/2021/08/03/css-chat-summary-29-july-2021/)󠁿

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

## Housekeeping

 * [@Dave](https://profiles.wordpress.org/dave/) Ryan offered to run next week’s
   meeting on [05 July 2021 @ 9pm UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=WordPress+Core+CSS+Chat&iso=20210805T21&p1=1440&ah=1))–
   thanks Dave!

## Custom Properties (󠀁[#49930](https://core.trac.wordpress.org/ticket/49930)󠁿)

 * [@notlaura](https://profiles.wordpress.org/notlaura/) shared her [draft Make post](https://docs.google.com/document/d/1gnLJ1upGfP1BVyQJAFAOZGldNqyH2U6x7ZzQdd2m2cQ/edit?usp=sharing)
   calling for contributors. UPDATE: The post has [now been published here](https://wp.me/p2AvED-nvq)!
 * [@Dave](https://profiles.wordpress.org/dave/) Ryan shared [a note from his PR](https://github.com/ryelle/wordpress-develop/pull/5#issue-696247153)
   about the need for some common colour values – more discussion needed on this
 * [@ryelle](https://profiles.wordpress.org/ryelle/) gave an update on her recent
   progress:
    - `common.css` has been updated and pushed to the `try/custom-properties` 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".
    - Making PRs to `try/custom-properties` is a great way for contributors to add
      their contributions
    - She is keeping `try/custom-properties` up-to-date with `master`
    - Anybody can give feedback on any PRs in that repo
 * [@Dave](https://profiles.wordpress.org/dave/) Ryan asked if fallback values should
   be provided as he’s seen some changes that use them and some that don’t. [@ryelle](https://profiles.wordpress.org/ryelle/)
   clarified that she had used them in `admin-bar.css` as adminadmin (and super 
   admin) color schemes don’t apply to the frontend, so the custom properties may
   not be defined. [@Dave](https://profiles.wordpress.org/dave/) Ryan pointed out
   that the same reasoning applies to the login page too
 * [@notlaura](https://profiles.wordpress.org/notlaura/) suggested that the next
   few meetings which have work sessions should begin with a quick check in for 
   updates & housekeeping and then straight into the work session

## CSSCSS Cascading Style Sheets. Link Share / Open Floor

 * [@notlaura](https://profiles.wordpress.org/notlaura/) shared [this CSS drawing pen of a very tired squirrel](https://codepen.io/medrupaloscil/pen/WNjQmmM)
 * We speculated if a drawing tool exists that outputs CSS – does anybody know of
   such a wondrous thing?!

Thanks everyone!

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

 [  ](https://profiles.wordpress.org/paaljoachim/) [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)
9:45 am _on_ August 3, 2021     
Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/),
[core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-agenda ( 189 )](https://make.wordpress.org/core/tag/core-editor-agenda/),
[meetings ( 14 )](https://make.wordpress.org/core/tag/meetings/)   

# 󠀁[Editor Chat Agenda: 4 August 2021](https://make.wordpress.org/core/2021/08/03/editor-chat-agenda-4-august-2021/)󠁿

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

This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, August ](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210804T16&p1=187&ah=1)
[04, 2021, 04:00 PM GMT+1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210721T16&p1=187&ah=1).

_This meeting is held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7)
channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform
[https://slack.com/](https://slack.com/). The WordPress community has its own Slack
Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)._

 * [WordPress 5.8 final release.](https://wordpress.org/news/2021/07/tatum/)
 * [What’s new in Gutenberg 11.2.0](https://make.wordpress.org/core/2021/08/05/whats-new-in-gutenberg-11-2-0-4-august/)
 * [Whats next in Gutenberg: July and August.](https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/)
 * [Project updates based on the latest site editing scope](https://github.com/WordPress/gutenberg/issues/33094)&
   5.8 Priorities:
    - 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 & Navigation Editor.
    - Template editor.
    - Patterns.
    - Styling.
    - Mobile Team.
 * Task Coordination.
 * Open Floor.

If you are not able to attend the meeting, you are encouraged to share anything 
relevant for the discussion:

 * If you have 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/)
9:48 pm _on_ August 2, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[core ( 743 )](https://make.wordpress.org/core/tag/core/), meta5802, [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)

# 󠀁[A Week in Core – August 2, 2021](https://make.wordpress.org/core/2021/08/02/a-week-in-core-august-2-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 July 26 and 
August 26, 2021.

 * 24 commits
 * 24 contributors
 * 85 tickets created
 * 7 tickets reopened
 * 58 tickets closed

Pending the appointment of the WordPress 5.9 team, a number of tickets have been
fixed, waiting for the next minor releaseMinor Release A set of releases or versions
having the same minor version number may be collectively referred to as .x , for
example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions
in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements
to existing features and functionality.(s). No release date is yet available for
5.8.1, but it should arrive in a couple of weeks.

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=08%2F02%2F2021&daysback=7&authors=&ticket=on&changeset=on&repo-=on&repo-design=on&repo-tests=on&sfp_email=&sfph_mail=&update=Update).
The following is a summary of commits, organized by component and/or focus.

## Code changes

### Build/Test Tools

 * Post a message to [#core](https://make.wordpress.org/core/tag/core/) in 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/)
   when a workflow fails – [#52644](https://core.trac.wordpress.org/ticket/52644)
 * Remove the check for changes to version-controlled files in the Test Old 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". workflow – [#53799](https://core.trac.wordpress.org/ticket/53799)
 * Revert the test and coding standards changes in [[51511]](https://core.trac.wordpress.org/changeset/51511)–
   [#52644](https://core.trac.wordpress.org/ticket/52644)
 * Split packages and blocks to their webpack configs – [#53690](https://core.trac.wordpress.org/ticket/53690)

### Bundled Themes

 * Remove extra trailing spaces from translatable strings in 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. patterns–
   [#53774](https://core.trac.wordpress.org/ticket/53774)

### Coding Standards

 * Apply some alignment fixes from `composer format` – [#53729](https://core.trac.wordpress.org/ticket/53729)
 * Coding Standards: Fix typo in the JSJS JavaScript, a web scripting language typically
   executed in the browser. Often used for advanced user interfaces and behaviors.
   function name for handling the password reset button – [#53359](https://core.trac.wordpress.org/ticket/53359)
 * Code Modernization: Silence the deprecation warning for missing return type in`
   JsonSerializable_Object` – [#53635](https://core.trac.wordpress.org/ticket/53635)
 * Add missing documentation for the `minute` parameter of `WP_Query` – [#53399](https://core.trac.wordpress.org/ticket/53399)

### Documentation

 * Clarify the `@return` value for `WP_Filesystem_Base::getnumchmodfromh()` – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Correct `@return` type for `WP_Filesystem_Base::getnumchmodfromh()` – [#53793](https://core.trac.wordpress.org/ticket/53793)
 * Correct the documented allowed range for the `minute` and `second` parameters
   of `WP_Query` – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Document the `$wpdb` global in `WP_Debug_Data::get_mysql_var()` – [#53845](https://core.trac.wordpress.org/ticket/53845)
 * Fix typo in the `WP_Upgrader::install_package()` description – [#53399](https://core.trac.wordpress.org/ticket/53399)
 * Replace `$this` in hook param docs with more appropriate names – [#53457](https://core.trac.wordpress.org/ticket/53457)

### Networks and Sites

 * Replace two remaining occurrences of “blogblog (versus network, site)” with “
   site” in user-facing strings – [#53775](https://core.trac.wordpress.org/ticket/53775)

### Site Health

 * Add some more MySQLMySQL MySQL is a relational database management system. A 
   database is a structured collection of data where content, configuration and 
   other options are stored. [https://www.mysql.com](https://www.mysql.com/) information
   to the Site Health Info screen – [#53845](https://core.trac.wordpress.org/ticket/53845)

### Site Health

 * Standardise site health check status message punctuation – [#53594](https://core.trac.wordpress.org/ticket/53594)

### TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. 󠀁[https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies)󠁿.

 * Pass correct default value for `$post_id` to `wp_terms_checklist()` in the posts
   list table – [#43639](https://core.trac.wordpress.org/ticket/43639)

### Themes

 * Add “Template Editing” to the list of WordPress theme features – [#53556](https://core.trac.wordpress.org/ticket/53556),
   [#meta5802](https://meta.trac.wordpress.org/ticket/5802)
 * Make sure `get_theme_mods()` always returns an array – [#51423](https://core.trac.wordpress.org/ticket/51423)

### Upgrade/Install

 * Add files for 5.8 to the `$_old_files` list that were missed – [#53702](https://core.trac.wordpress.org/ticket/53702)
 * Avoid creating nonce during installation – [#53830](https://core.trac.wordpress.org/ticket/53830)
 * Skip any `node_modules` directories when removing Genericons `example.html` files
   on update – [#52765](https://core.trac.wordpress.org/ticket/52765)
 * Store correct result when bulk updating plugins or themes – [#53002](https://core.trac.wordpress.org/ticket/53002)

## Props

**Thanks to the 24 people who contributed to WordPress Core on Trac last week:**
[@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/) (3), [@desrosj](https://profiles.wordpress.org/desrosj/)(
3), [@audrasjb](https://profiles.wordpress.org/audrasjb/) (3), [@jrf](https://profiles.wordpress.org/jrf/)(
2), [@johnbillion](https://profiles.wordpress.org/johnbillion/) (2), [@donmhico](https://profiles.wordpress.org/donmhico/)(
2), [@mukesh27](https://profiles.wordpress.org/mukesh27/) (2), [@afragen](https://profiles.wordpress.org/afragen/)(
2), [@pbiron](https://profiles.wordpress.org/pbiron/) (1), [@ocean90](https://profiles.wordpress.org/ocean90/)(
1), [@WFMattR](https://profiles.wordpress.org/wfmattr/) (1), [@aristath](https://profiles.wordpress.org/aristath/)(
1), [@youknowriad](https://profiles.wordpress.org/youknowriad/) (1), [@poena](https://profiles.wordpress.org/poena/)(
1), [@pwtyler](https://profiles.wordpress.org/pwtyler/) (1), [@tareiking](https://profiles.wordpress.org/tareiking/)(
1), [@bobbingwide](https://profiles.wordpress.org/bobbingwide/) (1), [@zodiac1978](https://profiles.wordpress.org/zodiac1978/)(
1), [@xknown](https://profiles.wordpress.org/xknown/) (1), [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/)(
1), [@sanketchodavadiya](https://profiles.wordpress.org/sanketchodavadiya/) (1),
[@swissspidy](https://profiles.wordpress.org/swissspidy/) (1), [@schlessera](https://profiles.wordpress.org/schlessera/)(
1), and [@ankitmaru](https://profiles.wordpress.org/ankitmaru/) (1).

**Congrats and welcome to our 2 new contributors of the week! **[@pwtyler](https://profiles.wordpress.org/pwtyler/)
and [@tareiking](https://profiles.wordpress.org/tareiking/) ♥️

**Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)(
15), [@desrosj](https://profiles.wordpress.org/desrosj/) (5) and [@johnbillion](https://profiles.wordpress.org/johnbillion/)(
4).

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

 [  ](https://profiles.wordpress.org/ajitbohra/) [Ajit Bohra](https://profiles.wordpress.org/ajitbohra/)
12:27 pm _on_ August 2, 2021     
Tags: [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/),
[core-editor-summary ( 185 )](https://make.wordpress.org/core/tag/core-editor-summary/),
[editor ( 223 )](https://make.wordpress.org/core/tag/editor/), [gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/),
[meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/)   

# 󠀁[Editor chat summary: Wednesday, 28 July 2021](https://make.wordpress.org/core/2021/08/02/editor-chat-summary-wednesday-28-july-2021/)󠁿

This post summarizes the latest weekly Editor meeting ([agenda](https://make.wordpress.org/core/2021/07/26/editor-chat-agenda-28-july-2021/),
[slack transcript](https://wordpress.slack.com/archives/C02QB2JS7/p1627480826045300)),
held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) 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, on[ Wednesday, July 28, 2021, 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210728T1400).

## WordPress 5.8

WordPress 5.8 was released on 20th July check out the [release post](https://wordpress.org/news/2021/07/tatum)
for a complete list of features and enhancements.

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

Gutenberg 11.1.0 was released on 21st July check out the [release post](https://make.wordpress.org/core/2021/07/21/whats-new-in-gutenberg-11-1-0-21-july/)
for a complete list of features and enhancements:

## Gutenberg 11.2.0

[Gutenberg 11.2.0 RC](https://github.com/WordPress/gutenberg/releases/tag/v11.2.0-rc.1)
is now available for testing.

## Monthly Plan

The monthly update containing the high-level items that Gutenberg contributors are
focusing on for June are:

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

For a detailed plan check out [monthly priorities](https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/)
post.

## Updates on the key projects

[@chipsnyder](https://profiles.wordpress.org/chipsnyder/)

For the Mobile side of things we have:

 * Soon Working to update the [Mobile Gallery Block Refactor](https://github.com/WordPress/gutenberg/pull/31306)
   with the changes from Web, should be ready this week.
 * Work for the iOSiOS The operating system used on iPhones and iPads. share extension
   on hold as we investigate some of the technical challenges there
    _In Progress:_

 * Editor Onboarding.
 * Adding search to the block inserter.
 * Embed block.
 * Integration tests.
 * Support GSS Font Settings and specific text color settings.

[@annezazu](https://profiles.wordpress.org/annezazu/)

 * block-based widgets editor crew is focused on [addressing the issues for the 5.8.1 milestone](https://github.com/WordPress/gutenberg/milestone/155).
 * [@critterverse](https://wordpress.slack.com/team/U01J0FUKMUP) shared an [awesome design dive into widgets in 5.8 and beyond](https://make.wordpress.org/design/2021/07/27/widgets-in-wordpress-5-8-and-beyond/)
   highly recommend checking it out. This might not fit perfectly into styling but
   I did want to note this awesome effort to work on adding [flex layout support](https://github.com/WordPress/gutenberg/pull/33359)
   to the block editor. This should help start to address a big point of feedback
   that’s come from the [#fse-outreach-experiment](https://wordpress.slack.com/archives/C015GUFFC00)
   in allowing more customization options.
 * As for templates, afaik, I don’t think much work is happening there just yet 
   beyond designs that have been shared due to 5.8 landing .

## Task Coordination

_Note: Anyone reading this summary outside of the meeting, please drop a comment
in the post summary, if you can/want to help with something._

[@youknowriad](https://profiles.wordpress.org/youknowriad/)

 * I’m working on the Flex Layout a bit, and experimenting with multi-layout architecture
   for inner blocks
 * I’ve also spent some time on performance jobs, tooling around that and I’m planning
   to continue that a bit
 * Reviewing a number of PRs

[@get_dave](https://profiles.wordpress.org/get_dave/)

 * Seeking a review for a PR to [fix a regression in copy/paste for Windows users](https://github.com/WordPress/gutenberg/pull/33607).
 * Looking for a review of PR to [only show image and description placeholders in rich previews of link UI if the data is available](https://github.com/WordPress/gutenberg/pull/33660/files).
 * Looking for feedback on [whether we should wrap long text when displaying in the Link UI or truncate in the middle](https://github.com/WordPress/gutenberg/issues/33586).
   Opinions welcome. Will affect the entire editor.
 * Any advice on [alternative UA string’s to use for the `url-details` REST API endpoint to improve the likelihood an external site will accept our HTTP request](https://github.com/WordPress/gutenberg/issues/33722)
   would be much appreciated. I’ve also pinged the 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/)
   team

[@mamaduka](https://profiles.wordpress.org/mamaduka/)

 * [Refactored](https://github.com/WordPress/gutenberg/pull/33695) Post Author component
   for editor. It now only makes _one request to render the component instead of
   four_.
 * [Deprecated](https://github.com/WordPress/gutenberg/pull/33725) `getAuthors` 
   data selector in favor of `getUsers`.
 * Fixed [regression](https://github.com/WordPress/gutenberg/pull/33679) in `withFontSizes`
   HOC. I would love to get some feedback on this PR and maybe ship with 5.8.1.
 * Now it’s possible to pass context to `getUser` and similar [data selector shortcuts](https://github.com/WordPress/gutenberg/pull/33689).
 * Worked on [flaky](https://github.com/WordPress/gutenberg/pull/33721) “Block Hierarchy
   Navigation” test issue.
 * Fixed issue when hitting `maxLength` in `FormTokenField` component [triggered an error](https://github.com/WordPress/gutenberg/pull/33623)

[@annezazu](https://profiles.wordpress.org/annezazu/)

 * I was out last week but am working on a few things this week for the [#fse-outreach-experiment](https://wordpress.slack.com/archives/C015GUFFC00)
   including a hallway hangout happening likely tomorrow (to be announced soon),
   a survey of block theme authors, and the next call for testing.
 * Working to try to [update the github template to use forms](https://github.com/WordPress/gutenberg/pull/33713)
   as well to perhaps make it easier for people to report issues.
 * Hoping to fit in some time to triagetriage The act of evaluating and sorting 
   bug reports, in order to decide priority, severity, and other factors. too.

## Open Floor

[@mikeschroder](https://profiles.wordpress.org/mikeschroder/)

 * If it’s okay, I’d be interested in shadowing someone close to my timezone (JST,
   so I’m guessing APAC or EU would work best) on a Gutenberg release, to learn 
   more about what’s involved.
 * I’d eventually love to be able to help with running one, and hoping that would
   help with learning about the knowledge gaps to fill.

[@get_dave](https://profiles.wordpress.org/get_dave/)

 * Could whoever is running the Gutenberg PluginPlugin A plugin is a piece of software
   containing a group of functions that can be added to a WordPress website. They
   can extend functionality or add new features to your WordPress websites. WordPress
   plugins are written in the PHP programming language and integrate seamlessly 
   with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
   or can be cost-based plugin from a third-party. release today please let me know
   how they found the [automated changelog feature grouping](https://github.com/WordPress/gutenberg/pull/33229)?
   I worked on [a couple of PRs on that](https://github.com/WordPress/gutenberg/pull/33625)
   and I’m curious to know whether anything could be improved. My DM’s are open.
 * Also on that note, please can I make a plea for folks to consider being even 
   more proactive in assigning labels to 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/)
   Issues? With the correct labels assigned creating the release changelog can be
   far more automated. I’ve noticed a number of recent PRs without any labels and
   so I’m hopeful that we can reverse that trend for the benefit of the release 
   leads. Much appreciated.

[@mamaduka](https://profiles.wordpress.org/mamaduka/)

 * I try to label the issues, but can do same for PRs as well 

[Read complete transcript](https://wordpress.slack.com/archives/C02QB2JS7/p1627480826045300)

[#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/),
[#editor](https://make.wordpress.org/core/tag/editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/),
[#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/)

 [  ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/)
10:05 am _on_ August 2, 2021     
Tags: [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/)

# 󠀁[Call for CSS contributors! Help implement custom properties in WP Admin.](https://make.wordpress.org/core/2021/08/02/call-for-css-contributors-help-implement-custom-properties-in-wp-admin/)󠁿

## 󠀁[󠀁[WordPress needs your CSSCSS Cascading Style Sheets. chops!

In[ #core-css](https://make.wordpress.org/core/tag/core-css/), we have been working
for over a year to devise how to implement custom properties for WP Adminadmin (
and super admin) in order to allow extended flexibility of color schemes, e.g. dark
mode and high contrast. After much deliberation, research, and prototyping, we are
now going forward with replacing the current color scheme implementation with custom
properties as outlined in ticketticket Created for both bug reports and feature 
development on the bug tracker.[ #49582](https://core.trac.wordpress.org/ticket/49930),
and **we need some help**!

If you’d like to get started on your own or learn details about this work, we are
keeping track of our workflow and collecting information that will serve as future
documentation in this Google Doc:[ WordPress Core CSS custom properties](https://docs.google.com/document/d/1Z0Wo1W0ZQwFJYPcJ8GlsubA9uKhcFdT8ifYnso82z9I/edit#).

## Join our Custom Property Work Sessions

We also know that it can take time to understand the nuances of a project enough
to contribute, it can be intimidating, and it can be hard to designate the time 
for it. That’s why we are devoting the next three weekly CoreCore Core is the set
of software required to run WordPress. The Core Development Team builds WordPress.
CSS Chats to work time and “office hours”, where experienced folks will be available
to help with any issues in 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/).

The dates and times for the _CSS Chat: Custom Property Work Session_ editions of
the weekly meeting will be:

 * August 5, 2021 at 21:00 UTC
 * August 12, 2021 at 21:00 UTC
 * August 19, 2021 at 21:00 UTC

## Excellent Opportunity for New Contributors

This is a _great_ opportunity to get involved with contributing code to WordPress!
The knowledge you’ll need for contributing is:

 * Ability to fork and clone a repo from 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/)
   and create your own 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".
 * Run commands to start the WordPress development environment
 * Read CSS selectors from a file and find what they refer to in the DOM
 * Understanding of CSS custom properties (a.k.a. CSS variables) syntax

Some helpful links for where to obtain this knowledge:

 * [The FAQ for New Contributors](https://make.wordpress.org/core/handbook/tutorials/faq-for-new-contributors/)
   is the place to start with lots of information about contributing to WordPress!
 * [Setting Up Your Development Environment](https://make.wordpress.org/core/handbook/tutorials/getting-started/#setting-up-your-development-environment)
   in the WordPress Core Handbook
 * [Using Custom Properties (variables)](https://developer.mozilla.org/en-US/docs/Web/CSS/Using_CSS_custom_properties)
   is a good overview of the concepts of custom properties, and [A Complete Guide to Custom Properties](https://css-tricks.com/a-complete-guide-to-custom-properties/)
   has more detailed info.

That said, **this knowledge is not required for attending the work sessions**. If
you run into an issue or have trouble following the doc above, just ask in Slack
during one of the meetings, and someone will help.

_We hope you will join us to help advance and maintain WordPress’ core stylesheets!_

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

 [  ](https://profiles.wordpress.org/marybaum/) [marybaum](https://profiles.wordpress.org/marybaum/)
12:40 am _on_ July 30, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[core ( 743 )](https://make.wordpress.org/core/tag/core/), [dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/),
[summary ( 975 )](https://make.wordpress.org/core/tag/summary/)   

# 󠀁[Devchat summary, July 28, 2021](https://make.wordpress.org/core/2021/07/30/devchat-summary-july-28-2021/)󠁿

A week after the release of WordPress 5.8, [@desrosj](https://profiles.wordpress.org/desrosj/)
led a well attended but quick chat [on this agenda.](https://make.wordpress.org/core/2021/07/27/dev-chat-agenda-for-july-28-2021/)

## Highlighted blogblog (versus network, site) posts

Jonathan drew the group’s attention to these posts:

> [A Week in Core – July 26, 2021](https://make.wordpress.org/core/2021/07/26/a-week-in-core-july-26-2021/)

> [CSS Chat Summary: 22 July 2021](https://make.wordpress.org/core/2021/07/27/css-chat-summary-22-july-2021/)

> [Editor chat summary: 21 July, 2021](https://make.wordpress.org/core/2021/07/21/editor-chat-summary-21-july-2021-2/)

> [[Request for feedback] Updater Proof of Concept](https://make.wordpress.org/core/2021/07/21/request-for-feedback-updater-proof-of-concept/)

> [Refining WordPress core’s lazy-loading implementation](https://make.wordpress.org/core/2021/07/15/refining-wordpress-cores-lazy-loading-implementation/)

He also added a late post of his own:

> [Consistent minor release squad leaders for each major branch: Trial run retrospective and 5.8.x releases](https://make.wordpress.org/core/2021/07/28/consistent-minor-release-squad-leaders-for-each-major-branch-trial-run-retrospective-and-5-8-x-releases/)

If you’d like to help with 5.8.xx minor releases, leave a comment on that post.

## To-do items on 5.8

Moving on, [@desrosj](https://profiles.wordpress.org/desrosj/) opened one last review
of the 5.8 release and asked the group for retrospective comments and other feedback.

In reply, [@chanthaboune](https://profiles.wordpress.org/chanthaboune/) said she’d
likely have her retrospective up later in the day. And she said [@matveb](https://profiles.wordpress.org/matveb/)
will shortly have some thoughts about features to target for 5.9.

Remember, also, that `trunk` is open now, so if you’re a committercommitter A developer
with commit access. WordPress has five lead developers and four permanent core developers
with commit access. Additionally, the project usually has a few guest or component
committers - a developer receiving commit access, generally for a single release
cycle (sometimes renewed) and/or for a specific component., keep committing whatever
you feel is ready! _(Ed. note: Plus, we’re also in alpha for 5.9, so whether you’re
a committer or not, if you’re passionate about bringing a new feature into CoreCore
Core is the set of software required to run WordPress. The Core Development Team
builds WordPress., now is the time to do what it takes to land it.)_

## Component maintainers

[@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) checked in with
news on Build/Test, where ticketticket Created for both bug reports and feature 
development on the bug tracker. [#53363](https://core.trac.wordpress.org/ticket/53363)
has details on some 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 and updated naming to follow established conventions.

On U[grade/Install, Sergey added a second plug for his[ feedback request on the updater proof of concept highlighted above.](https://make.wordpress.org/core/2021/07/21/request-for-feedback-updater-proof-of-concept/)

## Open Floor

Above, in highlighted posts, you probably noticed that [@desrosj](https://profiles.wordpress.org/desrosj/)
asked for comments [on his minor-releases post](https://wordpress.slack.com/archives/C02RQBWTW/p1627503737465000?thread_ts=1627502698.454100&cid=C02RQBWTW)
if you want to help with the 5.8.x minors. [He actually added that suggestion in Open Floor.](https://wordpress.slack.com/archives/C02RQBWTW/p1627503737465000?thread_ts=1627502698.454100&cid=C02RQBWTW)

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

 [  ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/)
6:42 pm _on_ July 29, 2021     
Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/),
[core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/)   

# 󠀁[CSS Chat Agenda: July 29, 2021](https://make.wordpress.org/core/2021/07/29/css-chat-agenda-july-29-2021/)󠁿

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled
for Thursday July 29 at 21:00PM UTC. The 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/).

 * **Housekeeping**
 * **Custom Properties** ([#49930](https://core.trac.wordpress.org/ticket/49930))
    - [Call for Contributors Make post](https://docs.google.com/document/d/1gnLJ1upGfP1BVyQJAFAOZGldNqyH2U6x7ZzQdd2m2cQ/edit?usp=sharing)
 *  - Discussion as needed
    - Work time
 * **Open Floor + CSS Link Share**

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

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

 [  ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/)
8:56 pm _on_ July 28, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[retrospective ( 23 )](https://make.wordpress.org/core/tag/retrospective/)   

# 󠀁[WordPress 5.8 ‘Tatum’ Retrospective](https://make.wordpress.org/core/2021/07/28/wordpress-5-8-tatum-retrospective/)󠁿

A lot of things changed with the way that the WordPress 5.8 release was managed.
A retrospective is always a good idea after a project, but in this case I wanted
to be sure I cataloged the big changes for anyone who **felt** that it was different,
but couldn’t quite put words to it. [I originally shared this with the release team in Slack.](https://wordpress.slack.com/archives/C01VACX5E2W/p1621980817077100)

 * **The teamwork had a different feeling.** Instead of having buddies or cohorts
   of learning contributors (roughly one-to-one), we put the squad in a public channel
   to coordinate the work (one-to-many).
 * **The release process had a different feeling.** We made feature freeze independent
   of any other type of milestone and also are trying to be more focused about what
   work is done in each phase.
 * **The included features had a different feeling.** Instead of flipping the switch
   on a massive change for everyone, full site editing is being being shipped in
   smaller, more manageable chunks so it’s easier to catch up and we can iterate
   as we go.
 * **The environment is different. **We’ve all been struggling through this pandemic
   and being isolated from those we care for. Whether we recognize it or not, that
   has a profound impact on what we choose to do with our spare time, how we are
   able to meet others where they are, and whether we “grow through” or “bounce 
   back” from hurdles that stand in our way.

Anyone is welcome to participate in this retro, so [please take a few moments to fill in the form](https://docs.google.com/forms/d/e/1FAIpQLSei8fSLjV0um4hk_1JKwgu-8E6mpNwwxF3j43mInW7lnVOTDw/viewform?usp=sf_link)
or leave public feedback in the comments below. It is not anonymous in case I need
some clarification, but your email address will not be kept. **The form will be 
open until August 15, 2021.**

Thank you everyone for your contribution to this release, and thanks in advance 
for taking the time to help make future releases even better!

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

 [  ](https://profiles.wordpress.org/desrosj/) [Jonathan Desrosiers](https://profiles.wordpress.org/desrosj/)
7:05 pm _on_ July 28, 2021     
Tags: [5.7 ( 67 )](https://make.wordpress.org/core/tag/5-7/),
[5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/)   

# 󠀁[Consistent minor release squad leaders for each major branch: Trial run retrospective and 5.8.x releases](https://make.wordpress.org/core/2021/07/28/consistent-minor-release-squad-leaders-for-each-major-branch-trial-run-retrospective-and-5-8-x-releases/)󠁿

During the 5.8 release cycle, a Release LeadRelease Lead The community member ultimately
responsible for the Release. and Release Deputy was named for all 5.7.x releases
in a trial run. The experiment was an attempt to address several pain points that
made executing minor releases needlessly difficult. Each of the [pain points of the minor release cycle were expanded in detail in the original post](https://make.wordpress.org/core/2021/03/16/trial-run-consistent-minor-release-squad-leaders-for-each-major-branch/).

For the 5.7.x releases, [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/)
and [@audrasjb](https://profiles.wordpress.org/audrasjb/) were [named as Release Lead and Release Deputy respectively](https://make.wordpress.org/core/2021/03/22/wordpress-5-7-1-maintenance-release-schedule/).
In the months between the 5.7 and 5.8 releases, they successfully planned and released
2 minor 5.7.x versions with an average of 4.5 weeks between each. The gap between
the final minor releaseMinor Release A set of releases or versions having the same
minor version number may be collectively referred to as .x , for example version
5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (
five dot two) branch of that software. Minor Releases often make improvements to
existing features and functionality. (5.7.2) and 5.8 was 9.7 weeks.

## Feedback

In an effort to evaluate how this process went, they were asked for some answers
to a handful of questions. Here is some collected feedback from [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/)
on how the process went.

### What went well?

Generally I thought the experiment was successful and it was good to be able to 
concentrate (and only be expected to concentrate) on the minor releases rather than
try to track both major and minor. More specifically:

 * Getting a few more people in the AEST timezone involved than usual helped with
   coordination.
 * Starting early my time for releases was good for the .1 version as it went longer
   than expected.
 * Probably should have asked for author rather than contributor permission on w.
   org/news so I could actually publish the posts I prepared.
 * Having scripts prepped a day in advance was great at reducing stress and allowed
   for dry-runs (excluding commit).

### What went poorly?

 * Night owls or not, I don’t think it was great having me in APAC and [@audrasjb](https://profiles.wordpress.org/audrasjb/)
   in EU working as team leads, everything that was good about release times for
   me was exactly the reverse for [@audrasjb](https://profiles.wordpress.org/audrasjb/)(
   and [@desrosj](https://profiles.wordpress.org/desrosj/) but to a lesser extent).
 * Better prep on the .1 release could have shortened the time for committing and
   moving on to the release party.
 * Needed to pull in a couple of people on the release day for the .1 release.
 * Finding someone with mission control access is not easy (especially in timezone).
   The list of those with permissions is really out of date, and some probably don’t
   need release permission any more.
 * I didn’t delegate some of the adminadmin (and super admin) stuff well and ended
   up doing a fair bit at the last minute as a result (on me for not asking).

### What did you learn?

 * How to release 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/)
   packages, although doing so on my first production commits to the repository 
   was a little brave.
 * Depending on the number of security backports, and how far back they need to 
   go, release day for a minor can be busier than a major.
 * Process page in the handbook is quite out of date: updated a few steps after 
   each of the two releases.

### What support did you receive?

A lot.

 * [@gziolo](https://profiles.wordpress.org/gziolo/) and [@isabel_brison](https://profiles.wordpress.org/isabel_brison/)
   helped a great deal with getting the Gutenberg release process down, especially
   [@gziolo](https://profiles.wordpress.org/gziolo/) by updating the undocumented
   steps as I asked questions.
 * [@audrasjb](https://profiles.wordpress.org/audrasjb/), [@desrosj](https://profiles.wordpress.org/desrosj/)
   and [@whyisjake](https://profiles.wordpress.org/whyisjake/) with release processes,
   both in advance and on the day.
 * Code review of shell scripts to attempt to speed up the process.
 * [@dd32](https://profiles.wordpress.org/dd32/) with release day stuff, including
   catching quite a few things I was unaware of on the day.

### ⏎ What support could you have used?

Needed a lot more support from editor team with some planning tasks. The team was
consumed with 5.8 and Full Site Editing, so they did not have much time to spare.

### What were some responsibilities or tasks you had to take care of that you did not anticipate?

 * Expected I’d need to prep some release day scripts, but didn’t realize how many
   until I started doing them. Again, probably would have been helped by better 
   delegation
 * Didn’t realize I’d need to do NPM releases at the start but figured it out well
   before the actual release

### Anything else you feel is worth sharing?

Generally I think it went well and was successful.

## Continuing the trial in 5.8.x releases

Because the experiment was generally successful, it will be repeated in 5.8.x releases.
To reiterate the ideal criteria that was listed in the original proposal, the two
contributors serving as release lead and release deputy will be responsible for:

 * Publishing timelines and plans for each minor release.
 * Executing these plans through release day.
 * Coordinating with the Security Team lead to improve the flow of fixes from the
   team to users.
 * Assembling and requesting help from other volunteers for each release as deemed
   necessary (docs, test, specific focus areas, etc.).

Ideally, one of these two contributors has a technical background (with the abilities
to identify, confirm, test, and approve 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 and changes),
and the other has a project manager or coordinator background (with the abilities
to create release timelines, coordinate contributors, and help unblock efforts).

One additional (potentially optional) criteria would be that either the lead or 
deputy be a part of the previous major releasemajor release A release, identified
by the first two numbers (3.6), which is the focus of a full release cycle and feature
development. WordPress uses decimaling count for major release versions, so 2.8,
2.9, 3.0, and 3.1 are sequential and comparable in scope.’s squad, or be very familiar
with the changes that were introduced in that major release. This would further 
increase the speed at which the minor releases are able to fix related bugs, as 
they are already “up to speed” on the changes.

In recent years, the gap between major releases has been, on average, 3 to 5 months.
If necessary, contributors can 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.) in and 
out of the role should circumstances change and it becomes necessary.

If you’re interested in volunteering as a Release Lead or Release Deputy for the
5.8.x releases, please comment below!

_Props [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) and [@audrasjb](https://profiles.wordpress.org/audrasjb/)
for their great work during the 5.7.1 and 5.7.2 releases, and [@chanthaboune](https://profiles.wordpress.org/chanthaboune/)
for pre-publish review._

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

 [  ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/)
9:57 pm _on_ July 27, 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: 22 July 2021](https://make.wordpress.org/core/2021/07/27/css-chat-summary-22-july-2021/)󠁿

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

## Housekeeping

 * No housekeeping items this week

## Custom Properties (󠀁[#49930](https://core.trac.wordpress.org/ticket/49930)󠁿)

 * [@notlaura](https://profiles.wordpress.org/notlaura/) shared some background 
   on the project for new participants and suggested another session of individual
   work time
 * [@notlaura](https://profiles.wordpress.org/notlaura/) added [a note to the trac ticket](https://core.trac.wordpress.org/ticket/49930#comment:21)
   indicating who has “claimed” particular coreCore Core is the set of software 
   required to run WordPress. The Core Development Team builds WordPress. CSSCSS
   Cascading Style Sheets. files

30 or so minutes later…

 * [@Dave](https://profiles.wordpress.org/dave/) Ryan reported having made solid
   progress on `login.css` & finding some near-duplicate shades of blue, for which
   he added new custom properties. Work on colour unification can come later
 * [@notlaura](https://profiles.wordpress.org/notlaura/) had a similar experience
   with shades of grey and agreed with the approach. [@Dave](https://profiles.wordpress.org/dave/)
   Ryan added a note about it to the shared doc

## CSS Link Share / Open Floor

 * [@notlaura](https://profiles.wordpress.org/notlaura/) shared a link to [a very cool CSS-only clock demo](https://css-tricks.com/of-course-we-can-make-a-css-only-clock-that-tells-the-current-time/)

Thanks everyone!

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

# Post navigation

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

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