Title: 2021 – Page 21 – Make WordPress Core --- # Yearly Archives: 2021 [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 7:32 am _on_ August 18, 2021 Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [core ( 743 )](https://make.wordpress.org/core/tag/core/), [dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/) # 󠀁[Dev Chat Agenda for August 18, 2021](https://make.wordpress.org/core/2021/08/18/dev-chat-agenda-for-august-18-2021/)󠁿 Here is the agenda for this week’s developer meeting to occur at [August 18, 2021, at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210818T2000). ## Blogblog (versus network, site) Post Highlights Bringing to your attention some interesting reads and some call for feedback and/ or volunteers * [A Week in Core – August 16, 2021](https://make.wordpress.org/core/2021/08/17/a-week-in-core-august-16-2021/). Thank you [@audrasjb](https://profiles.wordpress.org/audrasjb/) for compiling this week after week. * Consistent release leadRelease Lead The community member ultimately responsible for the Release. for 5.8.x found! Thank you [@desrosj](https://profiles.wordpress.org/desrosj/) for volunteering! * [FSE Program Theme Design Survey Results](https://make.wordpress.org/test/2021/08/17/fse-program-theme-design-survey-results/)( WOW! Thank you [@annezazu](https://profiles.wordpress.org/annezazu/) for collecting a huge amount of information!) * [Preliminary Road to 5.9](https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/). Must read from [@matveb](https://profiles.wordpress.org/matveb/) * [Finalizing the native TypeScript proposal](https://make.wordpress.org/core/2021/08/11/finalizing-the-native-typescript-proposal/). Thank you [@sarayourfriend](https://profiles.wordpress.org/sarayourfriend/) for the update. ## 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 the usual agenda items above? Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly. This meeting happens in the [#core](https://wordpress.slack.com/messages/C02RQBWTW) channel. To join the meeting, you’ll need an account on the [Making WordPress Slack](https://make.wordpress.org/chat/). [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core](https://make.wordpress.org/core/tag/core/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/) [ ](https://profiles.wordpress.org/dryanpress/) [Dave Ryan](https://profiles.wordpress.org/dryanpress/) 1:04 am _on_ August 18, 2021 Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/)    # 󠀁[CSS Chat Agenda: August 19, 2021](https://make.wordpress.org/core/2021/08/18/css-chat-agenda-august-19-2021/)󠁿 The next weekly CSSCSS Cascading Style Sheets. meeting is Thursday, August 19 at 21:00PM UTC in the [#core-css](https://make.wordpress.org/core/tag/core-css/) channel [in Making WordPress Slack](https://wordpress.slack.com/archives/CQ7V4966Q). ## CSS Custom Properties (󠀁[#49930](https://core.trac.wordpress.org/ticket/49930)󠁿) Focused on substituting existing colors throughout CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. stylesheets, the CSS Custom Properties project aims to make working with Adminadmin (and super admin) Themes & Admin Color Schemes easier and more reliable both in Core and Plugins. The [#core-css](https://make.wordpress.org/core/tag/core-css/) team is [looking for contributors](https://make.wordpress.org/core/2021/08/02/call-for-css-contributors-help-implement-custom-properties-in-wp-admin/) interested in adopting a stylesheet ([a process outlined here](https://docs.google.com/document/d/1Z0Wo1W0ZQwFJYPcJ8GlsubA9uKhcFdT8ifYnso82z9I/edit)). _No prior contributing experience is required_ — we’re happy to assist anyone who would like to participate! ## Meeting Agenda * **Welcome** _(21:00PM UTC)_ * Announcements & Housekeeping * CSS Custom Properties ([#49930](https://core.trac.wordpress.org/ticket/49930)) - Overview - How to Get Involved - Status Check-In & Blockers * Open Floor * Working & Collaboration Time * Huddle Up & Closing Discussion _(21:50PM UTC)_ * **CSS Link Share** _(Bring neat examples & helpful tools!)_ [#agenda](https://make.wordpress.org/core/tag/agenda/) [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 6:57 pm _on_ August 17, 2021 Tags: [core-auto-updates ( 37 )](https://make.wordpress.org/core/tag/core-auto-updates/), [updater ( 21 )](https://make.wordpress.org/core/tag/updater/), [upgrade-install ( 32 )](https://make.wordpress.org/core/tag/upgrade-install/) # 󠀁[Upgrade/Install Meeting Notes, August 17](https://make.wordpress.org/core/2021/08/17/upgrade-install-meeting-notes-august-17/)󠁿 On August 17, the Upgrade/Install component met to discuss the [proof of concept](https://make.wordpress.org/core/2021/07/21/request-for-feedback-updater-proof-of-concept/) that builds on the rollback update failure 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 prepare it to merge in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. [Slack logs.](https://wordpress.slack.com/archives/CULBN711P/p1629219636057400) In the post and during the meetings a number of concerns and potential improvements were mentioned, so here are the next steps: 1. [@aristath](https://profiles.wordpress.org/aristath/) will write steps for manual testing, in time for the next Test scrub (Friday, August 20) ✅ Instructions in the [Pull Request](https://github.com/WordPress/wordpress-develop/pull/1492) 2. [@francina](https://profiles.wordpress.org/francina/) will liaise with the Test Team and Hosting Team (aka cross post 😇) so the PR can be tested ✅ 3. [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) will do the code review once there is a _good amount_* of testing. The conversation led to other two topics 1. Unit tests for the updater classes. They don’t exist. Should they exist? Yes. But it’s a big task and it needs a dedicated initiative. Let’s take one step at a time. 2. [#51928](https://core.trac.wordpress.org/ticket/51928) is independent from the auto-updates/failures/rollback items, but closely related. As @pbironmentioned, failure data can give information about areas in the updater that could use more error checking/recovery logic, etc. The results are anonymous and seen only by the .org system folks. If you have input on any of the above, please leave a comment – here or on the relevant PR/Tickets. Thanks! [#core-auto-updates](https://make.wordpress.org/core/tag/core-auto-updates/), [#updater](https://make.wordpress.org/core/tag/updater/), [#upgrade-install](https://make.wordpress.org/core/tag/upgrade-install/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 6:04 pm _on_ August 17, 2021 Tags: [make.wordpress.org/test ( 29 )](https://make.wordpress.org/core/tag/make-wordpress-orgtest/), [p2-xpost ( 212 )](https://make.wordpress.org/core/tag/p2-xpost/)    # 󠀁[X-post: FSE Program Theme Design Survey Results](https://make.wordpress.org/core/2021/08/17/xpost-fse-program-theme-design-survey-results/)󠁿 X-comment from [+make.wordpress.org/test](https://make.wordpress.org/test/): Comment on [FSE Program Theme Design Survey Results](https://make.wordpress.org/test/2021/08/17/fse-program-theme-design-survey-results/#comment-1894) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 6:57 am _on_ August 17, 2021 Tags: [5.8.1 ( 8 )](https://make.wordpress.org/core/tag/5-8-1/), [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [core ( 743 )](https://make.wordpress.org/core/tag/core/), [week in core ( 245 )](https://make.wordpress.org/core/tag/week-in-core/)    # 󠀁[A Week in Core – August 16, 2021](https://make.wordpress.org/core/2021/08/17/a-week-in-core-august-16-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 August 9 and August 16, 2021. * 33 commits * 31 contributors * 43 tickets created * 5 tickets reopened * 37 tickets closed Pending the appointment of the WordPress 5.9 team, a number of tickets have been fixed, waiting for the next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.(s). Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the [Trac timeline for the period above](https://core.trac.wordpress.org/timeline?from=08%2F16%2F2021&daysback=7&authors=&ticket=on&changeset=on&repo-=on&repo-design=on&repo-tests=on&sfp_email=&sfph_mail=&update=Update). The following is a summary of commits, organized by component and/or focus. ## Code changes ### Build/Test Tools * Add schema reference to PHPUnit config files – [#53363](https://core.trac.wordpress.org/ticket/53363) * Declare two TestCase classes as abstract – [#53363](https://core.trac.wordpress.org/ticket/53363) * Enable running the tests on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.1 – [#53891](https://core.trac.wordpress.org/ticket/53891), [#53635](https://core.trac.wordpress.org/ticket/53635) * Hard deprecate `WP_UnitTestCase_Base::checkRequirements()` – [#46149](https://core.trac.wordpress.org/ticket/46149) * Hard deprecate `WP_UnitTestCase_Base::checkRequirements()` – [#46149](https://core.trac.wordpress.org/ticket/46149) * Make the polyfills loading more flexible – [#46149](https://core.trac.wordpress.org/ticket/46149) * Remove Unicode character from PHPUnit version check message – [#53363](https://core.trac.wordpress.org/ticket/53363) * Revert [51602] for now to investigate test failures on PHPUnit < 7.0 – [#46149](https://core.trac.wordpress.org/ticket/46149) * Simplify the PHPUnit test workflow – [#53891](https://core.trac.wordpress.org/ticket/53891) * Add unit tests for the `wp_nonce_ays()` function – [#53882](https://core.trac.wordpress.org/ticket/53882) * Fix failing i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/2021/page/21/?output_format=md#l10n). Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. unit tests for 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. metadata– Follow up for [#53238](https://core.trac.wordpress.org/ticket/53238) * Rename classes in `phpunit/tests/formatting/` per the naming conventions – [#53363](https://core.trac.wordpress.org/ticket/53363) * Use correct comparison in `do_enclose()` tests – [#53635](https://core.trac.wordpress.org/ticket/53635) ### Code Modernization * Check the return type of `_get_cron_array()` in `wp_schedule_event()` – [#53635](https://core.trac.wordpress.org/ticket/53635) * Check the return type of `parse_url()` in `WP::parse_request()` – [#53635](https://core.trac.wordpress.org/ticket/53635) * Correct handling of `null` in `wp_parse_str()` – [#53635](https://core.trac.wordpress.org/ticket/53635) * Rename the `readonly()` function to `wp_readonly()` – [#53858](https://core.trac.wordpress.org/ticket/53858) * Replace `strftime()` and `gmstrftime()` usage in unit tests – [#53897](https://core.trac.wordpress.org/ticket/53897) * Silence the deprecation warning for missing return type in `phpunit/tests/compat. php` – [#53635](https://core.trac.wordpress.org/ticket/53635) ### Documentation * Add a `@see` reference to the `wp_mail_content_type` 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 `wp_staticize_emoji_for_email()` – [#53399](https://core.trac.wordpress.org/ticket/53399) * Add a `@see` reference to the `xmlrpc_enabled` filter in `wp_xmlrpc_server::set_is_enabled()`– [#53399](https://core.trac.wordpress.org/ticket/53399) * Correct `@since` version for the `wp_parse_str` filter – [#53399](https://core.trac.wordpress.org/ticket/53399) * Fix typo in the `get_block_editor_settings()` description – [#53922](https://core.trac.wordpress.org/ticket/53922) * Improve documentation for a few functions per the documentation standards – [#53399](https://core.trac.wordpress.org/ticket/53399) * Synchronize documentation for `wp_get_attachment_image_attributes` filter callbacks in bundled themes – [#53878](https://core.trac.wordpress.org/ticket/53878) ### Editor * Preserve the original template keys when preparing a list of page templates – [#53898](https://core.trac.wordpress.org/ticket/53898) * Add support for `variations` in `block.json` file – [#53238](https://core.trac.wordpress.org/ticket/53238) ### General * Restore (un-deprecate) the `sanitize_url()` function – [#53876](https://core.trac.wordpress.org/ticket/53876) ### Themes * Make sure the theme 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. response is not an error before operating on it in `themes_api()` – [#53913](https://core.trac.wordpress.org/ticket/53913) * Twenty Seventeen: Add support for `wa.me` links in Social Links menu – [#51946](https://core.trac.wordpress.org/ticket/51946) * Twenty Twenty: Add support for `wa.me` links in Social menu – [#50542](https://core.trac.wordpress.org/ticket/50542) ### Upgrade/Install * Update sodium_compat to v1.17.0 – [#53907](https://core.trac.wordpress.org/ticket/53907) * Use consistent capitalization for “web host” in setup messages – [#53926](https://core.trac.wordpress.org/ticket/53926) ## Props **Thanks to the 31 people who contributed to WordPress Core on Trac last week:** [@jrf](https://profiles.wordpress.org/jrf/) (17), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 7), [@swissspidy](https://profiles.wordpress.org/swissspidy/) (4), [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/)( 4), [@pbearne](https://profiles.wordpress.org/pbearne/) (3), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/)( 3), [@mukesh27](https://profiles.wordpress.org/mukesh27/) (3), [@lucatume](https://profiles.wordpress.org/lucatume/)( 2), [@Ipstenu](https://profiles.wordpress.org/ipstenu/) (1), [@thomasplevy](https://profiles.wordpress.org/thomasplevy/)( 1), [@Toro_Unit](https://profiles.wordpress.org/toro_unit/) (1), [@aadilali](https://profiles.wordpress.org/aadilali/)( 1), [@Mamaduka](https://profiles.wordpress.org/mamaduka/) (1), [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)( 1), [@youknowriad](https://profiles.wordpress.org/youknowriad/) (1), [@ayeshrajans](https://profiles.wordpress.org/ayeshrajans/)( 1), [@haosun](https://profiles.wordpress.org/haosun/) (1), [@jeherve](https://profiles.wordpress.org/jeherve/)( 1), [@desrosj](https://profiles.wordpress.org/desrosj/) (1), [@schlessera](https://profiles.wordpress.org/schlessera/)( 1), [@gwwar](https://profiles.wordpress.org/gwwar/) (1), [@pierlo](https://profiles.wordpress.org/pierlo/)( 1), [@ankitmaru](https://profiles.wordpress.org/ankitmaru/) (1), [@bradparbs](https://profiles.wordpress.org/bradparbs/)( 1), [@tmatsuur](https://profiles.wordpress.org/tmatsuur/) (1), [@dkarfa](https://profiles.wordpress.org/dkarfa/)( 1), [@carepsules](https://profiles.wordpress.org/carepsules/) (1), [@macmanx](https://profiles.wordpress.org/macmanx/)( 1), [@pedromendonca](https://profiles.wordpress.org/pedromendonca/) (1), [@iluy](https://profiles.wordpress.org/iluy/)( 1), and [@knutsp](https://profiles.wordpress.org/knutsp/) (1). **Congrats and welcome to our 3 new contributors of the week! **[@aadilali](https://profiles.wordpress.org/aadilali/), [@carepsules](https://profiles.wordpress.org/carepsules/), and [@iluy](https://profiles.wordpress.org/iluy/) ♥️ **Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 31), and [@gziolo](https://profiles.wordpress.org/gziolo/) (2). [#5-8-1](https://make.wordpress.org/core/tag/5-8-1/), [#5-9](https://make.wordpress.org/core/tag/5-9/), [#core](https://make.wordpress.org/core/tag/core/), [#week-in-core](https://make.wordpress.org/core/tag/week-in-core/) [ ](https://profiles.wordpress.org/francina/) [Francesca Marano](https://profiles.wordpress.org/francina/) 8:53 am _on_ August 16, 2021 Tags: [core-auto-updates ( 37 )](https://make.wordpress.org/core/tag/core-auto-updates/), [updater ( 21 )](https://make.wordpress.org/core/tag/updater/), [upgrade-install ( 32 )](https://make.wordpress.org/core/tag/upgrade-install/) # 󠀁[Upgrade/Install component meeting agenda for August 17, 2021](https://make.wordpress.org/core/2021/08/16/upgrade-install-component-meeting-agenda-for-august-17-2021/)󠁿 The next meeting is scheduled on [Tuesday, August 17, 2021, at 17:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210817T1700) and will take place on [#core-auto-updates](https://wordpress.slack.com/archives/CULBN711P/p1583863308013300) SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) channel. The aim of the chat is to check the status of the [rollback for failed plugin/theme updates](https://core.trac.wordpress.org/ticket/51857) and decide if it is ready for a merge proposal. Got something to propose for the agenda? Please leave a comment below. [#core-auto-updates](https://make.wordpress.org/core/tag/core-auto-updates/), [#updater](https://make.wordpress.org/core/tag/updater/), [#upgrade-install](https://make.wordpress.org/core/tag/upgrade-install/) [ ](https://profiles.wordpress.org/matveb/) [Matias Ventura](https://profiles.wordpress.org/matveb/) 4:50 pm _on_ August 13, 2021 Tags: [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/)    # 󠀁[Preliminary Road to 5.9](https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/)󠁿 This is a quick overview of the main areas and features currently underway for 5.9 in GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/). Some are in more advanced stages than others, but together they paint a picture of what we are looking forwards to. To dive deeper into concrete tasks and areas of work, [this tracking issue](https://github.com/WordPress/gutenberg/issues/33094) is the best place to follow. ## Blocks + intrinsic web design [⌊Collection of various patterns displayed at mobile resolutions.⌉⌊Collection of various patterns displayed at mobile resolutions.⌉[ * One of the biggest points of friction for pattern and theme builders are the lack of responsive tools available at a 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. level. This needs to be solved in a way that doesn’t disproportionally increase interface complexity. * The block model is a good case to apply some _intrinsic design_ principles, since a block can occupy a place in many different layouts and containers, for which prescriptive media queries that don’t take context into account are inflexible. * Each block area should be intrinsically responsive allowing blocks to compose together, wrap, stack, and organize themselves to fit the different spaces and screens. For this to work well, container blocks need to absorb more layout controls.( Container queries might help expand this further in the future.) * Typography tools need to become more fluid and internally support algorithmic clamping. Whenever possible, patterns should _just work_ and accommodate themselves. ## Patterns [⌊Mosaic galleries showing different design patterns.⌉⌊Mosaic galleries showing different design patterns.⌉[ * With the initial rollout of the [new directory](https://wordpress.org/patterns/) there’s a growing need to expand the inserter integration to accommodate broader categories of patterns and the experience of browsing them. * There’s more work to be done within the setup flow of single and multi-block selections. This also includes improving the mechanisms for transforming _to_ and _from_ patterns, which are still nascent. * Creation flows with patterns also need expanding from template parts and blocks to pages and templates. ## Navigation Menus * The navigation block and navigation screen projects have been underway for quite some time and are a main target for 5.9. With the principal tracking issue [about to be completed](https://github.com/WordPress/gutenberg/issues/27593), a large part of the remaining work is to improve the user experience, reduce complexity, and test as much as possible on themes. ## An interface for 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.. [⌊Global Styles panel showing the main area and the background color section.⌉⌊Global Styles panel showing the main area and the background color section.⌉[ * 5.8 introduced the scaffolding necessary for themes to take the reins over how various aspects of blocks render and how the interface is controlled. The natural next step ahead is to develop the user interface that will allow users to interact with these style properties. This goes by the project name “global styles” and an updated design is currently in prototype stage. * It should be appreciated how important it is to leverage the global reach of CSSCSS Cascading Style Sheets. rules as we combine it with the power of blocks. The current structure deals with two large groups of design targets: blocks and elements. Elements represent things that can be styled globally and across blocks( such as “text”, “links”, “captions”, etc). ## Design Tools: Colors, Typography, Spacing, Layout [⌊Series of panels showing different configurations of the typography tools.⌉⌊Series of panels showing different configurations of the typography tools.⌉[ * The effort to bring better and more consistent design tools continues to progress. These tools need to integrate smoothly with both the block 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. (through the“ supports” mechanism) and theme.json. One of the main goals is consistent access to similar tools across blocks, including third-party ones. * Running parallel to this effort comes the work on the WordPress components system, refinements to color tools, interactivity, accessibilityAccessibility Accessibility( commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility), etc. ## Formalize editing flows for block themes [⌊Displays templates as small cards in a mosaic, connecting diagrams with the different flows.⌉⌊Displays templates as small cards in a mosaic, connecting diagrams with the different flows.⌉[ * A large percentage of the infrastructure and features needed to build block themes are established. The UXUX User experience and design needs the most attention, though, starting by mapping into a clearer information architecture all the possible flows that are to be supported (editing templates, parts, styles, pages, etc). * Continue to process and take into the design process all the feedback gathered from users and theme builders. * Begin defining transition flows from existing 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 to block areas when appropriate, and explore the various aspects of theme switching. * Finalize and commit all remaining blocks under the “theme” categoryCategory The' category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.. [#5-9](https://make.wordpress.org/core/tag/5-9/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/) [ ](https://profiles.wordpress.org/notlaura/) [Lara Schenck](https://profiles.wordpress.org/notlaura/) 3:36 pm _on_ August 12, 2021 Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/)    # 󠀁[CSS Chat Agenda: August 12, 2021](https://make.wordpress.org/core/2021/08/12/css-chat-agenda-august-12-2021/)󠁿 This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday August 21 at 21:00PM UTC. The meeting will be held in the [#core-css](https://make.wordpress.org/core/tag/core-css/) channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/). This week, we will be continuing with a supported working session for new contributors! Please see this post with our [call for contributors](https://make.wordpress.org/core/2021/08/02/call-for-css-contributors-help-implement-custom-properties-in-wp-admin/) and more details. Our agenda is as follows: * Welcome * Housekeeping * Discussion around the CSS Custom Properties project ([#49930](https://core.trac.wordpress.org/ticket/49930)) - Brief Overview - How to Get Involved * Open Floor * Working Time * 21:50PM UTC – Circle back, closing discussion, 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/get_dave/) [David Smith](https://profiles.wordpress.org/get_dave/) 11:06 am _on_ August 12, 2021 Tags: [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-summary ( 185 )](https://make.wordpress.org/core/tag/core-editor-summary/), [meeting notes ( 227 )](https://make.wordpress.org/core/tag/meeting-notes/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/) # 󠀁[Editor chat summary: 11th August 2021](https://make.wordpress.org/core/2021/08/12/editor-chat-summary-11th-august-2021/)󠁿 This post summarises the weekly editor chat meeting ([agenda here](https://make.wordpress.org/core/2021/08/10/editor-chat-agenda-11-august-2021/)) held on [2021-08-11 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210811T1400) in [Slack](https://wordpress.slack.com/archives/C02QB2JS7/p1628690404002200). Moderated by [@get_dave](https://profiles.wordpress.org/get_dave/profile/). ## 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 * [Gutenberg 11.2.1](https://github.com/WordPress/gutenberg/releases/tag/v11.2.1) which was released and contained [a fix for available alignments and layout for the post editor](https://github.com/WordPress/gutenberg/pull/33894). * [RC for 11.3.0 is available](https://github.com/WordPress/gutenberg/releases/tag/v11.3.0-rc.1). ## Whats next in Gutenberg: July and August * Most of the content from [Whats next in Gutenberg: July and August](https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/) had been covered in [the last Core Editor chat](https://make.wordpress.org/core/2021/08/05/editor-chat-summary-wednesday-4-august-2021/). * [@get_dave](https://profiles.wordpress.org/get_dave/) reminded folks that [the above](https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/) [ ](https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/) [post](https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/) has some great links to the **“Tracking Issues”** for each focus. It’s worth keeping an eye on the one’s you are interested in as they are canonical and a useful point of reference. * [@annezazu](https://profiles.wordpress.org/annezazu/) reminded us that there’s this [new template part focus mode overview issue](https://github.com/WordPress/gutenberg/issues/33926) that is now included in the overall site editing projects scope. ## Updates based on the scope for Site Editing projects Updates were requested for the key projects: ### Navigation 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. [@mkaz](https://profiles.wordpress.org/mkaz/) provided an update: * Small refinements still underway. * [@annezazu](https://profiles.wordpress.org/annezazu/) has posted [a call for testing that heavily focuses on using the Navigation Block](https://make.wordpress.org/test/2021/08/11/fse-program-testing-call-9-handling-highered-headers/) in various ways. ### Navigation Editor screen [@get_dave](https://profiles.wordpress.org/get_dave/) provided the update: * Work has continued on bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes and stability. * Now looking to define what is required to bring the Nav Editor out of “experimental”. * To this end, the team is looking to arrange a hallway hangout (or similarly public forum) to compare/contrast the classic navigation screen with the block-based navigation screen. * We’re also looking to 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. out or break down any “Epic” Issues from [the Nav Editor tracking issue](https://github.com/WordPress/gutenberg/issues/29102) into more actionable tasks (where possible). * [@javiarce](https://profiles.wordpress.org/javiarce/) has also been looking into and documenting the need to add some “polish” to the Nav Editor screen in order that UXUX User experience bugs/issues don’t spoil the overall experience. I believe he will look to add these as Bugs to the repo soon. * From this we will then look to reprioritise the task list in this tracking Issue around achieving feature parity at a user interface level (developer APIs will follow). ### Block 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 and 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.. [@get_dave](https://profiles.wordpress.org/get_dave/) provided the update: * There’s currently a major discussion around [how best to emulate the markup pattern of “Widget Title” + “Widget” which is how most Themes expect Widget HTML to be structured](https://github.com/WordPress/gutenberg/issues/32723#issuecomment-895265774). * Currently options are: a Block Pattern and a new “Widget Box” block (update: now renamed to “Widget Group”). * Seems simple but honestly it isn’t. Any feedback appreciated. * Also continuing with general bug fixes and stability improvements.  ### Native Mobile Team [@mattchowning](https://profiles.wordpress.org/mattchowning/) provided the update: _Shipped_ * Added Android support for themes that use Global Styles _Added:_ * [A guide for writing native mobile integration tests](https://github.com/WordPress/gutenberg/blob/99179203bf5eb16b2f71feadd3fe184a5d147504/docs/contributors/code/native-mobile-integration-test-guide.md) _In Progress_: * Block Picker Search is _almost_ ready to ship. * Embed block. * Editor onboarding help section. * GSS Font size. * line height. * colors. ### Styles, Patterns and Template Editor At the time of the meeting no updates were provided. If you are a contributor, please do leave an update in the comments below. (_Aside_: [see `Open Floor` section below](https://make.wordpress.org/core/2021/page/21/?output_format=md#proposal-key-project-updates) where we discussed how to avoid situations where there are no updates for key projects during the meeting). ## Bonus: impromptu discussion on “Full Page Patterns” This item was not on the agenda, but it’s worth including here because some good points were raised about the value of this proposal. * [@paaljoachim](https://profiles.wordpress.org/paaljoachim/) resurfaced the idea of full page patterns as an alternative to creating a page template. * There is [a proposal to add Full Page Patterns to Core](https://github.com/WordPress/gutenberg/issues/18055) which looks to have stalled. * One could tell the user to add a full page pattern instead of a reusable block that needs to first be converted back to regular blocks before being filled out. * Adding patterns is an accident proof way of not affecting any other pages.  * [@mkaz](https://profiles.wordpress.org/mkaz/) noted that this feature will work now – there is no limit to what can be put into a pattern. * [@get_dave](https://profiles.wordpress.org/get_dave/) noted the key difference between Full Page Patterns and Templates is that inserting a pattern is a one time operation – once inserted it will receive no further updates should the pattern be amended in future. * [@digamberpradhan](https://profiles.wordpress.org/digamberpradhan/) and Frank Wazeter were both in favour and could see the value of full page patterns as a discreet concept. ## Task Coordination **[@paaljoachim](https://profiles.wordpress.org/paaljoachim/):** * Highlighting [efforts to make Reusable blocks inherit alignment](https://github.com/WordPress/gutenberg/pull/31082)( also related to [Shortcode block issue](https://github.com/WordPress/gutenberg/issues/33886)). * Hightlighting [Breadcrumbs block draft PR](https://github.com/WordPress/gutenberg/pull/32500). **[@annezazu](https://profiles.wordpress.org/annezazu/):** * Main focuses this week are: - starting to [recap the block theme survey](https://make.wordpress.org/test/2021/07/30/help-shape-the-future-of-theme-design/)( responses due by Friday!). - shipping the call for testing today (included lots of testing). - responding to feedback as responses roll in. * I hope to have time to do triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. once more, focused again on labelling PRs to make releases a bit easier. **[@get_dave](https://profiles.wordpress.org/get_dave/):** * I’ve been working primarily on trying to resolve [the issue I mentioned early regarding the legacy Widget markup pattern](https://github.com/WordPress/gutenberg/issues/32723#issuecomment-897468866). * I’ve also been doing [_planning_ around the Nav Editor and what the next steps are](https://github.com/WordPress/gutenberg/issues/29102#issuecomment-896818791). As I mentioned a Hallway hangout will probably happen soon. I’ll post the info in advance and it would be great to see folk join to discuss how we can evolve this project. * Working with [@joen](https://wordpress.slack.com/team/U03KRCH0Z) on [a Split control for URL and Text within Link UI](https://github.com/WordPress/gutenberg/pull/33849) which should make it easier to add/modify links. * Tinkering with [making Reusable blocks inherit alignment of their internal blocks](https://github.com/WordPress/gutenberg/pull/31082). Turns out the issue is _very_ much more complicated than I’d first thought (who knew!?). * Trying to fix [a paste bug on Windows](https://github.com/WordPress/gutenberg/pull/33607/)– should be ready to land soon. ## Open Floor ### Proposal for improving the “Key project updates” section of editor chat meetings * [@priethor](https://profiles.wordpress.org/priethor/) has [a proposal for improving the project updates](https://make.wordpress.org/core/2021/08/10/editor-chat-agenda-11-august-2021/#comment-41693). * At the start of each week (or prior to editor chat) let’s ask contributors to leave an update comment on the tracking Issue (these are listed in [the recent What’s Next post](https://make.wordpress.org/core/2021/07/21/whats-next-in-gutenberg-site-editing-status-check-late-july-august-2021/)). * Will help the chat facilitator keep the pace of the chat when it’s quiet. * Will also help ensure we don’t end up with a “no updates” situation (see above). * [@get_dave](https://profiles.wordpress.org/get_dave/) has an [example update for the Nav Editor](https://github.com/WordPress/gutenberg/issues/29102#issuecomment-896818791) which serves as a basic template. * Kudos to [@nosolosw](https://profiles.wordpress.org/nosolosw/) who started doing this for the Global Styles project. * Most attendees agreed this would be a nice improvement – let’s include a prompt in the next agenda [@itsjusteileen](https://profiles.wordpress.org/itsjusteileen/). ### Usability feedback on the Template settings panel in Block Editor * [Frank Wazeter raised some feedback](https://wordpress.slack.com/archives/C02QB2JS7/p1628693740072300) about the [Template settings panel](https://github.com/WordPress/gutenberg/issues/34015). * When you click on “new”, the default thought is to do something akin to “create new from default template,” especially because the dropdown above has “default” selected. * However, what you get is whatever’s set in ‘defaultBlockTemplates’, which for the vast majority, isn’t anything explicitly set. * Likewise, if I select another template, my initial assumption is I’m making “ New from…” whatever template I set. * It might make more sense if there was a toggle – similar to in background color for “Color” or “Gradient” to indicate that I’m making a brand new blank template. * [@get_dave](https://profiles.wordpress.org/get_dave/) advised creating and Issue and [Frank did so after the meeting](https://github.com/WordPress/gutenberg/issues/34015). ## Wrap up Thanks to everyone who attended the meeting! [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/), [#meeting-notes](https://make.wordpress.org/core/tag/meeting-notes/), [#summary](https://make.wordpress.org/core/tag/summary/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 10:04 pm _on_ August 11, 2021 Tags: [core-css ( 191 )](https://make.wordpress.org/core/tag/core-css/), [core-site-health ( 3 )](https://make.wordpress.org/core/tag/core-site-health/), [core-test ( 12 )](https://make.wordpress.org/core/tag/core-test/), [dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/)    # 󠀁[Dev chat summary, August 11, 2021](https://make.wordpress.org/core/2021/08/11/dev-chat-summary-august-11-2021/)󠁿 [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) stepped up to lead [this agenda-less meeting](https://wordpress.slack.com/archives/C02RQBWTW/p1628712444279300). Big thank you! ## Highlighted blogblog (versus network, site) posts **From @audrasjb, another [A Week in Core](https://make.wordpress.org/core/2021/08/09/a-week-in-core-august-9-2021/) post** highlights the moving parts of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and recognizes a week’s worth of contributors at a time. **From [@sarayourfriend](https://profiles.wordpress.org/sarayourfriend/) provides an update on the [native TypeScript proposal](https://make.wordpress.org/core/2021/08/11/finalizing-the-native-typescript-proposal/)** announcing that 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/) project supports native TypeScript. **From [@notlaura](https://profiles.wordpress.org/notlaura/)** **comes a [Call for CSS Contributors](https://make.wordpress.org/core/2021/08/02/call-for-css-contributors-help-implement-custom-properties-in-wp-admin/)**, a carryover and reminder from last week. Their next weekly work session is August 12, 2021 at 21:00 UTC in [#core-css](https://make.wordpress.org/core/tag/core-css/). **From [@chanthaboune](https://profiles.wordpress.org/chanthaboune/), participate in the [WordPress 5.8 ‘Tatum’ Retrospective](https://make.wordpress.org/core/2021/07/28/wordpress-5-8-tatum-retrospective/).** Feedback is due on August 15th and is greatly appreciated to make future releases even better. **From [@webcommsat](https://profiles.wordpress.org/webcommsat/) comes a [helpful post for spreading the word about 5.8](https://make.wordpress.org/marketing/2021/08/11/share-about-wordpress-5-8-on-social-media/).** In this post, you will find [social posts](https://make.wordpress.org/marketing/2021/08/11/share-about-wordpress-5-8-on-social-media/#socialposts) you can share and adapt on Twitter and Facebook. **From [@annezazu](https://profiles.wordpress.org/annezazu/)**, **[follow the latest call for testing](https://make.wordpress.org/test/2021/08/11/fse-program-testing-call-9-handling-highered-headers/) through the FSE Outreach Program. **It’s focused on using the navigation 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. to build out a HigherEd themed headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. with three weeks to share you feedback. **From [@annezazu](https://profiles.wordpress.org/annezazu/) comes a reminder to [help shape the future of theme design](https://make.wordpress.org/test/2021/07/30/help-shape-the-future-of-theme-design/).** If you’re a block theme author or have explored that space, please share your responses by August 15th and know they are each greatly appreciated.  Finally, catch up with the previous episodes of [WP Briefing](https://wordpress.org/news/podcast/). The podcast will return in September! ## Component maintainers **Reporting in on Build/Test tools, **[@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) shared that, as of last weekend, WordPress test suite is compatible with PHPUnit 8 & 9, and runs tests on PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher 8.1 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. (scheduled for release in November). Props to [@jrf](https://profiles.wordpress.org/jrf/) and [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) for all the fixes and improvements that made it possible!  See ticketticket Created for both bug reports and feature development on the bug tracker. [#46149](https://core.trac.wordpress.org/ticket/46149) for more details. **Reporting on Date/Time, I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see [localization](https://make.wordpress.org/core/2021/page/21/?output_format=md#l10n). Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill., Permalinks**, [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) said that there’s no major news this week. **Reporting on General,** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) shared that work has started on making various compatibility fixes for PHP 8.1. Thanks [@jrf](https://profiles.wordpress.org/jrf/), again!  See ticket [#53635](https://core.trac.wordpress.org/ticket/53635) for more details. ## Open Floor Considering [#49728](https://core.trac.wordpress.org/ticket/49728) for the 5.9 release. Raised by [@hareesh-pillai](https://profiles.wordpress.org/hareesh-pillai/). Since the topic of compatibility with the latest PHP versions came up, Hareesh flagged that it would make sense to include this additional ticket after it was pushed from 5.6. Next step: [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) moved it to the 5.9 milestone. Invitation to contribute to testing. Raised by [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/). Anyone interested in contributing to testing including attempting to reproduce problems, gathering testing information (such as testing steps, acceptance criteria, dependencies), user testing, and automated testing, you’re invited to join us in #core-test channel. Checking in on a dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include a description of the change, the decision that led to this change, and a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. related to 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. folks finding issues with PHPUnit updates. Raised by [@jeffpaul](https://profiles.wordpress.org/jeffpaul/). [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) and [@jrf](https://profiles.wordpress.org/jrf/) quickly chimed in to say that a dev note is in progress with an ideal publish date of next week. The quick TL;DR is: * Fixture methods changed in the WP test cases, i.e. changed to snake_case * Wrappers for the snake_case will be backported for extenders who are testing against versions other than 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.. * Once those backports happen, then the fixture methods in your tests need to be updated for testing against trunk. To help extenders, command-line messages will be added as well to alert and guide devs. Bumping the ACCEPTABLE_PHP and SUPPORTED_PHP versions in light of PHP 7.3 support ending in 3 months. Raised by [@hareesh-pillai](https://profiles.wordpress.org/hareesh-pillai/). [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) recommended that this be raised as a discussion topic in the next #core-site-health meeting. He also shared that he felt it was a bit too early to bump the recommended version to PHP 8.0, as there is still ongoing work to make it more compatible. [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/) # Post navigation [← Older posts](https://make.wordpress.org/core/2021/page/22/?output_format=md) [Newer posts →](https://make.wordpress.org/core/2021/page/20/?output_format=md)