Title: 2021 – Page 41 – Make WordPress Core

---

#  Yearly Archives: 2021

 [  ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/)
4:59 pm _on_ April 22, 2021     
Tags: [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/)

# 󠀁[CSS Chat Agenda: April 22, 2021](https://make.wordpress.org/core/2021/04/22/css-chat-agenda-april-22-2021/)󠁿

_Note: 1 hour before the meeting this week, _[@notlaura](https://profiles.wordpress.org/notlaura/)_
will lead a 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/)
CSSCSS Cascading Style Sheets. bugbug A bug is an error or unexpected result. Performance
improvements, code optimization, and are considered enhancements, not defects. After
feature freeze, only bugs are dealt with, with regressions (adverse changes from
the previous version) being the highest priority. scrub!_

This is the agenda for the upcoming CSS meeting scheduled for [Thursday, April 22, at 5:00 PM EDT](https://www.timeanddate.com/worldclock/fixedtime.html?msg=WordPress+CSS+Core+Chat&iso=20210422T17&p1=418&ah=1).
This meeting will be held in the [#core-css](https://make.wordpress.org/core/tag/core-css/)
channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform
[https://slack.com/](https://slack.com/). The WordPress community has its own Slack
Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/).

If there’s any topic you’d like to discuss, or if you have suggestions for discussion
questions, please leave a comment below!

 * Housekeeping
 * Project Updates
    - CSS Audit ([#49582](https://core.trac.wordpress.org/ticket/49582))
    - Color Scheming ([#49999](https://core.trac.wordpress.org/ticket/49999))
    - Deprecation path & JSJS JavaScript, a web scripting language typically executed
      in the browser. Often used for advanced user interfaces and behaviors. targeting
      conventions
 * Open Floor + CSS Link Share

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

 [  ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/)
3:49 pm _on_ April 21, 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: 15 April 2021](https://make.wordpress.org/core/2021/04/21/css-chat-summary-15-april-2021/)󠁿

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

## Housekeeping

 * Our next bugbug A bug is an error or unexpected result. Performance improvements,
   code optimization, and are considered enhancements, not defects. After feature
   freeze, only bugs are dealt with, with regressions (adverse changes from the 
   previous version) being the highest priority. scrub will be at [8pm UTC on 22 April](https://www.timeanddate.com/worldclock/fixedtime.html?msg=Core+CSS+bug+scrub&iso=20210422T20&p1=1440&ah=1),
   covering issues 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/)
   repo with the `CSS Styling` 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.)
 * **If anyone is interested in leading this bug scrub please let us know in `#core-
   css`!**

## Review discussion outcomes

We reviewed the outcomes from last week’s discussions:

### CSSCSS Cascading Style Sheets. deprecation path

 * Last week we discussed the two main parts of the problem:
    - Identifying deprecated CSS in a specific place e.g. `deprecated.css`
    - Providing external tools for 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. developers e.g. visually flagging deprecated
      selectors, stylelint rules
 * Deprecation should take place at selector level, not based on specific declarations
 * We agreed on using the deprecated selector `.icon16` to test run the deprecation
   path
 * The next step is for @tellthemachines to create a ticketticket Created for both
   bug reports and feature development on the bug tracker. & bring it up in dev-
   chat

### CSS class naming conventions for 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/)󠁿 targeting

 * Last week we agreed that `js-` prefix is a sensible way to identify CSS classes
   intended to be used via JavaScript
 * [@danfarrow](https://profiles.wordpress.org/danfarrow/) wondered what the transition
   process would look like, [@notlaura](https://profiles.wordpress.org/notlaura/)
   observed that it’s another deprecation problem
 * We wondered if there is a current JSJS JavaScript, a web scripting language typically
   executed in the browser. Often used for advanced user interfaces and behaviors.
   deprecation path & found a [related Make post](https://make.wordpress.org/core/2020/09/01/deprecated-javascript-globals/)
 * [@lukecarbis](https://profiles.wordpress.org/lukecarbis/) agreed that CSS deprecation
   should also be mindful of JavaScript that may be using deprecated classes for
   targeting
 * [@danfarrow](https://profiles.wordpress.org/danfarrow/) speculated that searching
   the plugins directory for instances of each deprecated CSS class might help gauge
   the impact of removing that class, but we’re not really sure what that would 
   involve
 * The next step would be to update [ticket 40686](https://core.trac.wordpress.org/ticket/40686)
   with a recommendation & also bring the topic up in dev-chat. [@notlaura](https://profiles.wordpress.org/notlaura/)
   summarised the recommendations for the ticket:

 1. Using the `.js-` namespace for classes with JS hooksHooks In WordPress theme and
    development, hooks are functions that can be applied to an action or a Filter in
    WordPress. Actions are functions performed when a certain event occurs in WordPress.
    Filters allow you to modify certain functions. Arguments used to hook both filters
    and actions look the same.
 2. These classes should not have styling attached to them, instead any JS applied 
    styling should use stateful `.is-*` classes e.g. `.is-hidden`
 3. We need to determine a workflow for updating selectors in the JS and identify third
    party plugins that might rely on them for JS purposes

## Open floor / CSS link share

 * Before the meeting [@joyously](https://profiles.wordpress.org/joyously/) [shared some ideas around implementing a Dark Mode](https://wordpress.slack.com/archives/CQ7V4966Q/p1618519321348200)
   which we discussed, concluding that the ideas are interesting & it would be good
   to see a mock up of this approach e.g. used for a coreCore Core is the set of
   software required to run WordPress. The Core Development Team builds WordPress.
   component
 * [@notlaura](https://profiles.wordpress.org/notlaura/) [shared a related pen](https://codepen.io/laras126/pen/ExZbvPY?editors=0100)
   which uses the nifty [_var space hack_](https://lea.verou.me/2020/10/the-var-space-hack-to-toggle-multiple-values-with-one-custom-property/)
   to remove the need for multiple media queries
 * [@danfarrow](https://profiles.wordpress.org/danfarrow/) recalled seeing the _var
   space hack_ used for a [CSS only version of Minesweeper](https://propjockey.github.io/css-sweeper/)

With that we were out of time. Thanks everyone!

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

 [  ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/)
10:24 pm _on_ April 20, 2021     
Tags: [5.7.1 ( 20 )](https://make.wordpress.org/core/tag/5-7-1/),
[5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [agenda ( 1,142 )](https://make.wordpress.org/core/tag/agenda/),
[dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/)   

# 󠀁[Dev Chat Agenda for April 21, 2021](https://make.wordpress.org/core/2021/04/20/dev-chat-agenda-for-april-21-2021/)󠁿

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

## Release Announcements

 * [WordPress 5.7.1](https://wordpress.org/news/2021/04/wordpress-5-7-1-security-and-maintenance-release/)
   security and maintenance release is out
 * [Gutenberg 10.4 has been released](https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/)

## Blogblog (versus network, site) Post Highlights

 * [[[A Week in Core – April 19, 2021](https://make.wordpress.org/core/2021/04/19/a-week-in-core-april-19-2021/)
 * [Full Site Editing Go/No Go | April 14, 2021](https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/)
 * [Full Site Editing Go/No Go: Next steps](https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/)

## Blog posts that need feedback

 * [Proposal: Treat FLoC like a security concern](https://make.wordpress.org/core/2021/04/18/proposal-treat-floc-as-a-security-concern/)–
   Please note, [@helen](https://profiles.wordpress.org/helen/), lead developer 
   of the WordPress project, has published a [top comment](https://make.wordpress.org/core/2021/04/18/proposal-treat-floc-as-a-security-concern/#comment-41139)
   about the proposal.

## Components check-in and status updates

 * Check-in with each component for status updates.
 * Poll for components that need assistance.

## Open Floor

Do you have something to propose for the agenda, or a specific item relevant to 
our standard list above?

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

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

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

 [  ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/)
9:10 pm _on_ April 20, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/), [gutenberg ( 547 )](https://make.wordpress.org/core/tag/gutenberg/)

# 󠀁[Full Site Editing Go/No Go: Next steps](https://make.wordpress.org/core/2021/04/20/full-site-editing-go-no-go-next-steps/)󠁿

The Full Site Editing Go/No Go demo [took place a few days ago](https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/),
where project leadership determined what new features should be included in WordPress
5.8 based on their current status, feedback gathered in calls for testing, and the
prospect of achieving a solid implementation before the feature freeze.

This post aims to provide a high-level overview of the focuses to attend to before
the feature freeze; linked individual actionable 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/)
items further develop lower-level requirements to complete. Individual items are
also being tracked in the [WordPress 5.8 FSE Must Haves project board](https://github.com/WordPress/gutenberg/projects/55#card-59207760).

## Schedule

According to the [WordPress 5.8 pre-planning schedule](https://make.wordpress.org/core/2021/03/30/5-8-pre-planning/),
the **feature freeze will take place on May 25th**, leaving room for the following
GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress.
The editor improves the process and experience of creating new content, making writing
rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes,
custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
pluginPlugin A plugin is a piece of software containing a group of functions that
can be added to a WordPress website. They can extend functionality or add new features
to your WordPress websites. WordPress plugins are written in the PHP programming
language and integrate seamlessly with WordPress. These can be free in the WordPress.
org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
or can be cost-based plugin from a third-party. releases to be merged:

| Gutenberg version | 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/41/?output_format=md#alpha-beta). release date | Stable release date | 
| 10.5 | April 21st | April 28th | 
| 10.6 | May 5th | May 12th | 
| 10.7 | **May 19th** | ~May 26th~ |

To align with this schedule, the last version to be merged in coreCore Core is the
set of software required to run WordPress. The Core Development Team builds WordPress.
before the feature freeze will be 10.7-RC, with any future bugfix applied before
or after the stable 10.7.0 being ported as well. Moreover, to ease new feature testing
with more frequent merges, as [suggested in a recent dev chat](https://make.wordpress.org/core/2021/03/25/dev-chat-meeting-summary-march-24-2021/),
Gutenberg 10.4 -without experimental features- is [already available in WordPress core](https://core.trac.wordpress.org/changeset/50761).

## Next steps

Apart from all the incremental improvements included by merging up to 9 plugin releases,
from Gutenberg 9.9 to 10.7, the following work-in-progress features are targeted
for 5.8 and should become stable by Gutenberg 10.7. 

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

Block themes might arguably represent one of the biggest core theme-building paradigm
changes in the last decade. As such, a huge effort is being done to achieve a future-
proof, evolvable foundation. With most of the infrastructure ready, the focus remains
on the `theme.json` configuration file, and the “block supports” mechanism:

 * [Refining the theme.json structure](https://github.com/WordPress/gutenberg/issues/29891)
 * [Version handling of the theme.json file](https://github.com/WordPress/gutenberg/issues/27230).
 * [Iterating over the block supports mechanism](https://github.com/WordPress/gutenberg/issues/28913).

A list of detailed requirements to meet before the feature freeze can be found at
the [Block Styles Breakdown overview issue](https://github.com/WordPress/gutenberg/issues/20331).

Once released in 5.8, theme developers will be able to create block themes and provide
quality feedback to iterate over these mechanisms.

### Introducing Theme blocks

As part of the implementation of Full Site Editing, a number of theme blocks have
been developed to cover theme/site features similar to how classic template tags
worked. The next steps are to [finish determining which of these blocks should be included in 5.8 and enabled for classic themes](https://github.com/WordPress/gutenberg/issues/28744),
and polish them, including:

 * [Query](https://github.com/WordPress/gutenberg/issues/30910)
 * [Navigation](https://github.com/WordPress/gutenberg/issues/27593)
 * [Site Title](https://github.com/WordPress/gutenberg/issues/30918)
 * [Site Logo](https://github.com/WordPress/gutenberg/issues/30406)
 * [Site Tagline](https://github.com/WordPress/gutenberg/issues/30921)

These blocks [should display a badge in the inserter](https://github.com/WordPress/gutenberg/issues/26632),
denoting they are new blocks that, while completely stable and functional, might
still need some UXUX User experience polishing and are meant to experiment and tinker
around.

### Template editing within the post editor

With one of the targets for 5.8 being to introduce block templates, users will be
able to create custom block templates for posts and pages in classic themes. Although
this feature mostly relies on the existing site editing infrastructure already available
in the plugin, [th](https://github.com/WordPress/gutenberg/issues/27814)[e](https://github.com/WordPress/gutenberg/issues/27814)
[se improvements will be focused on](https://github.com/WordPress/gutenberg/issues/27814)
to provide a great user experience. User testing is planned in coordination with
[@annezazu](https://profiles.wordpress.org/annezazu/) from the FSE Outreach program
during the WordPress 5.8 betaBeta A pre-release of software that is given out to
a large group of users to trial under real conditions. Beta versions have gone through
alpha testing in-house and are generally fairly close in look, feel and function
to the final product; however, design changes often occur as part of the process.
phase. Users are encouraged to join this program as [it provides invaluable feedback](https://make.wordpress.org/core/2021/03/16/high-level-feedback-from-the-fse-program-march/)
that helps drive the projects’ focus and determine feature usability.

### Widgets Editor & Block Widgets 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.

The Widgets Editor project aims to bring the power of blocks to classic theme with
two major milestones:

 * Adding support for blocks in 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. areas
 * Embedding a block editor in the customizer

Once these milestones have been completed, the remaining efforts towards 5.8 focus
on providing stellar stability and backward compatibility, with an upcoming call
for testing to be launched in the near future; if this is of interest to you, please
keep an eye out for a future post on this blogblog (versus network, site). A detailed
list of the next actions can be found at the [Widgets Editor tracking issue](https://github.com/WordPress/gutenberg/issues/24687).

### Persistent List view in the post editor

The [Persistent List View](https://github.com/WordPress/gutenberg/issues/29736) 
provides an improved overview of the inserted blocks and has greatly enriched the
way users navigate the block tree in the Site Editor. Therefore, the goal is to 
[bring the Persistent List View to the post editor](https://github.com/WordPress/gutenberg/issues/29470)
as well in 5.8.

### Duotone block supports

WordPress 5.8 aims to introduce the new duotone design tool as a “block supports”
feature, available by default in the core image and cover blocks. The [PR introducing this feature](https://github.com/WordPress/gutenberg/pull/26752)
is currently in its last polishing iterations and should be expected to land in 
the plugin soon.

### Gallery block refactor

Last, but not least, work and [a round of testing](https://make.wordpress.org/core/2021/03/23/gallery-block-update-call-for-testing/)
continue on the Gallery block refactor which seeks to be a wrapper around Image 
block rather than a separate block entirely. This will allow the Gallery block to
benefit by default from all design tools and improvements made to the Image block.
Feedback collected is [addressed as part of the PR efforts](https://github.com/WordPress/gutenberg/pull/25940);
users are welcome to test and submit their feedback as early as possible so that
it can be acted upon in the upcoming weeks.

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

 [  ](https://profiles.wordpress.org/kjellr/) [Kjell Reigstad](https://profiles.wordpress.org/kjellr/)
8:30 pm _on_ April 20, 2021     
Tags: [make.wordpress.org/themes ( 26 )](https://make.wordpress.org/core/tag/make-wordpress-org-themes/),
[p2-xpost ( 213 )](https://make.wordpress.org/core/tag/p2-xpost/)   

# 󠀁[X-post: Block-based Themes Meeting Agenda: Apr 21, 2021](https://make.wordpress.org/core/2021/04/20/xpost-block-based-themes-meeting-agenda-apr-21-2021/)󠁿

X-post from [+make.wordpress.org/themes](https://make.wordpress.org/themes/): [Block-based Themes Meeting Agenda: Apr 21, 2021](https://make.wordpress.org/themes/2021/04/20/block-based-themes-meeting-agenda-apr-21-2021/)

 [  ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
10:50 pm _on_ April 19, 2021     
Tags: [5.7.1 ( 20 )](https://make.wordpress.org/core/tag/5-7-1/),
[5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)

# 󠀁[A Week in Core – April 19, 2021](https://make.wordpress.org/core/2021/04/19/a-week-in-core-april-19-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 April 12 and
April 19, 2021.

 * 26 commits
 * 22 contributors
 * 44 tickets created
 * 5 tickets reopened
 * 37 tickets closed

[WordPress 5.7.1](https://wordpress.org/news/2021/04/wordpress-5-7-1-security-and-maintenance-release/)
was released on April 14, 2021.

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=04%2F12%2F2021&daysback=7&authors=&ticket=on&sfp_email=&sfph_mail=&update=Update).
The following is a summary of commits, organized by component.

## Code changes

### Build/Test Tools

 * Make adjustments to how often old branches are tested – [#52653](https://core.trac.wordpress.org/ticket/52653)

### Bundled Themes

 * Bump versions for WordPress 5.7.1 – [#52859](https://core.trac.wordpress.org/ticket/52859)

### Coding Standards

 * Use strict comparison in `wp-admin/includes/class-wp-media-list-table.php` – 
   [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Fix WPCSWordPress Community Support A public benefit corporation and a subsidiary
   of the WordPress Foundation, [established](https://wordpressfoundation.org/news/2016/introducing-wordpress-community-support-a-public-benefit-subsidiary/)
   in 2016. issues in `wp-admin/includes/class-wp-comments-list-table.php` – [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Use strict comparison in `wp-admin/includes/class-walker-nav-menu-edit.php` –
   [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Give a variable in `WP_Automatic_Updater::after_core_update()` a more meaningful
   name – [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Use strict comparison in `wp-admin/includes/class-custom-image-header.php` – 
   [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Use strict comparison in `wp-admin/includes/class-custom-background.php` – [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Rewrite a fragment in `request_filesystem_credentials()` for clarity and to avoid
   repetition – [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Use strict comparison in `wp-admin/includes/file.php` – [#52627](https://core.trac.wordpress.org/ticket/52627)
 * Use strict comparison in `wp-admin/includes/class-wp-automatic-updater.php` –
   [#52627](https://core.trac.wordpress.org/ticket/52627)

### Documentation

 * Correct comment format in `wp-adminadmin (and super admin)/edit-tags.php`, remove
   extra space – [#46428](https://core.trac.wordpress.org/ticket/46428)

### Editor

 * Update WordPress packages to use with WordPress 5.8 – [#52991](https://core.trac.wordpress.org/ticket/52991)
 * Backportbackport A port is when code from one branch (or trunk) is merged into
   another branch or trunk. Some changes in WordPress point releases are the result
   of backporting code from trunk to the release branch. changes for WordPress packages
   added in 5.7.1 – [#52912](https://core.trac.wordpress.org/ticket/52912)
 * Blocks: Add `is_default` handling to server side 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 registry –
   [#53006](https://core.trac.wordpress.org/ticket/53006)

### External libraries

 * Include upstream GetID3 fix for PHPPHP The web scripting language in which WordPress
   is primarily architected. WordPress requires PHP 7.4 or higher 8

### Feeds

 * Rename “Summary” to “ExcerptExcerpt An excerpt is the description of the blog
   post or page that will by default show on the blog archive page, in search results(
   SERPs), and on social media. With an SEO plugin, the excerpt may also be in that
   plugin’s metabox.” in Reading Settings – [#52987](https://core.trac.wordpress.org/ticket/52987)

### Internationalization

 * Add context to strings when updating a pluginPlugin A plugin is a piece of software
   containing a group of functions that can be added to a WordPress website. They
   can extend functionality or add new features to your WordPress websites. WordPress
   plugins are written in the PHP programming language and integrate seamlessly 
   with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/)
   or can be cost-based plugin from a third-party. or theme with a ZIP package –
   [#53017](https://core.trac.wordpress.org/ticket/53017), [#52625](https://core.trac.wordpress.org/ticket/52625)

### Privacy

 * Ensure “Export Personal Data” does not generate invalidinvalid A resolution on
   the bug tracker (and generally common in software development, sometimes also
   _notabug_) that indicates the ticket is not a bug, is a support request, or is
   generally invalid. JSONJSON JSON, or JavaScript Object Notation, is a minimal,
   readable format for structuring data. It is used primarily to transmit data between
   a server and web application, as an alternative to XML. – [#52892](https://core.trac.wordpress.org/ticket/52892)

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

 * Allow authors to read their own password protected posts

### Site Health

 * Remove Ajax requests from 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. – [#49814](https://core.trac.wordpress.org/ticket/49814)
 * Correct array key for the default tab – [#47225](https://core.trac.wordpress.org/ticket/47225)
 * Support custom sub-menus and pages – [#47225](https://core.trac.wordpress.org/ticket/47225)
 * Correct test result status for the HTTPSHTTPS HTTPS is an acronym for Hyper Text
   Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over
   which data is sent between your browser and the website that you are connected
   to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications
   between your browser and the website are encrypted. This is especially helpful
   for protecting sensitive data like banking information. test – [#52783](https://core.trac.wordpress.org/ticket/52783)

### Upgrade/Install

 * Correct the alignment of error messages for the language installer – [#52989](https://core.trac.wordpress.org/ticket/52989)

## Props

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

[@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/) (3), [@mukesh27](https://profiles.wordpress.org/mukesh27/)(
3), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (3), [@jrf](https://profiles.wordpress.org/jrf/)(
2), [@xknown](https://profiles.wordpress.org/xknown/) (2), [@xavivars](https://profiles.wordpress.org/xavivars/)(
1), [@dimadin](https://profiles.wordpress.org/dimadin/) (1), [@desrosj](https://profiles.wordpress.org/desrosj/)(
1), [@TimothyBlynJacobs](https://profiles.wordpress.org/timothyblynjacobs/) (1),
[@audrasjb](https://profiles.wordpress.org/audrasjb/) (1), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/)(
1), [@immeet94](https://profiles.wordpress.org/immeet94/) (1), [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/)(
1), [@arena](https://profiles.wordpress.org/arena/) (1), [@timothyblynjacobs](https://profiles.wordpress.org/timothyblynjacobs/)(
1), [@swissspidy](https://profiles.wordpress.org/swissspidy/) (1), [@zieladam](https://profiles.wordpress.org/zieladam/)(
1), [@andraganescu](https://profiles.wordpress.org/andraganescu/) (1), [@aristath](https://profiles.wordpress.org/aristath/)(
1), [@youknowriad](https://profiles.wordpress.org/youknowriad/) (1), [@ramiy](https://profiles.wordpress.org/ramiy/)(
1), and [@ravipatel](https://profiles.wordpress.org/ravipatel/) (1).

**Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)(
11), [@desrosj](https://profiles.wordpress.org/desrosj/) (4), [@clorith](https://profiles.wordpress.org/clorith/)(
3), [@gziolo](https://profiles.wordpress.org/gziolo/) (3), [@davidbaumwald](https://profiles.wordpress.org/davidbaumwald/)(
3), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (1), and [@ocean90](https://profiles.wordpress.org/ocean90/)(
1).

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

 [  ](https://profiles.wordpress.org/ajitbohra/) [Ajit Bohra](https://profiles.wordpress.org/ajitbohra/)
8:11 pm _on_ April 19, 2021     
Tags: [core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/),
[core-editor-agenda ( 189 )](https://make.wordpress.org/core/tag/core-editor-agenda/)

# 󠀁[Editor Chat Agenda: 21 April 2021](https://make.wordpress.org/core/2021/04/19/editor-chat-agenda-21-april-2021/)󠁿

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

This is the agenda for the weekly _editor chat_ scheduled for [Wednesday, 21 April 2021, 14:00 UT](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210421T1400)
[C](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201104T1400).

This meeting is held in the #coreCore Core is the set of software required to run
WordPress. The Core Development Team builds WordPress.-editor 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/).

 * [Full Site Editing GO/NO GO](https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/)
 * [WordPress 5.8 FSE Must Have](https://github.com/WordPress/gutenberg/projects/55)
 * [Gutenberg 10.4](https://make.wordpress.org/core/2021/04/14/whats-new-in-gutenberg-10-4-14-april/)
   
   GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress.
   The editor improves the process and experience of creating new content, making
   writing rich content much simpler. It uses ‘blocks’ to add richness rather than
   shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/)
   10.5 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/41/?output_format=md#alpha-beta).
 * [Monthly Plan for April 2021](https://make.wordpress.org/core/2021/04/08/whats-next-in-gutenberg-april-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.

**Even if you can’t make the meeting, you’re encouraged to share anything relevant
for the meeting in the comments below:**

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

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

 [  ](https://profiles.wordpress.org/carike/) [Carike](https://profiles.wordpress.org/carike/)
2:08 pm _on_ April 18, 2021     
Tags: [core-privacy ( 53 )](https://make.wordpress.org/core/tag/core-privacy/)

# 󠀁[Proposal: Treat FLoC like a security concern](https://make.wordpress.org/core/2021/04/18/proposal-treat-floc-as-a-security-concern/)󠁿

Google is rolling out Federated Learning of Cohorts (FLoC) for the Chrome browser.

> TL;DR: FLoC places people in groups based on their browsing habits to target advertising.

**Why is this bad?** As the Electronic Frontier Foundation explains in their post“
[Google’s FLoC is a terrible idea](https://www.eff.org/deeplinks/2021/03/googles-floc-terrible-idea)“,
placing people in groups based on their browsing habits is likely to facilitate 
employment, housing and other types of discrimination, as well as predatory targeting
of unsophisticated consumers.
This is in addition to the privacy concerns of tracking
people and sharing their data, seemingly without informed consent – and making it
more difficult for legislators and regulators to protect people.

## So What Now?

WordPress powers approximately 41% of the web – and this community can help combat
racism, sexism, anti-LGBTQ+ discrimination and discrimination against those with
mental illness with a few lines of codeLines of Code Lines of code. This is sometimes
used as a poor metric for developer productivity, but can also have other uses.:

    ```notranslate
    function disable_floc( array $headers ) : array {
    	$permissions = [];
    	if ( ! empty( $headers['Permissions-Policy'] ) ) {
    		// Abort if cohorts has already been added.
    		if ( strpos( $headers['Permissions-Policy'], 'interest-cohort' ) !== false ) {
    			return $headers;
    		}
    		$permissions = explode( ',', $headers['Permissions-Policy'] );
    	}

    	$permissions[] = 'interest-cohort=()';
    	$headers['Permissions-Policy'] = implode( ',', $permissions );
    	return $headers;
    }
    add_filter( 'wp_headers', 'disable_floc' );
    ```

## What About Admins Who Want FLoC?

Those websites who want to opt into FLoC are likely to have the technical know-how
to simply override this proposed filterFilter Filters are one of the two types of
Hooks [https://codex.wordpress.org/Plugin_API/Hooks](https://codex.wordpress.org/Plugin_API/Hooks).
They provide a way for functions to modify data of other functions. They are the
counterpart to Actions. Unlike Actions, filters are meant to work in an isolated
manner, and should never have side effects such as affecting global variables and
output. in CoreCore Core is the set of software required to run WordPress. The Core
Development Team builds WordPress..

When balancing the stakeholder interests, the needs of website administrators who
are not even aware that this is something that they need to mitigate – and the interests
of the users and visitors to those sites, is simply more compelling.

Furthermore, for WordPress versions that support privacy settings, we can easily
add an on-off toggle to enable websites to opt in. This would only require a few
more lines of code and only a couple of new strings.

## What Do You Mean By “Treat It Like A Security Concern”?

 1. Include the patchpatch A special text file that describes changes to code, by identifying
    the files and lines which are added, removed, and altered. It may also be referred
    to as a **diff**. A patch can be _applied_ to a codebase for testing. 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., rather than waiting for the next 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.;
 2. Back-port the patch to previous versions of WordPress.

## Why Treat It That Way? Why Not Just Wait For The Next Major Release?

Well, keep your eyes peeled, because there is a ticketticket Created for both bug
reports and feature development on the bug tracker. for future releases on its way!

While it is indeed unusual to treat a new “feature” this way, there is precedent
in that something that was not strictly a security vulnerability in comments was
back-ported to previous versions for the good of the community as a whole.

Currently,[ 5.8. is only scheduled for July 2021](https://make.wordpress.org/core/5-8/).
FLoC will likely be rolling out this month.

Furthermore, a significant number of WordPress sites only update to minor versions.
By back-porting, we can protect more sites and more visitors to those sites – and
amplify the impact.

## Request For Comment

Please join the discussion below!

Whether want to show support, disagree vehemently, or just want to make the implementation
the best that it can possibly be, please have your voice be heard.

I’m aware that there is a lot of discussion on other platforms, including Twitter
on this matter, but we won’t see all of it, so in addition to spreading the conversation
there, please comment here too, so that it can be considered when this is discussed
at development meetings and when the ticket is created (consensus building first–
and that is done here 😉 )

**YOU DO NOT HAVE TO BE A DEVELOPER TO PARTICIPATE.** There will be a ticket on 
core.trac.wordpress.orgWordPress.org The community site where WordPress code is 
created and shared by the users. This is where you can download the source code 
for WordPress core, plugins and themes as well as the central location for community
conversations and organization. [https://wordpress.org/](https://wordpress.org/)
where we will discuss all of the technical stuff. I’m tremendously grateful that
there are so many developers, Core, MetaMeta Meta is a term that refers to the inside
workings of a group. For us, this is the team that works on internal WordPress sites
like WordCamp Central and Make WordPress. and others, around, but blogblog (versus
network, site) posts on make.wordpress.org are **the** places that are accessible
to techies and non-techies alike 🙂

    ```wp-block-preformatted
    Version Control:
    1. Edited to add clarification that treatment like a security concern refers to the process / procedure (accelerated development and back-porting).
    2. Code snippet updated based on suggestions below. Thank you to Tom for the snippet and to everyone who suggested conditionally appending, rather than replacing.
    Added some more info to the Request for Comment.
    ```

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

 [  ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/)
10:28 pm _on_ April 16, 2021     
Tags: [5.7.1 ( 20 )](https://make.wordpress.org/core/tag/5-7-1/),
[5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/), [dev chat ( 922 )](https://make.wordpress.org/core/tag/dev-chat/),
[summary ( 975 )](https://make.wordpress.org/core/tag/summary/)   

# 󠀁[DevChat meeting Summary – April 14, 2021](https://make.wordpress.org/core/2021/04/16/devchat-meeting-summary-april-14-2021/)󠁿

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

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

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

## Upcoming WordPress releases

### WordPress 5.7.1

Since no issue was raised after the [release candidate](https://make.wordpress.org/core/2021/04/07/wordpress-5-7-1-rc-1/),
WordPress 5.7.1 was released a few hours after the devchat. It contains 26 bugfixes
and 2 security fixes.

> [WordPress 5.7.1 Security and Maintenance Release](https://wordpress.org/news/2021/04/wordpress-5-7-1-security-and-maintenance-release/)

### WordPress 5.8

Some blogblog (versus network, site) posts were published on Make/Core:

 * [Full Site Editing Scope for WP 5.8](https://make.wordpress.org/core/2021/04/08/full-site-editing-scope-for-wp5-8/)
 * [Early test scrub for WordPress 5.8](https://make.wordpress.org/core/2021/04/12/early-test-scrub-for-wordpress-5-8-2/)
 * [Gutenberg 10.4 RC1 is available](https://github.com/WordPress/gutenberg/releases/tag/v10.4.0-rc.1)

While it happened after the meeting, it’s important to note that the [Full Site Editing Go/No Go decision was published on April 14, 2021](https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/).

[@annezazu](https://profiles.wordpress.org/annezazu/) mentioned the latest call 
for testing for the FSE Outreach Program. [This week, it’s about the Query Block](https://make.wordpress.org/test/2021/04/14/fse-program-testing-call-5-query-quest/).

## Announcements and news

 * [A Week in Core – April 12, 2021](https://make.wordpress.org/core/2021/04/12/a-week-in-core-april-12-2021/)
 * [What’s next in Gutenberg? (April 2021)](https://make.wordpress.org/core/2021/04/08/whats-next-in-gutenberg-april-2021/)
 * [Recent Build/Test Tool changes and GitHub Actions update](https://make.wordpress.org/core/2021/04/08/recent-build-test-tool-changes-and-github-actions-update/)

Please note that these posts are still waiting for feeback:

 * [Follow up to the native TypeScript proposal](https://make.wordpress.org/core/2021/04/09/follow-up-to-the-native-typescript-proposal/)
 * [Feedback | Full Site Editing in WP5.8](https://make.wordpress.org/updates/2021/04/09/feedback-full-site-editing-in-wp5-8/)

## Component maintainers updates

**General** ([@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)):
Sergey has started chipping away at some long-standing coding standards issues in
core, see ticketticket Created for both bug reports and feature development on the
bug tracker. [#52627](https://core.trac.wordpress.org/ticket/52627) for more details.

**Build/Test Tools**, **Date/Time**, **Internationalization**, **Permalinks** ([@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)):
No major news this week.

**Site Health** ([@clorith](https://profiles.wordpress.org/clorith/)): No major 
news this week.

**Menus**, **Widgets** and **Upgrade/Install** ([@audrasjb](https://profiles.wordpress.org/audrasjb/)):
No major new this week.

[@audrasjb](https://profiles.wordpress.org/audrasjb/) mentioned there are still 
many [Core components](https://make.wordpress.org/core/components/) looking for 
new maintainers:

 * Cache APIAPI An API or Application Programming Interface is a software intermediary
   that allows programs to interact with each other and share data in limited, clearly
   defined ways.
 * Database
 * ~Help/About~ ([@marybaum](https://profiles.wordpress.org/marybaum/))
 * Quick/Bulk Edit
 * Feeds
 * Filesystem API
 * Import
 * Mail
 * Plugins
 * Post, Post types
 * Login and registration

[@marybaum](https://profiles.wordpress.org/marybaum/) volunteered to maintain the
_Help/About_ component. This request was accepted by the Core team.

## Open floor

[@webcommsat](https://profiles.wordpress.org/webcommsat/) shared that lots of people
have been asking about WCEU dates (7-10 June 2021). The community team is looking
at how they promote contributing this year too. More soon.

Ticket [#53014](https://core.trac.wordpress.org/ticket/53014) was mentioned in both
5:00 UTC and 20:00 UTC devchats. It’s in milestone 5.8. It wasn’t fixed in previous
releases as it still needs a patchpatch A special text file that describes changes
to code, by identifying the files and lines which are added, removed, and altered.
It may also be referred to as a **diff**. A patch can be _applied_ to a codebase
for testing. and proper testing. 

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

 [  ](https://profiles.wordpress.org/chanthaboune/) [Josepha](https://profiles.wordpress.org/chanthaboune/)
3:39 pm _on_ April 15, 2021     
Tags: [5.8 ( 99 )](https://make.wordpress.org/core/tag/5-8/),
[core-editor ( 757 )](https://make.wordpress.org/core/tag/core-editor/)   

# 󠀁[Full Site Editing Go/No Go | April 14, 2021](https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/)󠁿

## TL;DR

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. shipped v10.4 yesterday, April 14th,
and Matías hosted the go/no go demo to review the current state of Full Site Editing
and determine what, if anything, should be included in WordPress 5.8 (July 2021),
as described in [my earlier post](https://make.wordpress.org/core/2021/04/08/full-site-editing-scope-for-wp5-8/).

The demo lasted close to 1.5 hours; it’s impressive to see how far Gutenberg has
come. It was evident in the demo how powerful Full Site Editing can be. There is
plenty to iterate upon and refine, but from a high level perspective all participants
felt this was a “go” for WP5.8. Listed below are the primary areas to focus our 
collaborative efforts on, as well as a full list of issues/questions raised in the
demo. With the cadence of Gutenberg updates there should be three major releases
of Gutenberg (10.7) before the feature freeze date for WP5.8 betaBeta A pre-release
of software that is given out to a large group of users to trial under real conditions.
Beta versions have gone through alpha testing in-house and are generally fairly 
close in look, feel and function to the final product; however, design changes often
occur as part of the process..
The changes that Phase 2 bring to WordPress are substantial,
so to avoid overwhelming users **the Global Styles interface and Site Editor (managing
all templates) will ship post-WP5.8.** This also gives more time for more theme 
authors, plugin developers, agencies, designers, site builders, and the like to 
explore and provide feedback.

### WP5.8 Go ✅

 * Improvements from Gutenberg 9.9+.
 * Introduce new blocks (Query, Site Logo, Navigation, etc).
 * `theme.json` mechanism.
 * Template Editor for Pages/Blank Template.
 * Widgets Screen & 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. widgets in 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..
 * Design tools: Duotone, Layout controls, padding, etc.

Not all of the above are currently ready but there’s some level of confidence that
they can be by the time of 5.8.

## Who Attended

 * Matt Mullenweg – Project Lead (advocating for the vision/mission of WordPress,
   and aggregate body of users)
 * Matías Ventura – Gutenberg project lead (host of the demo)
 * Helen Hou-Sandí – Lead developer (advocating for CoreCore Core is the set of 
   software required to run WordPress. The Core Development Team builds WordPress.,
   and extender community)
 * Josepha Haden Chomphosy – Executive Director (advocating for the community of
   WordPress, and aggregate body of users)
 * Héctor Prieto – Technical Project Manager (following up on technical action items)
 * Chloé Bringmann – Assisting with administrative and operational logistics

## Reflections and Action Items

_Listed below are synthesized suggestions and comments from the conversation._

### Pattern Directory

 * While the directory is not ready yet, iterations will continue. More available
   patterns will be necessary, if it is to live up to its potential.

### Query Block

 * Perhaps rename Query along the lines of, “Block List.”
 * Define the “query” of query block, and refine nomenclature for users.
 * When selecting a pattern, it’s not clear that what you see is an example and 
   that you still need to select which pattern you want. Iterate on UIUI User interface.
 * Multi-entity saving flow is not clear, as when you don’t save some entities’ 
   changes nothing tells you what happened, and unselected changes aren’t actually
   discarded, just not saved in the background.
 * Iterate on the best placement for block names.
 * The “inherit query” text is not clear, both from a technical standpoint and a
   jargon standpoint. We need to aim for the right type of verbose so that it’s 
   clear and descriptive.
 * 🚩 This is potentially too powerful for users—you can edit everything from the
   blocks in this block. _Flag was seconded._

### theme. jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML.

 * When options aren’t available in the UI because they have been disabled by the
   theme, make it clear that the options are turned off.
 * theme.json should allow a primary block to declare the styles for any nested 
   blocks (like a search block within the nav block).

### Inserter

 * The slide-in inserter makes the canvas smaller, so when adding full-page patterns
   they don’t look the same as in the preview until the inserter is closed again.
   Add the possibility for the inserter to show the patterns in the canvas in a 
   zoomed-view rather than in a responsive view.

### Navigation

 * We need more user-testing of both the Navigation Block and the Navigation Editor.
 * Move most of the block popups to the toolbar like when cropping images in the
   Image Block. E.g., links are not visible until you edit them.

### Other

 * Devise a “beta” label, perhaps “lab,” to identify new features that are stable
   might still need some polishing. The [badge can be added to blocks in the inserter](https://github.com/WordPress/gutenberg/issues/26632).
 * **Site Logo**: [Feature parity with the image block](https://github.com/WordPress/gutenberg/issues/30406),
   connect it with the site icon, better description.
 * **Site Title**: The description [should link to “Settings > General”](https://github.com/WordPress/gutenberg/issues/30871)
 * **Image Block**: [Explain why the “Alt Text” field in the sidebar is important](https://github.com/WordPress/gutenberg/issues/30872).
   The linked explanation should ideally be hosted in [wordpress.org](http://wordpress.org).
 * **Persistent List View**: [enable it in the Post Editor](https://href.li/?https://github.com/WordPress/gutenberg/issues/29470).
 * Copy refinement and opportunities for training/workshops/docs were present throughout.

## Next Steps

With this outline for the WP5.8 scope, look for a plan to prioritize and address
these issues in the coming days.

## Recording

April 14, 2021 Recording

_Thank you to [@cbringmann](https://profiles.wordpress.org/cbringmann/), [@matveb](https://profiles.wordpress.org/matveb/),
and [@priethor](https://profiles.wordpress.org/priethor/) for their work on getting
this content processed and ready to ship. _

## Transcript

 [Continue reading →](https://make.wordpress.org/core/2021/04/15/full-site-editing-go-no-go-april-14-2021/#more-88391)

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

# Post navigation

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

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