Title: 2021 – Page 49 – Make WordPress Core

---

#  Yearly Archives: 2021

 [  ](https://profiles.wordpress.org/paaljoachim/) [Paal Joachim Romdahl](https://profiles.wordpress.org/paaljoachim/)
4:57 pm _on_ March 8, 2021     
Tags: [agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/),
[core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-agenda ( 189 )](https://make.wordpress.org/core/tag/core-editor-agenda/),
[meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/)   

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

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

This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, March 10, 2021, 03:00 PM GMT+1](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+Editor+Meeting&iso=20210310T09&p1=2157&ah=1).

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

 * [WordPress 5.7](https://wordpress.org/news/2021/03/esperanza/)
 * 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.2
 * [Monthly Plan for March 2021](https://make.wordpress.org/core/2021/03/08/whats-next-in-gutenberg-march-2021/)
   and key project updates:
    - Global Styles.
 *  - BlockBlock Block is the abstract term used to describe units of markup that,
      composed together, form the content or layout of a webpage using the WordPress
      editor. The idea combines concepts of what in the past may have achieved with
      shortcodes, custom HTML, and embed discovery into a single consistent API 
      and user experience. based WidgetWidget A WordPress Widget is a small block
      that performs a specific function. You can add these widgets in sidebars also
      known as widget-ready areas on your web page. WordPress widgets were originally
      created to provide a simple and easy-to-use way of giving design and structure
      control of the WordPress theme to the user. Editor.
    - Navigation block.
    - Full Site Editing.
 * 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/), 
[#meeting](https://make.wordpress.org/core/tag/meeting/)

 [  ](https://profiles.wordpress.org/gziolo/) [Greg Ziółkowski](https://profiles.wordpress.org/gziolo/)
2:55 pm _on_ March 8, 2021     
Tags: [core-js ( 131 )](https://make.wordpress.org/core/tag/core-js/),
[javascript ( 130 )](https://make.wordpress.org/core/tag/javascript/), [npm packages ( 2 )](https://make.wordpress.org/core/tag/npm-packages/)

# 󠀁[Publishing WordPress packages to npm](https://make.wordpress.org/core/2021/03/08/publishing-wordpress-packages-to-npm/)󠁿

The WordPress project has started publishing its packages to npm – the largest package
repository – over 4 years ago. As of today, there is a collection of nearly 80 actively
maintained packages under the [WordPress organization](https://www.npmjs.com/org/wordpress).

The latest updates to the process were documented 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/)
in [PR#29028](https://github.com/WordPress/gutenberg/pull/29028). I wanted to share
some details about the latest addition to the process and summarize the overall 
strategy for publishing.

## Development releases

WordPress 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. can be closed or in “feature-freeze” mode. 
Usually, this happens during the WordPress ongoing release cycle (like now with 
WordPress 5.7), which takes several weeks. It means that packages don’t get any 
enhancements and new features during the ongoing WordPress 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.
process.

Another type of release was introduced to address the limitation mentioned earlier
and unblock ongoing development for projects that depend on WordPress packages. 
It takes advantage of [package distribution tags](https://docs.npmjs.com/cli/v7/commands/npm-dist-tag)
that make it possible to consume the future version of the codebase according to
npm guidelines:

> By default, the `latest` 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.) is used
> by npm to identify the current version of a package, and `npm install <pkg>` (
> without any `@<version>` or `@<tag>` specifier) installs the `latest` tag. Typically,
> projects only use the `latest` tag for stable release versions, and use other 
> tags for unstable versions such as prereleases.
> npm documentation

In this case, the `next` distribution tag is used for publishing the devolvement
version of the packages. Developers can install a package in their project by typing:

    ```wp-block-code
    npm install @wordpress/components@next
    ```

The release process is fully automated via a single command:

    ```wp-block-code
     ./bin/plugin/cli.js npm-next
    ```

The person in charge of the release needs only to run the script, and everything
else happens through interactions in the terminal.

Behind the scenes, the `wp/next` 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". is synchronized with the latest
release branch (`release/*`) created for 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/)
pluginPlugin A plugin is a piece of software containing a group of functions that
can be added to a WordPress website. They can extend functionality or add new features
to your WordPress websites. WordPress plugins are written in the PHP programming
language and integrate seamlessly with WordPress. These can be free in the WordPress.
org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party.. To avoid collisions in the versioning
of packages, we always include the newest commit’s `sha`, for example, `@wordpress/
block-editor@5.2.10-next.645224df70.0`.

## Release types and their schedule

It’s worth clarifying that the Gutenberg plugin consumes the local copy of WordPress
packages because they are developed inside the same repository. It’s a completely
different story for the WordPress coreCore Core is the set of software required 
to run WordPress. The Core Development Team builds WordPress. that consumes the 
packages from the npm registry.

The following list includes the full list of supported release types for publishing
WordPress packages to npm:

 * [Synchronizing WordPress Trunk](https://github.com/WordPress/gutenberg/blob/trunk/docs/contributors/code/release.md#synchronizing-wordpress-trunk)(`
   latest` dist tag) – when there is no “feature-freeze” mode in WordPress Core,
   then publishing happens every two weeks based on the new stable version of the
   Gutenberg plugin. Otherwise, only 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 
   get manually included and published to npm before every next 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. and 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/49/?output_format=md#alpha-beta).
   version of the following WordPress release. There is a script that automates 
   the process: `./bin/commander.js npm-latest`.
 * [Minor WordPress Releases](https://github.com/WordPress/gutenberg/blob/trunk/docs/contributors/code/release.md#minor-wordpress-releases)(`
   patch` dist tag) – only when bug fixes or security releases need to be backported
   into WordPress Core. It’s a manual process that requires cherry-picking individual
   commits and ends with executing `npm run publish:patch` command.
 * [Development Releases](https://github.com/WordPress/gutenberg/blob/trunk/docs/contributors/code/release.md#development-releases)(`
   next` dist tag) – at least every two weeks when the RC version for the Gutenberg
   plugin is released. There is a script that automates the process: `./bin/commander.
   js npm-next`.

There is also an option to perform [Standalone Package Releases](https://github.com/WordPress/gutenberg/blob/trunk/docs/contributors/code/release.md#standalone-package-releases)
at will. It should be reserved only for critical bug fixes or security releases 
that must be published to _npm_ outside of a regular WordPress release cycle. It’s
a manual process with many steps required that ends with executing `npm run publish:
prod` command.

---

We are constantly seeking feedback to improve the processes around npm packages.
The workflow for the WordPress core works quite well, and we didn’t discover any
major issues when backporting the changes applied to 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. editor in the Gutenberg plugin.
Let us know what else we can do to improve the experience for projects that consume
WordPress packages from npm.

[#core-js](https://make.wordpress.org/core/tag/core-js/), [#javascript](https://make.wordpress.org/core/tag/javascript/),
[#npm-packages](https://make.wordpress.org/core/tag/npm-packages/)

 [  ](https://profiles.wordpress.org/metalandcoffee/) [Ebonie Butler](https://profiles.wordpress.org/metalandcoffee/)
8:27 pm _on_ March 5, 2021     
Tags: [5.7 ( 67 )](https://make.wordpress.org/core/tag/5-7/)

# 󠀁[WordPress 5.7 Release Candidate 3](https://make.wordpress.org/core/2021/03/05/wordpress-5-7-release-candidate-3/)󠁿

In preparation for the final release of WordPress 5.7 on **March 9th 2021**, a Release
Candidaterelease 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/49/?output_format=md#alpha-beta).
3 has been packaged and released 🎉

The following were late-discovered blocking issues:

 * Twenty Fifteen & Twenty Sixteen: Remove extra space around post editor ([[50468](https://core.trac.wordpress.org/changeset/50468)]
   [52646](https://core.trac.wordpress.org/ticket/52646))
 * Twenty Twenty-One: Correct inner container background color for Cover Blocks ([
   [50469](https://core.trac.wordpress.org/changeset/50469)] [52676](https://core.trac.wordpress.org/ticket/52676))
 * Twenty Twenty-One: Make text readable when dark background is selected for the
   Media & Text 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. ([[50494](https://core.trac.wordpress.org/changeset/50494)]
   [52702](https://core.trac.wordpress.org/ticket/52702))
 * XML-RPC: Pass an empty array to the `xmlrpc_call` action in methods that have
   no arguments ([[50500](https://core.trac.wordpress.org/changeset/50500)] [52524](https://core.trac.wordpress.org/ticket/52524))
 * Block Editor: Fix color support for dynamic blocks ([[50489](https://core.trac.wordpress.org/changeset/50489)]
   [52709](https://core.trac.wordpress.org/ticket/52709))
 * Block Editor: Drop zone: fix media lib duplicate issue ([[50497](https://core.trac.wordpress.org/changeset/50497)]
   [52718](https://core.trac.wordpress.org/ticket/52718))
 * Block Editor: Fix cover block content position not migrating correctly from deprecated
   version ([[50497](https://core.trac.wordpress.org/changeset/50497)] [52718](https://core.trac.wordpress.org/ticket/52718))
 * Block Editor: Fix solid-color only cover has small gray border in the editor 
   only ([[50497](https://core.trac.wordpress.org/changeset/50497)] [52718](https://core.trac.wordpress.org/ticket/52718))
 * Block Editor: Add z-index to gallery fig caption to make sure it is still selectable
   over absolute positioned border ([[50497](https://core.trac.wordpress.org/changeset/50497)]
   [52718](https://core.trac.wordpress.org/ticket/52718))
 * Block Editor: Cover: Add missing align `attr` to deprecation ([[50497](https://core.trac.wordpress.org/changeset/50497)]
   [52718](https://core.trac.wordpress.org/ticket/52718))

A special thanks to the reporters of these issues for bringing them to light.

You can test the WordPress 5.7 release candidate in two ways:

 * Try the [WordPress Beta Tester](https://wordpress.org/plugins/wordpress-beta-tester/)
   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. (choose the “Bleeding edgebleeding
   edge The latest revision of the software, generally in development and often 
   unstable. Also known as [trunk](https://make.wordpress.org/core/2021/page/49/?output_format=md#trunk).”
   channel and 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./
   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/49/?output_format=md#alpha-beta).
   Only” stream options)
 * Or [download the release candidate here (zip)](https://wordpress.org/wordpress-5.7-RC3.zip).

**If you think you’ve found a 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.**, you can post to the [Alpha/Beta area](https://wordpress.org/support/forum/alphabeta)
in the support forums. We’d love to hear from you! If you’re comfortable writing
a reproducible bug report, [file one on WordPress Trac](https://make.wordpress.org/core/reports/),
where you can also find [a list of known bugs](https://core.trac.wordpress.org/tickets/major).

_Props to [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) for 
compiling all of the issues and to [@audrasjb](https://profiles.wordpress.org/audrasjb/)
and _[@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/)_ for their 
peer revision._

___________________________

_RC here, RC there…
RCs are everywhereBecause we must prepare!

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

 [  ](https://profiles.wordpress.org/mattchowning/) [Matt Chowning](https://profiles.wordpress.org/mattchowning/)
2:03 pm _on_ March 5, 2021      

# 󠀁[Dual-Licensing Gutenberg: Next Steps](https://make.wordpress.org/core/2021/03/05/dual-licensing-gutenberg-next-steps/)󠁿

Last year it was [discussed on GitHub](https://github.com/WordPress/gutenberg/issues/23651)
and then [proposed on Make/Core](https://make.wordpress.org/core/2020/09/21/proposal-dual-licensing-gutenberg-under-gpl-v2-0-and-mpl-v2-0/)
to dual-license 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/)
under the GNU General Public License v2 GPLGPL GNU General Public License. Also 
see [copyright license](https://make.wordpress.org/core/2021/page/49/?output_format=md#copyright-license).
and the Mozilla Public License v2.0, in order to broaden Gutenberg’s usage outside
of WordPress and within mobile apps.

Before doing this, every Gutenberg contribution must be dual-licensed either by 
obtaining explicit consent from the contributor or because the contribution was 
made under a dual-license. New contributions are made to Gutenberg every day so,
in order to cover every contribution, this post proposes updating Gutenberg’s license
by following these four steps:

 1. **By Friday, March 19th**: Update Gutenberg’s license to dual-license _future_ 
    contributions, but leave the project as a whole licensed under the GPL ([GitHub gist with draft interim license](https://gist.github.com/mchowning/31e0ba64a9214c79caf511272db0a5fc)),
    update the PR template to include notice of this change, and leave comments on 
    all open PRs requesting consent to the relicense the contributions in those PRs.
 2. **By Friday, April 2nd**: Open a GitHubGitHub GitHub is a website that offers online
    implementation of git repositories that can easily be shared, copied and modified
    by other developers. Public repositories are free to host, private repositories
    require a paid subscription. GitHub introduced the concept of the ‘pull request’
    where code changes done in branches by contributors can be reviewed and discussed
    before being merged by the repository owner. [https://github.com/](https://github.com/)
    issue seeking consent from all _past_ contributors to dual-license their contributions.
    Any PRs opened before the interim license change that are still open would be closed
    at this time if the contributor has not left a comment on their PR consenting to
    dual-licensing their contribution.
 3. **Three months later**: Begin removing or rewriting any contributions that cannot
    be relicensed because the contributors have not consented.
 4. **Once any contributions that cannot be relicensed have been removed or rewritten**:
    Update Gutenberg’s license to release Gutenberg under a dual-license.

Some Gutenberg modules are not relevant to using Gutenberg in software outside the
context of WordPress, and there is a [GitHub issue](https://github.com/WordPress/gutenberg/issues/29483)
to discuss whether any of these modules should remain GPL-only and, if so, how to
accomplish that.

Any questions or thoughts? Please leave a comment. 🙂

_Thank you to [@jeffpaul](https://profiles.wordpress.org/jeffpaul/) and [@pschrottky](https://profiles.wordpress.org/pschrottky/)
for reviewing this post._

 [  ](https://profiles.wordpress.org/monikarao/) [Monika Rao](https://profiles.wordpress.org/monikarao/)
5:52 am _on_ March 5, 2021      

# 󠀁[Test scrub for WordPress 5.7 Release Candidate 2 and office hours](https://make.wordpress.org/core/2021/03/05/test-scrub-for-wordpress-5-7-release-candidate-2-and-office-hours/)󠁿

As part of the 5.7 release, we’ll be hosting an **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/49/?output_format=md#alpha-beta).
2 focused test scrub** on [March 5, 2021, 13:30 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210305T1330)
in the [#core](https://app.slack.com/client/T024MFP4J/C02RQBWTW) channel on SlackSlack
Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/).
The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

In particular, we will focus on user testing and highlighted tickets to ensure there
are no regressions. 
Highlighted Tickets:[https://core.trac.wordpress.org/ticket/52702](https://core.trac.wordpress.org/ticket/52702)
[https://core.trac.wordpress.org/ticket/52676](https://core.trac.wordpress.org/ticket/52676)
[https://core.trac.wordpress.org/ticket/52638](https://core.trac.wordpress.org/ticket/52638)
[https://core.trac.wordpress.org/ticket/52646](https://core.trac.wordpress.org/ticket/52646)
[https://core.trac.wordpress.org/ticket/52326](https://core.trac.wordpress.org/ticket/52326)
[https://core.trac.wordpress.org/ticket/52605](https://core.trac.wordpress.org/ticket/52605)
[https://core.trac.wordpress.org/ticket/50025](https://core.trac.wordpress.org/ticket/50025)
[https://core.trac.wordpress.org/ticket/34281](https://core.trac.wordpress.org/ticket/34281)
[https://core.trac.wordpress.org/ticket/43890](https://core.trac.wordpress.org/ticket/43890)

Please join us and share your valuable feedback.

You can read more about Release candidaterelease 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/49/?output_format=md#alpha-beta).
2 on its announcement post.
[https://wordpress.org/news/2021/03/wordpress-5-7-release-candidate-2/](https://wordpress.org/news/2021/03/wordpress-5-7-release-candidate-2/)**
What you need**– Test website– WordPress 5.7 Release Candidate 2:– Try the [WordPress Beta Tester plugin](https://wordpress.org/plugins/wordpress-beta-tester/)(
choose the “Bleeding edgebleeding edge The latest revision of the software, generally
in development and often unstable. Also known as [trunk](https://make.wordpress.org/core/2021/page/49/?output_format=md#trunk).”
channel and 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./RC Only” stream
options)– Or [](https://wordpress.org/wordpress-5.7-RC2.zip)[download the release candidate here (zip)](https://wordpress.org/wordpress-5.7-RC2.zip).

Looking forward to testing with you!
[#test](https://make.wordpress.org/core/tag/test/),
[#testing](https://make.wordpress.org/core/tag/testing/)

 [  ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/)
8:51 pm _on_ March 4, 2021     
Tags: [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/),
[core-editor-improvement ( 35 )](https://make.wordpress.org/core/tag/core-editor-improvement/)

# 󠀁[Core Editor Improvement: Need for (page/post) Speed](https://make.wordpress.org/core/2021/03/04/core-editor-improvement-need-for-page-post-speed/)󠁿

_Thank you to [@aristath](https://profiles.wordpress.org/aristath/) who helped with
this post_.

In today’s world, speed matters whether you’re trying to write a post in the editor
or load a page as a visitor. Over the last couple of months, a lot has changed around
performance to improve both of these aspects, but the changes might have happened
so fast you missed them! This post will focus solely on front end performance with
a future post in the works that covers performance-related changes to the editor
itself. For now, read on to learn just how speedy the coreCore Core is the set of
software required to run WordPress. The Core Development Team builds WordPress. 
editor makes your site and get excited because what’s discussed here is [currently available in Gutenberg 10.1](https://make.wordpress.org/core/2021/03/02/whats-new-in-gutenberg-10-1-3-march/)!

**Updates to front end performance**

As most developers know, you can think of front end performance as the type of performance
that impacts SEO and the experience visitors have when they check out your site.
Lots of things contribute to the performance of your site including various CSSCSS
Cascading Style Sheets. styles, JavaScriptJavaScript JavaScript or JS is an object-
oriented computer programming language commonly used to create interactive effects
within web browsers. WordPress makes extensive use of JS for a better user experience.
While PHP is executed on the server, JS executes within a user’s browser. [https://www.javascript.com](https://www.javascript.com/)
files, and more. While your theme and plugins contribute to what needs to be loaded
to create the magic of viewing a page or post, the core editor does as well! 

[With the merging of this PR](https://github.com/WordPress/gutenberg/pull/28358),
CSS styles are only loaded for blocks used on a page, which cuts down the amount
of CSS needed and increases performance dramatically. For context, in previous 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/) releases,
all styles for all blocks were enqueued in a single file causing extra page load.
This means that now only what’s necessary is loaded when you’re viewing content!

After the work was done to [separate out block styles](https://github.com/WordPress/gutenberg/pull/25220),
an [additional PR was merged for Gutenberg 10.1](https://github.com/WordPress/gutenberg/pull/28358)
to improve the performance of these 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. styles. Since most blocks have fairly
small stylesheets, it didn’t make sense to send requests to the server for these
bite-sized styles. To resolve this, the tiny stylesheets were inlined, further improving
the performance by including everything the browser needs in a single request. Think
of this as sending one text message covering a few topics, rather than writing a
bunch of individual messages one after the other. 

Right now, both of the above changes are the default behavior in FSE, but they are
opt-in for non-FSE templates to avoid backward-compatibility issues with CSS overrides
in older themes. When FSE gets merged into Core, these improvements will be more
widely available and make a big difference for all. 

**Stay tuned for more**

As with many performance enhancements, it’s easier to notice when things break compared
to when they are running smoothly. Hopefully, this post gave you a behind-the-scenes
look into the work that goes into keeping your sites speedy while using the Core
Editor. While a lot of work is put into democratizing publishing in the WordPress
project, this kind of work helps democratize delivery, allowing people to get the
content they want to consume easier and faster. With [changes coming to Google Search](https://developers.google.com/search/blog/2020/11/timing-for-page-experience#:~:text=Today%20we're%20announcing%20that,security%2C%20and%20intrusive%20interstitial%20guidelines.)
related to the speed of webpages, performance improvements for both the front end
and in the editor have never been more timely. 

The work here is never done though so, if you’re interested in working on improving
performance, make sure to join [#core-editor](https://wordpress.slack.com/archives/C02QB2JS7),
check out the [current focuses](https://make.wordpress.org/core/tag/gutenberg-next/),
and attend the [Core Editor weekly meeting Wednesday @ 14:00 UTC](https://make.wordpress.org/core/tag/core-editor-agenda/).

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

 [  ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/)
7:44 pm _on_ March 4, 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: March 4, 2021](https://make.wordpress.org/core/2021/03/04/css-chat-agenda-march-4-2021/)󠁿

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled
for [Thursday, March 4, at 10:00 PM UTC](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+CSS+Weekly+Chat&iso=20210304T22&p1=1440&ah=1).
This meeting will be held in the [#core-css](https://wordpress.slack.com/archives/CQ7V4966Q)
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
    - Bug scrub leader for next week
 * Discussion: Compare ideas for naming custom properties for colors in a button.
    - We discussed creating a CodePen or similar to show how we would name colors
      for a button – see [this message with details](https://wordpress.slack.com/archives/CQ7V4966Q/p1614292416077600?thread_ts=1614292405.077500&cid=CQ7V4966Q)
      on the colors to include.
 * Project Updates
    - CSS Audit ([#49582](https://core.trac.wordpress.org/ticket/49582))
 *  - Color Scheming ([#49999](https://core.trac.wordpress.org/ticket/49999))
 * Open Floor + CSS Link Share

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

 [  ](https://profiles.wordpress.org/andraganescu/) [Andrei Draganescu](https://profiles.wordpress.org/andraganescu/)
11:47 am _on_ March 4, 2021      

# 󠀁[Core Editor Chat Notes 3 Mar., 2020](https://make.wordpress.org/core/2021/03/04/core-editor-notes-10-feb-2020-2/)󠁿

This post summarizes the latest weekly Editor meeting ([agenda](https://make.wordpress.org/core/2021/03/02/editor-chat-agenda-3-march-2021/),
[slack transcript](https://wordpress.slack.com/archives/C02QB2JS7/p1614780018437300)).
This meeting was 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, Mar. 3, 2021, 9:00 AM EDT and was facilitated by [@andraganescu](https://profiles.wordpress.org/andraganescu/).

## **WordPress 5.7 Upcoming Release **

[WordPress 5.7 RC 2](https://wordpress.org/news/2021/02/wordpress-5-7-release-candidate/)
is now available for testing.  If you are a pluginPlugin A plugin is a piece of 
software containing a group of functions that can be added to a WordPress website.
They can extend functionality or add new features to your WordPress websites. WordPress
plugins are written in the PHP programming language and integrate seamlessly with
WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. author and/or a theme developer 
test your plugins and themes against WordPress 5.7 and update the _Tested up to_
version in the readme file to 5.7. There will likely be a 5.7 RC3 later this week.

The [WordPress 5.7 Field Guide](https://make.wordpress.org/core/2021/02/23/wordpress-5-7-field-guide/)
is out! It contains a full breakdown of everything you need to know about WordPress
5.7.

## **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/)󠁿 Version 10.**1

Gutenberg 10.1 has been released! This release includes a number of nice enhancements
and as usual many 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. In addition Full Site Editing, Widgets and Navigation
screens and Global Styles saw many improvements.I believe the many recent improvements
to the different user flows related to Reusable blocks should be highlighted.

The most recent one is the enhanced creation flow, that also allows you to cancel
the action. We now have better clarity on the Image toolbar and more blocks are 
going to follow. 🙂 Finally we now have spacing options for Social Links and Buttons
that will help users achieve more elegant designs effortlessly.

Kudos to all for your help and contributions!

## **Monthly Priorities**

March monthly plan will be released soon.

 * FSE – there is a focus on [making](https://github.com/WordPress/gutenberg/pull/29335)
   the theme/template creation process [more](https://github.com/WordPress/gutenberg/pull/29517)
   WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly
   used in relation to editors, where changes made in edit mode reflect exactly 
   as they will translate to the published page..  [Infrastructure and UI milestone](https://github.com/WordPress/gutenberg/issues/24818)
   progressed with [Persistent List View](https://github.com/WordPress/gutenberg/pull/28637)
   and previews in the [browsing](https://github.com/WordPress/gutenberg/pull/29225)
   sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used
   by WordPress themes to display information that is not a part of the main content.
   It is not always a vertical column on the side. It can be a horizontal rectangle
   below or above the content area, footer, header, or any where in the theme.. 
   Almost all of the Semantic Template Parts tasks from the milestone have been 
   completed. 
 * New 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 editors – the widgets editor now has  [a preview ](https://github.com/WordPress/gutenberg/pull/29365)
   of block support in 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. while the navigation editor is quickly iterating 
   on the UIUI User interface update it got recently. Help is always welcome in 
   any shape to help with the long list of [queued](https://github.com/WordPress/gutenberg/issues/29102)
   up [issues](https://github.com/WordPress/gutenberg/issues/24687).
 * Mobile apps – [started global style support](https://github.com/WordPress/gutenberg/pull/25226),
   work progressed on reusable blocks, Removing ability to switch to the Classic
   editor switch, dual-licensing Gutenberg, search block, adding search to the block
   inserter, embed block

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

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

 * Amplifying the second [FSE call for testing ](https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/how-to-test-fse/)(
   working with marketing, reaching out to a few communities, etc)
 * Responding to the second FSE call for testing and filing issues. Thanks to all
   who have left feedback!
 * Some triagetriage The act of evaluating and sorting bug reports, in order to 
   decide priority, severity, and other factors. mainly around older issues and 
   testing FSE everyday.
 * Helped draft the proposal for dropping IE11 support.
 * Working on a Make CoreCore Core is the set of software required to run WordPress.
   The Core Development Team builds WordPress. post about the role of the Gutenberg
   plugin.
 * Working on a [Core Editor Improvement post](https://make.wordpress.org/core/tag/core-editor-improvement/)
   about performance enhancements.

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

 * This week I focused mostly on a hybrid-themes proof of concept to allow the use
   of both php templates and user-created templates: `[PR 29298](https://github.com/WordPress/gutenberg/pull/29298)`
   This can allow users to manually create templates on any theme (even non-FSE 
   themes) so they can have a regular theme, and create a completely custom frontpage.
   It would be great to have something like that in the FSE MVPMinimum Viable Product"
   A minimum viable product (MVP) is a product with just enough features to satisfy
   early customers, and to provide feedback for future product development." - [WikiPedia](https://en.wikipedia.org/wiki/Minimum_viable_product),
   but the interaction part is still a bit unclear and it would need lots of feedback
   as to how some things can happen. The PR however shows that it’s definitely possible
   to have both 
 * For next week I plan to start tackling some of the items listed in `[Issue 22724](https://github.com/WordPress/gutenberg/issues/22724)`
   so we can get the FSE MVP across the finish line on time for 5.8

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

 * Made an issue to consolidate setup instructions for core and Gutenberg. [Issue 29448](https://github.com/WordPress/gutenberg/issues/29448)
 * Added a video showing how to test a PR by downloading a special Gutenberg plugin.
   [Issue comment](https://github.com/WordPress/gutenberg/issues/28881#issuecomment-787506552)
 * Triage and testing.

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

 * Still working on navigation block adjacent tasks, and would love eyes on this
   CSSCSS Cascading Style Sheets. refactor: [PR 29465](http://github.com/WordPress/gutenberg/pull/29465)
 * Also took a stab at a frustrating embed issue that’s in the 5.7 must have categoryCategory
   The 'category' taxonomy lets you group posts / content together that share a 
   common bond. Categories are pre-defined and broad ranging.. The PR works, but
   it needs a developer to bring it home: [PR 29510](http://github.com/WordPress/gutenberg/pull/29510)

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

 * Updates for the new Component System project: Integration is moving along. [@sarayourfriend (she/her)](https://wordpress.slack.com/team/U011QMH0BHT)
   and I (mostly Sara ) are continuing to move the new components into Gutenberg.
   We’re at around 23% integrated.
 * The main working issue is [here](https://github.com/WordPress/gutenberg/issues/28399):
 * The simple status page for this project is [here](https://status.g2-components.com/).

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

 * Query Title block spinoff PR from my original one, that handles Archive Title
   for now as block variation([PR 29428](https://github.com/WordPress/gutenberg/pull/29428))
 * Some fixes for Site Logo and Query blocks

## **Open Floor**

[@annezazu](https://profiles.wordpress.org/annezazu/) asked, and got some good support,
if we could use a nudge in a dashboard 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. to get more user testing of upcoming features.

Some concern about the size and novelty of FSE was expressed and also an idea to
split existing documentation in byte sized versions.

[@Zeb](https://profiles.wordpress.org/zeb/) brought up [his PR](https://github.com/WordPress/gutenberg/pull/29394)
that fixes a bug with the Table of Contents block, asking for some review help.

[@itsjonq](https://profiles.wordpress.org/itsjonq/) [created an issue](https://github.com/WordPress/gutenberg/issues/29519)
for the RTL bug thay affects the current WordPress 5.7 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/49/?output_format=md#alpha-beta).
2, mentioned earlier in the meeting by [@swissspidy](https://profiles.wordpress.org/swissspidy/).

In the [Gutenberg repository](https://github.com/WordPress/gutenberg) the 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". `master` is now renamed to `trunk`. The post describing the change is [here](https://make.wordpress.org/core/2020/06/18/proposal-update-all-git-repositories-to-use-main-instead-of-master/)
and you can find the details on how to update your local on the repository’s home.

[[

 [  ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/)
10:50 am _on_ March 4, 2021     
Tags: [accessibility ( 59 )](https://make.wordpress.org/core/tag/accessibility/),
[browser support ( 6 )](https://make.wordpress.org/core/tag/browser-support/), [performance ( 414 )](https://make.wordpress.org/core/tag/performance/)

# 󠀁[Discussion: Dropping support for IE11](https://make.wordpress.org/core/2021/03/04/discussion-dropping-support-for-ie11/)󠁿

After digging into data and reviewing previous decisions around browser support,
this is a proposal to define a policy to stop supporting Internet Explorer 11 (IE11)
now that usage has cumulatively fallen below ~1% across three metrics. 

**Current state of IE11**

As of February 25th 2021, IE11 usage has cumulatively fallen below ~1% according
to three sources of metrics:

 * 0.71% from [StatCounter’s GlobalStats](https://gs.statcounter.com/browser-version-partially-combined-market-share#monthly-202001-202101).
 * 1.2% from [W3 Counter](https://www.w3counter.com/trends).
 * 0.46% from WordPress.comWordPress.com An online implementation of WordPress code
   that lets you immediately access a new WordPress environment to publish your 
   content. WordPress.com is a private company owned by Automattic that hosts the
   largest multisite in the world. This is arguably the best place to start blogging
   if you have never touched WordPress before. [https://wordpress.com/](https://wordpress.com/).

For comparison, the numbers above are very close to the data used to make a decision
in 2017 to [drop support for IE versions 8, 9, and 10](https://make.wordpress.org/core/2017/04/23/target-browser-coverage/).
It’s important to keep in mind that when viewing these statistics in the context
of WordPress, these percentages represent tens (if not hundreds) of thousands of
users that could potentially be left behind if support for IE11 is dropped. 

In August 2020 [Microsoft themselves announced that Microsoft 365 and Teams apps would stop supporting IE](https://techcommunity.microsoft.com/t5/microsoft-365-blog/microsoft-365-apps-say-farewell-to-internet-explorer-11-and/ba-p/1591666)
in the upcoming months. However, given that IE11 is a component bundled with Windows10,
[according to the IE Lifecycle](https://docs.microsoft.com/en-us/lifecycle/faq/internet-explorer-microsoft-edge)
it will still receive security updates as long as the Windows version it was shipped
with continues to receive support. 

In terms of the current WordPress user experience, a [flag was added to not recommend IE in BrowseHappy](https://meta.trac.wordpress.org/ticket/4863)
about 13 months ago, so by now, most WordPress users should be aware. Tied to this,
the [experience overall is not optimal in IE11](https://meta.trac.wordpress.org/ticket/4863)
with a high cost of maintenance for developers.

**Proposed Policy**

The proposed policy for WordPress is to end Internet Explorer 11 support. This was
discussed most recently in the [February 24th Core Editor Chat](https://make.wordpress.org/core/2021/02/24/editor-chat-summary-24-february-2021/)
and briefly during [February 23rd JavaScript office hours](https://wordpress.slack.com/archives/C5UNMSU4R/p1614093014007100)
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/).
More context and discussion have been shared over time [in this original Trac issue](https://core.trac.wordpress.org/ticket/49696)
that seeks to determine clear guidelines around what absolutely can’t be broken 
in order to help identify development and testing needs. 

**Benefits**

Dropping support would result in smaller scripts, lower maintenance burden, and 
decrease build times. For instance, [a recent exploration by @youknowriad](https://github.com/WordPress/gutenberg/pull/27685)
demonstrated that not transpiling the scripts to IE11 immediately resulted in a 
net reduction of nearly 84kB in 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/)
JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming
language commonly used to create interactive effects within web browsers. WordPress
makes extensive use of JS for a better user experience. While PHP is executed on
the server, JS executes within a user’s browser. [https://www.javascript.com](https://www.javascript.com/)
built files, representing a 7,78% total decrease in size; these scripts have seen
a size contraction up to 60%, with an average reduction of 24%. This is a result
of heavily [relying on transpilers, further explained by Jason Miller](https://twitter.com/_developit/status/1337147962976301057),
Web DevRel at Google. Moreover, dropping support would ultimately make WordPress’
[currently included polyfill script](https://core.trac.wordpress.org/browser/trunk/src/wp-includes/script-loader.php#L94)
obsolete, decreasing the enqueued scripts size up to 102kB more.

The smaller downloads would positively impact all users, especially those on slower
networks, or computing devices. We expect a result of dropping IE11 support to improve
performance for the vast majority of users. 

**Potential Concerns/Blockers**

_TLDR: The concerns are for those who are unable to upgrade, like financial institutions
and education sectors, and those who rely on IE11 for screen readers. _

There are major institutions like banking, government, and education that are unable
to control when they can upgrade sometimes due to legal requirements, depending 
on the country. This further underscores the need to determine a policy that takes
into consideration both a data-informed approach and the impacted user bases while
weighing the potential benefits for the wider web. 

According to a [September 2019 WebAIM survey](https://webaim.org/projects/screenreadersurvey8/#browsers),
IE11 is still used as a browser among screen readers with 11.5% share. This is an
older survey and IE11’s global share was 2.9% at the time the survey was done according
to the sources linked above. It takes time for screen reader software to support
newer browsers and the latest versions of popular screen reader NVDA have [continued improving and adding support for the Edge browser](https://www.nvaccess.org/files/nvda/releases/2020.4/nvda_2020.4_changes.html).
As a result, this post embraces an assumption that IE usage among screen reader 
users has declined since the survey as the software improves and overall usage of
IE11 has declined. Please let us know if this assumption is or if there is better
data available to refer to.

Keep in mind that there are ways to 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. gaps in functionality that’s determined critical to maintain
for a time. This post does not seek to go into technical implementation details 
though.

**Share your feedback about this proposed policy change to drop support by March
18th**

This is a tough decision to make and we want to solicit feedback from as many voices
across the community it may impact. Please note, this post is not meant to go over
any technical fallbacks at this time but to purely discuss the policy of dropping
support. 

Once we’ve gathered feedback, the next step will be to consolidate and decide the
policy. The actual technical implementation of the policy is most practical to pursue
across the numerous WordPress projects. 

_Thank you to [@mkaz](https://profiles.wordpress.org/mkaz/), [@annezazu](https://profiles.wordpress.org/annezazu/),
[@youknowriad](https://profiles.wordpress.org/youknowriad/), [@desrosj](https://profiles.wordpress.org/desrosj/)
for help writing and reviewing this post. _

 [#accessibility](https://make.wordpress.org/core/tag/accessibility/), [#browser-support](https://make.wordpress.org/core/tag/browser-support/),
[#performance](https://make.wordpress.org/core/tag/performance/)

 [  ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/)
9:16 pm _on_ March 3, 2021      

# 󠀁[Timezones and Daylight Saving Time](https://make.wordpress.org/core/2021/03/03/timezones-and-daylight-saving-time/)󠁿

It’s that time of the year again! Start or stop daylight savings time (DST) depending
on where you are in the world.

As noted by Chloé in an [Updates blog post](https://make.wordpress.org/updates/2021/02/09/2021-daylight-savings-time-planning/),
these are the dates:

 * March 14 – US/CA starts DST
 * March 29 – UK/EU starts DST
 * April 4 – AU ends DST

In the fall, 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)
who [commented on the time change](https://make.wordpress.org/core/2020/08/31/dev-chat-update/)
decided to maintain the UTC time.

I propose we continue observing UTC, as mentioned by Helen back in September 2020:

 * No more confusion about when exactly it’s changing due to differences in DST 
   implementation
 * Less important, but still a consideration, consistent naming between the two 
   meetings

If anyone is vehemently against it, please let me know. If no one has concerns about
this, I will confirm the UTC time and edit the handbook page accordingly (HT [@desrosj](https://profiles.wordpress.org/desrosj/)
for mentioning it).

Thanks

# Post navigation

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