Title: 2021 – Page 12 – Make WordPress Core --- # Yearly Archives: 2021 [ ](https://profiles.wordpress.org/talldanwp/) [Daniel Richards](https://profiles.wordpress.org/talldanwp/) 10:09 am _on_ October 15, 2021   # 󠀁[Summary: Navigation Editor and Block hallway hangout](https://make.wordpress.org/core/2021/10/15/summary-navigation-editor-and-block-hallway-hangout/)󠁿 On [October 13, 2021, 10:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211013T1000) a hallway hangout was held to discuss the future of the Navigation Editor and 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.. [See here for the full agenda.](https://make.wordpress.org/core/2021/10/11/navigation-editor-and-block-hallway-hangout/) The meeting was convened to discuss some of the challenges contributors have been facing. Those challenges can probably be best dissected into two parts: 1. What important changes to the Navigation Block need to be made for full site editing? 2. What is the best path forwards for the Navigation Editor given the proposed changes to the block? ## Meeting recording Here’s a recording for the full meeting. The recording starts halfway through the introductions and didn’t capture the intros for myself ([@talldanwp](https://profiles.wordpress.org/talldanwp/)), Tammie ([@karmatosed](https://profiles.wordpress.org/karmatosed/)), Joen ([@joen](https://profiles.wordpress.org/joen/)) or Emmanuel ([@manooweb](https://profiles.wordpress.org/manooweb/)). ## Topics The meeting was quite a deep dive into the Navigation Block and Editor, exploring concepts like: * How the Navigation Editor and Block development has diverged * Upcoming priorities for the Navigation Block and Editor * Upcoming improvements to the Navigation Block. Largely centered around the block saving data like a Template Part or Reusable block does (described 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/) issue [#34612](https://github.com/WordPress/gutenberg/issues/34612)) - There has already been some work on using a Template Part post type for this( pull request [#35418](https://github.com/WordPress/gutenberg/pull/35418)) - Some exploration should happen around alternatives – a new post type or using the menu term’s description field - The actual data structure that is saved needs consideration and exploration * Migrating menu data when a user switches theme (e.g. to a block-based theme or between block-based themes) * Backwards compatibility with the current menu system - The shortcomings of the current menu / menu item data structure, the overhead and performance of this system - The current menu and menu item being the best way to achieve full backwards compatibility in the Navigation Editor - MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. paths for extensibility * The navigation block supporting different designs and styles * Some analysis of products and plugins that handle menus ## Outcomes The main outcome was to focus in the short-term on the Navigation Block for WordPress 5.9. (as an addendum to what was discussed in the meeting, this can be tracked via the Twenty Twenty-Two tracking issue ([#75](https://github.com/WordPress/twentytwentytwo/issues/75)), and in the Navigation Block tracking issue ([#35521](https://github.com/WordPress/gutenberg/issues/35521))). As the Navigation Block develops it will be possible to explore ways that it might work better within the Navigation Editor. ## Immediate tasks * Publish a clearer set of goals for the Navigation Editor and Block. * Ensure the tracking issues are up-to-date. [ ](https://profiles.wordpress.org/zieladam/) [Adam Zieliński](https://profiles.wordpress.org/zieladam/) 1:56 pm _on_ October 14, 2021 Tags: [block-editor ( 139 )](https://make.wordpress.org/core/tag/block-editor/), [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [gutenberg ( 546 )](https://make.wordpress.org/core/tag/gutenberg/), [gutenberg-new ( 216 )](https://make.wordpress.org/core/tag/gutenberg-new/)    # 󠀁[What’s new in Gutenberg 11.7 (October 13th)](https://make.wordpress.org/core/2021/10/14/whats-new-in-gutenberg-11-7-october-13th/)󠁿 GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) 11.7 has been released! This release includes a number of nice enhancements and as usual many bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes. ### **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. And Navigation Editor Advances** The [Lighter Navigation Block Experience](https://github.com/WordPress/gutenberg/issues/34041) and the [Navigation Editor](https://github.com/WordPress/gutenberg/issues/29102) efforts led to many quality of life improvements in Gutenberg 11.7!  [[ The Navigation Block underwent a series of changes intended to provide a more intuitive navigation management experience. New links are now [added instantly after clicking the “+” icon](https://github.com/WordPress/gutenberg/pull/34899) without an additional block selection step. There is also an additional new way of adding links: using a [slash inserter](https://github.com/WordPress/gutenberg/pull/35196). It is worth noting that a slash inserter can be enabled for any block using a new, experimental flag called __experimentalSlashInserter. In addition, navigation links [may now be transformed](https://github.com/WordPress/gutenberg/pull/34978) into other allowed block types, such as Site Logo, Home Link, or Social Icons. Finally, it’s easier for users to notice linking mistakes thanks to [the squiggly line](https://github.com/WordPress/gutenberg/pull/35139) highlighting empty links similarly to grammar errors.  On the frontend front: The navigation link now [supports custom font size and line-height](https://github.com/WordPress/gutenberg/pull/35324). Link labels, such as “Previous post,” may now be a [part of the link to the post itself](https://github.com/WordPress/gutenberg/pull/34952). Mobile menus now [reflect the justification settings](https://github.com/WordPress/gutenberg/pull/35077) of the desktop menus.  ### **Global Styles And Full Site Editing** The site editing experience got polished in this recent release. The template part editor gained a [convenient back button](https://github.com/WordPress/gutenberg/pull/34732) to ease returning to the site editor. Switching between editing different template parts was made more accessible by listing the available areas in [template details](https://github.com/WordPress/gutenberg/pull/35202). Also, the custom [gradient picker was refreshed](https://github.com/WordPress/gutenberg/pull/34712). [[ [[ [[ There’s more! The Site editor was equipped with [padding settings for specific template parts](https://github.com/WordPress/gutenberg/pull/35241). Color palette settings are now available in a [separate panel in the global styles sidebar](https://github.com/WordPress/gutenberg/pull/35109). In addition, Duotone support was extended to the [site logo block](https://github.com/WordPress/gutenberg/pull/35344). [[ While we’re talking about Duotone, Gutenberg 11.7 enables theme authors to customize the default Duotone 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. using [theme.json styles](https://github.com/WordPress/gutenberg/pull/34667): ```notranslate { "styles": { "blocks": { "core/site-logo": { "filter": { "duotone": "var(--wp--preset--duotone--blue-filter)" } } } } } ``` ### **Columns Block Support For Tweaking The Gaps And Margins** The Columns block now [allows you to adjust the space between the columns](https://github.com/WordPress/gutenberg/pull/34630) and the margins surrounding the block. Combined with [customizable template part padding](https://github.com/WordPress/gutenberg/pull/35241), it is the most flexible layout-building experience Gutenberg ever had. [[ ### **Other Notable Highlights** As a part of the effort to [get the LinkControl component out of the “experimental” state](https://github.com/WordPress/gutenberg/issues/35073), 11.7 adds the [ability to create pages](https://github.com/WordPress/gutenberg/pull/35083) directly from the link popup. So far, this was only possible in the Navigation block, but now this feature is exposed on every link. The popup also [underwent subtle visual adjustments](https://github.com/WordPress/gutenberg/issues/35143). In addition, [empty links can no longer be added](https://github.com/WordPress/gutenberg/pull/35060), making adding one by mistake harder. The ones that fall through the cracks are now [clearly denoted as empty](https://github.com/WordPress/gutenberg/pull/35043).  [[ [[ Gutenberg 11.7 also ships a few formatting improvements. One of them is the ability to [highlight text](https://github.com/WordPress/gutenberg/pull/34680). Another is [a new alignment option called “none,”](https://github.com/WordPress/gutenberg/pull/34710) intended for resetting alignment settings. It is also worth noting that a breaking change [the post pagination markup](https://github.com/WordPress/gutenberg/issues/35610) was introduced in PR [35092](https://github.com/WordPress/gutenberg/pull/35092). # **11.7** ### Enhancements #### 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) * Adjust wording for post format suggestions. ([14124](https://github.com/WordPress/gutenberg/pull/14124)) * Add a visually hidden label for the Search block. ([35034](https://github.com/WordPress/gutenberg/pull/35034)) * Add an accessible label to the Back button in preferences. ([35340](https://github.com/WordPress/gutenberg/pull/35340)) * Global Styles: Add accessible label to Back button. ([35325](https://github.com/WordPress/gutenberg/pull/35325)) * Template title: Include a button and label text when there is no post/page title.( [35148](https://github.com/WordPress/gutenberg/pull/35148)) #### Block Editor * Allow other blocks to use the slash inserter. ([35196](https://github.com/WordPress/gutenberg/pull/35196)) * Enable ability to create Pages from the inline Link UIUI User interface. ([35083](https://github.com/WordPress/gutenberg/pull/35083)) * Polish quick inserter. ([35339](https://github.com/WordPress/gutenberg/pull/35339)) * Remove visual clue from alignment toolbar. ([35080](https://github.com/WordPress/gutenberg/pull/35080)) * Remove native block inserter onboarding tooltip. ([35150](https://github.com/WordPress/gutenberg/pull/35150)) #### Block Library * Site Logo: Add duotone support. ([35344](https://github.com/WordPress/gutenberg/pull/35344)) * Columns block: Enable blockGap and vertical margin support. ([34630](https://github.com/WordPress/gutenberg/pull/34630)) * File Block: Only display PDF preview height `RangeControl` when embed is enabled.( [35207](https://github.com/WordPress/gutenberg/pull/35207)) * Navigation: Add transformations from a link to other allowed nav blocks. ([34978](https://github.com/WordPress/gutenberg/pull/34978)) * Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. [https://codex.wordpress.org/The_Loop](https://codex.wordpress.org/The_Loop): Include a Query Pagination option on the block variations. ([35347](https://github.com/WordPress/gutenberg/pull/35347)) * Show “none” as an alignment option and use contextual text to clarify settings.( [34710](https://github.com/WordPress/gutenberg/pull/34710)) * Social Links: Add block gap support. ([35236](https://github.com/WordPress/gutenberg/pull/35236)) * Site Title: Add option to toggle home link. ([31540](https://github.com/WordPress/gutenberg/pull/31540)) * Site title: update block description. ([34474](https://github.com/WordPress/gutenberg/pull/34474)) * Transform Nav Links with children into Submenus. ([34831](https://github.com/WordPress/gutenberg/pull/34831)) * Add an option for displaying the label inside the Navigation Link block. ([34952](https://github.com/WordPress/gutenberg/pull/34952)) * Add typography settings for the Navigation Link block. ([35324](https://github.com/WordPress/gutenberg/pull/35324)) * Add option to remove/clear logo from the Site Logo block. ([34820](https://github.com/WordPress/gutenberg/pull/34820)) #### CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. data * Add ‘context’ to the query parts type definition. ([35069](https://github.com/WordPress/gutenberg/pull/35069)) #### Components * Add new Navigator components and use them in the global styles sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme.. ([34904](https://github.com/WordPress/gutenberg/pull/34904)) * Use _builtin property of classes in navigation link PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher. ([35166](https://github.com/WordPress/gutenberg/pull/35166)) * `Item`: Remove `isAction` and use `onClick` to decide if it should render as ` button`. ([35152](https://github.com/WordPress/gutenberg/pull/35152)) * Make tooltip delay configurable with a property. ([35246](https://github.com/WordPress/gutenberg/pull/35246)) #### Design Tools * Block gap: Only render CSSCSS Cascading Style Sheets. variable if corresponding theme setting is enabled. ([35209](https://github.com/WordPress/gutenberg/pull/35209)) * Format library: Add background color. ([34680](https://github.com/WordPress/gutenberg/pull/34680)) * Update: Custom gradient picker design. ([34712](https://github.com/WordPress/gutenberg/pull/34712)) #### Global Styles * Add Padding to the root level of global styles. ([35241](https://github.com/WordPress/gutenberg/pull/35241)) * Add duotone 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. styles support. ([34667](https://github.com/WordPress/gutenberg/pull/34667)) * Extract the color palette to its own global styles screen. ([35109](https://github.com/WordPress/gutenberg/pull/35109)) * Update the rules to hide/show blocks in the global styles sidebar. ([35178](https://github.com/WordPress/gutenberg/pull/35178)) * Synchronize user custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. registration and UI visibility. ([35427](https://github.com/WordPress/gutenberg/pull/35427)) * Enqueue preset styles for all themes in the editor. ([35424](https://github.com/WordPress/gutenberg/pull/35424)) #### Icons * Add color icon. ([35187](https://github.com/WordPress/gutenberg/pull/35187)) * Rename globe icon to url. ([35032](https://github.com/WordPress/gutenberg/pull/35032)) #### Site Editor * Remove warning box from post terms. ([35242](https://github.com/WordPress/gutenberg/pull/35242)) #### Template Editor * Add back button for isolated template part editor. ([34732](https://github.com/WordPress/gutenberg/pull/34732)) * Add template areas to template details. ([35202](https://github.com/WordPress/gutenberg/pull/35202)) ### Bug Fixes #### Block Editor * Block Editor: Fix duplicate clientIds when dragging patterns. ([35124](https://github.com/WordPress/gutenberg/pull/35124)) * Disallow creation of empty links using Link UI directly. ([35060](https://github.com/WordPress/gutenberg/pull/35060)) * Fix Link UI when hyperlink has an empty `href` value. ([35043](https://github.com/WordPress/gutenberg/pull/35043)) * Fix missing border in the quick inserter. ([35307](https://github.com/WordPress/gutenberg/pull/35307)) * Fix toggle off for Duotone control and Post Date block’s date picking control.( [35024](https://github.com/WordPress/gutenberg/pull/35024)) * useMultiSelection: Avoid crashing editor when block refs aren’t available. ([35177](https://github.com/WordPress/gutenberg/pull/35177)) * Rich text: fix internal paste across multiline and single line instances. ([35416](https://github.com/WordPress/gutenberg/pull/35416)) #### Block Library * Embed: Remove meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through [https://www.meetup.com/](https://www.meetup.com/). A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area.-com from variations. ([35146](https://github.com/WordPress/gutenberg/pull/35146)) * Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts.: Remove descendent space. ([35273](https://github.com/WordPress/gutenberg/pull/35273)) * Fix: Broken disabled select style in the editor area. ([35135](https://github.com/WordPress/gutenberg/pull/35135)) * Fix native BlockAlignmentControl. ([35191](https://github.com/WordPress/gutenberg/pull/35191)) * Gallery block: Fix Safari image sizing issue. ([35309](https://github.com/WordPress/gutenberg/pull/35309)) * Gallery block: Fix problem with caption showing encode tags when not selected.( [35131](https://github.com/WordPress/gutenberg/pull/35131)) * Gallery block: Unset alignment on new images to prevent it breaking layout. ( [35132](https://github.com/WordPress/gutenberg/pull/35132)) * Post Template: Remove margins from the block. ([35193](https://github.com/WordPress/gutenberg/pull/35193)) * Post Title: Always use blockProps. ([35286](https://github.com/WordPress/gutenberg/pull/35286)) * Post Title: Only render link element if we have a post. ([35284](https://github.com/WordPress/gutenberg/pull/35284)) * Query Pagination: Don’t render an empty container. ([35092](https://github.com/WordPress/gutenberg/pull/35092)) * Navigation Link: Fix PHP notice in the Navigation Link block. ([34984](https://github.com/WordPress/gutenberg/pull/34984)) * Fix Post Comment Content block’s edit function. ([35190](https://github.com/WordPress/gutenberg/pull/35190)) #### Components * Color Picker: Match figma metrics. ([35039](https://github.com/WordPress/gutenberg/pull/35039)) * Remove shift-stepping from range in RangeControl. ([35020](https://github.com/WordPress/gutenberg/pull/35020)) * Popover: fix __unstableBoundaryParent ([35082](https://github.com/WordPress/gutenberg/pull/35082)) #### Design Tools * ToolsPanelItem: Add panelId check before calling toggle methods. ([35375](https://github.com/WordPress/gutenberg/pull/35375)) #### Media * MediaUpload: Ensure current images in a gallery are selected after opening media library. ([35070](https://github.com/WordPress/gutenberg/pull/35070)) #### Post Editor * Fix missing save label. ([34948](https://github.com/WordPress/gutenberg/pull/34948)) * Keyboard shortcut: Prevent post saving through keyboard if post saving locked.( [35361](https://github.com/WordPress/gutenberg/pull/35361)) #### 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/)󠁿 * 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. Fetch: Improve isMediaUploadRequest check. ([34417](https://github.com/WordPress/gutenberg/pull/34417)) * Fix slashing when creating or updating a menu item. ([35147](https://github.com/WordPress/gutenberg/pull/35147)) #### Server Side Render * Prevent empty renders in ServerSideRender component caused by changing props while already fetching markup ([35433](https://github.com/WordPress/gutenberg/pull/35433)) #### Template Editor * Fix the styling of template details. ([35285](https://github.com/WordPress/gutenberg/pull/35285)) #### Widgets Editor * inspector-section: Track isOpen to make a better isContextuallyActive() function.( [35055](https://github.com/WordPress/gutenberg/pull/35055)) ### Performance * Edit Site: Optimize useSelect calls. ([35213](https://github.com/WordPress/gutenberg/pull/35213)) * Memoize entity records selectors properly. ([34323](https://github.com/WordPress/gutenberg/pull/34323)) * Widgets: Optimize useSelect calls. ([35256](https://github.com/WordPress/gutenberg/pull/35256)) ### Experiments #### Block Library * Polish responsive navigation modal, inherit justifications, fix submenu direction.( [35077](https://github.com/WordPress/gutenberg/pull/35077)) * Polish submenu indicator button. ([35030](https://github.com/WordPress/gutenberg/pull/35030)) * Fix: Adding nav items from existing menu. ([34837](https://github.com/WordPress/gutenberg/pull/34837)) #### Navigation Screen * Remove 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/12/?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. of help link in navigation editor. ([35313](https://github.com/WordPress/gutenberg/pull/35313)) * Add a tooltip to Navigation items in a setup state. ([35139](https://github.com/WordPress/gutenberg/pull/35139)) * Fix gap regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or [blockers](https://make.wordpress.org/core/2021/page/12/?output_format=md#blocker). Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in navigation screen. ([35234](https://github.com/WordPress/gutenberg/pull/35234)) * Truncate long menu names. ([35188](https://github.com/WordPress/gutenberg/pull/35188)) * Insert Navigation Link blocks by default in Navigation block. ([34899](https://github.com/WordPress/gutenberg/pull/34899)) * Migrate resolvers to thunks. ([35044](https://github.com/WordPress/gutenberg/pull/35044)) #### Full Site Editing * Remove extra styling around “Post content” placeholder. ([35243](https://github.com/WordPress/gutenberg/pull/35243)) ### Documentation #### Handbook * Docs: Update testing overview with minor fixes. ([35232](https://github.com/WordPress/gutenberg/pull/35232)) * Fix typos, grammar in contributors release doc. ([35268](https://github.com/WordPress/gutenberg/pull/35268)) * Update `nvm` to latest `0.38.0` version in Handbook. ([35125](https://github.com/WordPress/gutenberg/pull/35125)) * Adding example readme template to contributing guidelines. ([34847](https://github.com/WordPress/gutenberg/pull/34847)) * Fix erroneous usage of the word `master`. ([35392](https://github.com/WordPress/gutenberg/pull/35392)) #### Packages * Add instructions for installing plugins/themes with wp-env. ([35064](https://github.com/WordPress/gutenberg/pull/35064)) * MediaUpload: Reflect the correct filter name in the readme. ([35240](https://github.com/WordPress/gutenberg/pull/35240)) * Update LinkControl documentation with additional examples. ([35199](https://github.com/WordPress/gutenberg/pull/35199)) * Update doc block in block editor to fix documentation generation lint error. ( [35295](https://github.com/WordPress/gutenberg/pull/35295)) * Add missing doc blocks for the exported members of edit-widgets store. ([35263](https://github.com/WordPress/gutenberg/pull/35263)) ### Code Quality #### Block Editor * Add colord package to block editor; Replace tinycolor2 with colord on duotone.( [#34616](https://github.com/WordPress/gutenberg/pull/34616)), [34605](https://github.com/WordPress/gutenberg/pull/34605), [35165](https://github.com/WordPress/gutenberg/pull/35165), [35164](https://github.com/WordPress/gutenberg/pull/35164)) * Migrate the toggleFeature action to a thunk. ([35075](https://github.com/WordPress/gutenberg/pull/35075)) #### Block Library * Migrate store actions to thunks. ([35031](https://github.com/WordPress/gutenberg/pull/35031)) * Post Title Block: Fix argument numbering in ‘sprintf’. ([35338](https://github.com/WordPress/gutenberg/pull/35338)) * Replace tinycolor2 with colord on block library package. ([35184](https://github.com/WordPress/gutenberg/pull/35184) #### Components * Refactor `Navigator*` folder structure, rename `Navigator` to `NavigatorProvider`.( [35160](https://github.com/WordPress/gutenberg/pull/35160)) * Replace tinycolor2 with colord. ([35185](https://github.com/WordPress/gutenberg/pull/35185)) * ToolsPanel component: Refactor to typescript. ([34028](https://github.com/WordPress/gutenberg/pull/34028)) * UnitControl component: Refactor utils to TypeScript. ([35138](https://github.com/WordPress/gutenberg/pull/35138)) * Do not export `SimpleColorSwatch` in Storybook examples for Item Group. ([35179](https://github.com/WordPress/gutenberg/pull/35179)) * Refactor Navigator to TypeScript. ([35214](https://github.com/WordPress/gutenberg/pull/35214)) #### Global Styles * Simplify code that deals with user data for clarity. ([35248](https://github.com/WordPress/gutenberg/pull/35248)) * Simplify how we register preset metadata. ([35228](https://github.com/WordPress/gutenberg/pull/35228)) * Reorganize the global styles UI code base. ([35218](https://github.com/WordPress/gutenberg/pull/35218)) * Don’t output preset classes for colors defined by the theme ([35514](https://github.com/WordPress/gutenberg/pull/35514)) * Clean up logic to retrieve GS settings depending on context. ([35437](https://github.com/WordPress/gutenberg/pull/35437)) #### Post Editor * Keyboard Shortcuts: Use a new selector getter method. ([35385](https://github.com/WordPress/gutenberg/pull/35385)) #### Navigation Component * Refactor the preferences modal to use the new Navigator components. ([35142](https://github.com/WordPress/gutenberg/pull/35142)) * Navigation Editor: Remove duplicated stripHTML. ([35189](https://github.com/WordPress/gutenberg/pull/35189)) #### Widgets Editor * Migrate edit-widgets store to thunks. ([35110](https://github.com/WordPress/gutenberg/pull/35110)) ### Tools #### Build Tooling * Remove polyfills from view.js block scripts. ([35038](https://github.com/WordPress/gutenberg/pull/35038)) #### Testing * Add tests for `Navigator*`. ([35163](https://github.com/WordPress/gutenberg/pull/35163)) * Enable flaky tests reporter bot in PRs. ([35029](https://github.com/WordPress/gutenberg/pull/35029)) * Replace tinycolor2 with colord on getMostReadableColor util. Add unit testunit test Code written to test a small piece of code or functionality within a larger application. Everything from themes to WordPress core have a series of unit tests. Also see [regression](https://make.wordpress.org/core/2021/page/12/?output_format=md#regression)..( [34625](https://github.com/WordPress/gutenberg/pull/34625)) * Try fixing flaky navigation test. ([35380](https://github.com/WordPress/gutenberg/pull/35380)) * Fix not archiving failure artifacts for flaky tests. ([35379](https://github.com/WordPress/gutenberg/pull/35379)) #### Plugins * Add `oandregal` and `tellthemachines` to codeowners file. ([35233](https://github.com/WordPress/gutenberg/pull/35233)) ## Performance Benchmark The following benchmark compares performance for a particularly sizeable post (~ 36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance. | Version | Time To Render The First Block | KeyPress Event (typing) | | Gutenberg 11.7 | 3.7 s | 24.68 ms | | Gutenberg 11.6 | 3.5 s | 25.88 ms | | WordPress 5.8 | 4.0 s | 34.06 ms | Kudos to all the contributors that helped with the release. 👏 Thanks to [@priethor](https://profiles.wordpress.org/priethor/), [@matveb](https://profiles.wordpress.org/matveb/), and [@javiarce](https://profiles.wordpress.org/javiarce/) for helping with the release! --- Want to know more about recent Gutenberg releases? Check out the [release post for Gutenberg 11.6](https://make.wordpress.org/core/2021/10/01/whats-new-in-gutenberg-11-6-29-september/)! [#block-editor](https://make.wordpress.org/core/tag/block-editor/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#gutenberg](https://make.wordpress.org/core/tag/gutenberg/), [#gutenberg-new](https://make.wordpress.org/core/tag/gutenberg-new/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 10:26 pm _on_ October 13, 2021 Tags: [5.8.x ( 13 )](https://make.wordpress.org/core/tag/5-8-x/), [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [core-auto-updates ( 37 )](https://make.wordpress.org/core/tag/core-auto-updates/), [dev chat ( 920 )](https://make.wordpress.org/core/tag/dev-chat/), [summary ( 975 )](https://make.wordpress.org/core/tag/summary/), [twenty-twenty-two ( 4 )](https://make.wordpress.org/core/tag/twenty-twenty-two/) # 󠀁[Dev chat summary – October 13, 2021](https://make.wordpress.org/core/2021/10/13/dev-chat-summary-october-13-2021/)󠁿 [@audrasjb](https://profiles.wordpress.org/audrasjb/) led the chat on [this agenda](https://make.wordpress.org/core/2021/10/12/dev-chat-agenda-for-october-13-2021/). You can also read the [Slack logs](https://wordpress.slack.com/archives/C02RQBWTW/p1634155224245700). ## Highlighted blogblog (versus network, site) posts Bringing to your attention some interesting reads and some call for feedback and/ or volunteers: * [Core Editor Improvement: Continued progress on accessibility](https://make.wordpress.org/core/2021/10/06/core-editor-improvement-continued-progress-on-accessibility/) * [Proposal: Gutenberg Developer Hours series of events](https://make.wordpress.org/core/2021/10/07/proposal-gutenberg-developer-hours-series-of-events/) * [CSS chat summary – October 7](https://make.wordpress.org/core/2021/10/12/css-chat-summary-07-october-2021/) * [Twenty Twenty-Two Chat Summary — 11 Oct 2021](https://make.wordpress.org/core/2021/10/11/twenty-twenty-two-chat-summary-11-oct-2021/) * [Editor chat summary – 13 October, 2021](https://make.wordpress.org/core/2021/10/13/editor-chat-summary-13-october-2021/) * [Navigation Editor and Block Hallway Hangout](https://make.wordpress.org/core/2021/10/11/navigation-editor-and-block-hallway-hangout/)( happening earlier than dev chat) * [Submit Full Site Editing questions by Oct 27th](https://make.wordpress.org/core/2021/10/13/submit-full-site-editing-questions-by-oct-27th/) * [WordPress.org Profiles now show GitHub activity](https://make.wordpress.org/meta/2021/10/11/wordpress-org-profiles-now-show-github-activity/) * [Proposal for a Performance team](https://make.wordpress.org/core/2021/10/12/proposal-for-a-performance-team/) The proposal for a new Make/Performance team was well received by the meeting participants. Encouraging! Please add your feedback in the post comments. Worth mentioning: > **Thanks to the 30 contributors of the past week, including 3 new contributors! > Kudos to the 5 coreCore Core is the set of software required to run WordPress. > The Core Development Team builds WordPress. committers of the week, too.** > [**A Week in Core – October 11, 2021**](https://make.wordpress.org/core/2021/10/12/a-week-in-core-october-11-2021/) ## Upcoming releases updates ### 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) Please note that [5.8.2 was deferred](https://make.wordpress.org/core/2021/10/04/wordpress-5-8-2-deferred/) due to the lack of ready-to-ship tickets. Reminder: [@desrosj](https://profiles.wordpress.org/desrosj/) and [@circlecube](https://profiles.wordpress.org/circlecube/) are co-leading the 5.8.x releases. The 5.8.x point releases are coordinated in the [#5-8-release-leads](https://wordpress.slack.com/archives/C01VACX5E2W) 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. This channel is public and will be archived once 5.9 is released. [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) proposed to also 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. changeset [[51883]](https://core.trac.wordpress.org/changeset/51883)( which is milestoned to 5.8.2) to older branches. ### 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. Concerning the next major release —**WordPress 5.9**— a [planning roundup](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/) was published some weeks ago. [@kjellr](https://profiles.wordpress.org/kjellr/) introduced the new bundled theme on Make/Core last week. The first Twenty Twenty-Two meeting [was hosted on October 11, in the #core-themes Slack channel](https://make.wordpress.org/core/2021/10/11/twenty-twenty-two-chat-summary-11-oct-2021/). As usual, there is a [public repository on GitHub](https://github.com/wordpress/twentytwentytwo) so feel free to help testing the theme, and to contribute to this project. > [Introducing Twenty Twenty-Two](https://make.wordpress.org/core/2021/10/06/introducing-twenty-twenty-two/) The go/no go date for the main WP 5.9 features is October 14. [@audrasjb](https://profiles.wordpress.org/audrasjb/) will run another 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 on [Thursday October 14, 2021 at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211014T2000). Reminder: **everyone is welcome to run a bug scrub** on the `#core` Slack channel. If you are interested, please read this handbook post: [Leading bug scrubs](https://make.wordpress.org/core/handbook/tutorials/leading-bug-scrubs/) and get in touch with [@audrasjb](https://profiles.wordpress.org/audrasjb/) or [@francina](https://profiles.wordpress.org/francina/) for details. ## Component maintainers updates ### Upgrade/Install – 󠀁[@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)󠁿 󠀁[@afragen](https://profiles.wordpress.org/afragen/)󠁿 Work has continued on addressing PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher timeouts or missing files during large 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 updates. A couple of solutions were implemented so far, but it looks like the issue might not be fully resolved yet. Any testing and feedback welcome! See ticketticket Created for both bug reports and feature development on the bug tracker. [#54166](https://core.trac.wordpress.org/ticket/54166) for more details. Also, [@afragen](https://profiles.wordpress.org/afragen/) made a few updates to the new `move_dir()` function based on [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)’ s comments. ### Help/About – 󠀁[@marybaum](https://profiles.wordpress.org/marybaum/)󠁿 Help/About: the component had a scrub Monday and is following up with another on [@audrasjb](https://profiles.wordpress.org/audrasjb/) will run another bug scrub on [Monday October 18, 2021 at 19:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211018T1900). So far two tickets are ready for commit action. The [#core-auto-updates](https://make.wordpress.org/core/tag/core-auto-updates/) team is still looking on getting a consensus on which approach to proceed with for [#22316](https://core.trac.wordpress.org/ticket/22316). Two competing PRs are proposed( [1547](https://github.com/WordPress/wordpress-develop/pull/1547) and [1724](https://github.com/WordPress/wordpress-develop/pull/1724)), there is a need to decide what is the best approach. ## Open Floor [@johnjamesjacoby](https://profiles.wordpress.org/johnjamesjacoby/) raised ticket [#38231](https://core.trac.wordpress.org/ticket/38231) and asked for another pair of eyes. [@costdev](https://profiles.wordpress.org/costdev/) pointed out some possible enhancements in the unit tests provided by the ticket. [@webcommsat](https://profiles.wordpress.org/webcommsat/) shared that the Marketing Team is exploring how to help the Test Team reach extenders with the message to update their test suites to bring them in line with the latest WordPress Core PHP Test Suites.Everyone is welcome to join the collaboration in [this document](https://docs.google.com/document/d/1zPEjpLKVfPNgTBGR99izlny7uigIYXGZkmpk45PNg98/edit#heading=h.xrqgpw7mksxc), and they are looking specifically for items to be filled in on the table on page 4 to 6. [#5-8-x](https://make.wordpress.org/core/tag/5-8-x/), [#5-9](https://make.wordpress.org/core/tag/5-9/), [#dev-chat](https://make.wordpress.org/core/tag/dev-chat/), [#summary](https://make.wordpress.org/core/tag/summary/), [#twenty-twenty-two](https://make.wordpress.org/core/tag/twenty-twenty-two/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 4:02 pm _on_ October 13, 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/), [fse-outreach-experiment ( 14 )](https://make.wordpress.org/core/tag/fse-outreach-experiment/) # 󠀁[Editor chat summary: 13 October, 2021](https://make.wordpress.org/core/2021/10/13/editor-chat-summary-13-october-2021/)󠁿 This post summarizes the weekly editor chat meeting ([agenda here](https://make.wordpress.org/core/2021/10/11/editor-chat-agenda-13-oct-2021/)) held in [Slack](https://wordpress.slack.com/archives/C02QB2JS7/p1634133603250500). Moderated by [@annezazu](https://profiles.wordpress.org/annezazu/). ## Announcements * GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. [https://wordpress.org/gutenberg/](https://wordpress.org/gutenberg/) 11.7 is set to be released today with some wrangling [around any critical bug fixes](https://wordpress.slack.com/archives/C02QB2JS7/p1634124467245900). * It’s the last day to explore the current #fse-outreach-experiment call for testing. [Share your feedback here](https://make.wordpress.org/test/2021/09/29/fse-program-testing-call-10-pattern-party/)! * [The WordPress 5.9 Go/no go is coming up tomorrow](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/). Stay tuned for more insights after that completes.  * [Share your full site editing related questions](https://make.wordpress.org/core/2021/10/13/submit-full-site-editing-questions-by-oct-27th/) by October 27th! * [Check out this post ](https://make.wordpress.org/design/2021/10/08/adventures-in-block-theme-switching/) to get a peak of the future from [@critterverse](https://profiles.wordpress.org/critterverse/) on design explorations 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. theme switching. ## Monthly Priorities & Key Project Updates The overarching plan for October has not yet been shipped yet so we based today’s conversation on the [Mid September Plan](https://make.wordpress.org/core/2021/09/17/whats-next-in-gutenberg-mid-september-2021/). As a reminder to those working on these projects, async updates are both welcomed if you can’t make the meeting and _needed_. **Mobile Team** Shipped * Use theme colors in htmlHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. mode Fixes * Small fixes for embed block and help screen In Progress * Embed block improvements * GSS Font size, line height, colors **Navigation Block & Navigation Editor** The crew working on these projects had a hallway hangout today to chat through the state of their work. There is a [longer takeaway here](https://wordpress.slack.com/archives/C01KDAZJMQ9/p1634131070324000) from [@spacedmonkey](https://profiles.wordpress.org/spacedmonkey/) until notes are posted but for now, here’s a TLDR: Focus is on the navigation block / experience in FSE and the nav editor is blocked until the block lands. **Template editor** In 11.7, there are two changes impacting this general area of work: * A back button has been [added to the focused template part editor](https://github.com/WordPress/gutenberg/pull/34732) to make it easier to switch between experiences. * [Template areas have been added to template details](https://github.com/WordPress/gutenberg/pull/35202) making it more obvious to see at a glance where various template areas are in your content (see the PR for a visual). **Patterns** [A PR landed for 11.8 that changes the initial patterns](https://github.com/WordPress/gutenberg/pull/35115) shown to be from a featured list of patterns from the directory rather than an underwhelming alphabetical order. This should really help folks see the power of patterns more readily! **Styling** Shipping: * The team landed [support for `step=any` in both `UnitControl` and `NumberControl`](https://github.com/WordPress/gutenberg/pull/34542)! We have some [follow-up work](https://github.com/WordPress/gutenberg/issues/34817) planned as well. * Both `Navigator` and `UnitControl` made the move to TypeScript.  In Progress: * To match the [updated designs for the Global Styles sidebar](https://github.com/WordPress/gutenberg/issues/34574), [@ntsekouras](https://profiles.wordpress.org/ntsekouras/) opened [a PR enhancing the ](https://github.com/WordPress/gutenberg/pull/35395)` FontSizePicker`[ component](https://github.com/WordPress/gutenberg/pull/35395), adding specialized UIs for a small number of predefined options, a larger number of predefined options, and custom size selections. * We’re moving toward using `ToolsPanel` for typography tools. This week, we [merged a Storybook story attempting this](https://github.com/WordPress/gutenberg/pull/35293), which helped demonstrate some necessary changes on lower-level components. A few smaller refinements have been merged already, including [removing the unnecessary `fieldset` from](https://github.com/WordPress/gutenberg/pull/35461) [ ](https://href.li/?https://github.com/WordPress/gutenberg/pull/35461)`FontAppearanceControl`, support for [custom `aria-label` values on `ToggleGroupControl`](https://github.com/WordPress/gutenberg/pull/35423), and [removing vertical separators in `ToggleGroupControl`](https://github.com/WordPress/gutenberg/pull/35497). ## Task Coordination Feel free to add items to this post if you weren’t able to make the meeting. As a reminder, never be shy in sharing what you’re working on! It can sometimes be intimidating to see sponsored contributors share all they are doing but remember it all counts and is so appreciated. **[@mamaduka](https://profiles.wordpress.org/mamaduka/)** * I’m continuing exploration for remaining individual block locking items. Some [decisions](https://github.com/WordPress/gutenberg/issues/29864#issuecomment-935968290) are needed before I can start building UIUI User interface, and I would appreciate your feedback. * I created a small PR to [hide the “Move to”](https://github.com/WordPress/gutenberg/pull/35463) option when the block is locked. * I will try address Andre’s feedback re [parent/child theme.json merging](https://github.com/WordPress/gutenberg/pull/35459#issuecomment-939960484) feature this week. * Also created PR to correctly [use data](https://github.com/WordPress/gutenberg/pull/35592) for `customTemplates` from the 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. **[@annezazu](https://profiles.wordpress.org/annezazu/)** * [Responding to the patterns party call for testing](https://make.wordpress.org/test/2021/09/29/fse-program-testing-call-10-pattern-party/) feedback. * Drafting a summary of the results for the latest call for testing. * [Running a hallway hangout](https://make.wordpress.org/test/2021/10/06/hallway-hangout-pattern-party-testing-walkthrough-6-october/) alongside [@sparklingrobots](https://profiles.wordpress.org/sparklingrobots/). **[@colorful-tones](https://profiles.wordpress.org/colorful-tones/)** * I plan on trying to dig in on Margin/Padding rollout within [Consistent dimension controls across blocks.](https://github.com/WordPress/gutenberg/issues/28356) * Looking to help triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors., wrangle issues that are related and even maybe get a PR or two in. This relates to needs popping up in TwentyTwentyTwo. Specifically the latest here: [Post Title Block: Custom margin applied to Headings does is not reflected in the front-end #35522](https://github.com/WordPress/gutenberg/issues/35522) **[@mciampini](https://profiles.wordpress.org/mciampini/)** * I will continue supporting folks working on WordPress components. * This week in particular, I believe we’re going to focus on improving  the `ColorPicker`,` FontSizePicker`, `ToggleGroupControl`  any other control components used in Global Styles sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme., while coordinating the adoption of `ToolsPanel` in the Typography Tools **[@jffng](https://profiles.wordpress.org/jffng/)** * I’ve been working on [this PR](https://github.com/WordPress/gutenberg/pull/33217) that adds a Pattern block — giving themes a way to translate strings that appear inside block templates. * Keeping an eye on this [overview issue in Twenty Twenty-Two](https://github.com/WordPress/twentytwentytwo/issues/75) where we’re tracking some issues which would really help the next default theme ## Open Floor Lovely kudos to the team. Shared by Steve Dwire. > Just want to give a big thank you to everyone contributing so much.  I’m finally > getting back to theme development after years of neglect, and most of my to-do > list is already being addressed by coreCore Core is the set of software required > to run WordPress. The Core Development Team builds WordPress. team.  THANK YOU! Please help review [this PR that would move an API from experimental to stable](https://github.com/WordPress/gutenberg/pull/26031). Raised by [@fabiankaegy](https://profiles.wordpress.org/fabiankaegy/). As noted by Fabian, this PR touches many areas and would be a huge win 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, particularly because it would make building custom blocks with inner blocks so much easier. Next step: [@annezazu](https://profiles.wordpress.org/annezazu/) will follow up to see if we can get a review in place or figure out what the priority is. How can we liven up these open floor moments and use the [GitHub Discussions section better](https://github.com/WordPress/gutenberg/discussions)? Raised by [@annezazu](https://profiles.wordpress.org/annezazu/). For a while now, the open floor section of the meeting has been fairly quiet/uneventful, which feels a bit like a missed opportunity to connect and share ideas. We chatted about both re-sharing interesting discussions from the 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/) Discussions section in the meeting and having a nice interplay where perhaps a discussion from Core Editor ends up there to continue async. Many folks don’t check that part of GitHub right now so it might help bring larger attention and use there. If other folks have ideas/suggestions, do share in future meeting since this seems to be a longstanding pattern. On hallway hangouts, a PR ahead of 5.9, and speaking at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. [Learn more](https://central.wordcamp.org/about/). Italia. Raised by [@overclokk](https://profiles.wordpress.org/overclokk/). The topic of language barriers with hallway hangouts was brought up as not everyone is comfortable speaking in English but might still want to join hallway hangouts. This was a great chance to share that hallway hangouts don’t require speaking – you can join, listen in, and leave whenever you want. At the same time though, it would be neat to see them done in other languages and to have folks join who aren’t as comfortable with English in order to give feedback about how we can make them more inclusive. From there, we chatted briefly [about an issue raised that impacts block themes](https://github.com/WordPress/gutenberg/issues/34550) and that is important to review ahead of 5.9. Finally, we all sent good vibes and luck to [@overclokk](https://profiles.wordpress.org/overclokk/) ahead of his FSE presentation! Help review the [Autogenerate heading anchors PR](https://github.com/WordPress/gutenberg/pull/30825). Raised by [@paaljoachim](https://profiles.wordpress.org/paaljoachim/). This PR impacts larger work around a table-of-contents block so it would be lovely to continue to move this forward. [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-summary](https://make.wordpress.org/core/tag/core-editor-summary/) [ ](https://profiles.wordpress.org/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 4:01 pm _on_ October 13, 2021 Tags: [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [fse-answers ( 2 )](https://make.wordpress.org/core/tag/fse-answers/), [fse-outreach-experiment ( 14 )](https://make.wordpress.org/core/tag/fse-outreach-experiment/), [fse-outreach-program ( 5 )](https://make.wordpress.org/core/tag/fse-outreach-program/), [full-site editing ( 15 )](https://make.wordpress.org/core/tag/full-site-editing/) # 󠀁[Submit Full Site Editing questions by Oct 27th](https://make.wordpress.org/core/2021/10/13/submit-full-site-editing-questions-by-oct-27th/)󠁿 [With the Go/No Go session happening this week ahead of WordPress 5.9’s release in December 2021](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/), let’s use this time to dig into any general questions you all might have around Full Site Editing! As it’s possible, please focus questions specifically around WordPress 5.9 as those will be the most high impact to address and not on larger strategic decisions. You are welcome to submit questions using the form below or to leave them as a comment on this post by October 27th:   [Submit Questions](https://wordpressdotorg.survey.fm/fse-outreach-program-submit-fse-questions-round-three) Keep in mind that because, depending on the questions it’s likely that some answers might take the form of “people are working to figure this out and feedback is welcome here,” rather than a definitive answer. This is especially true for features/milestones that are planned for future releases.  **When and where will you share the answers? ** I’ll share a recap post on this blogblog (versus network, site) (Make CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.) as soon as I possibly can and aim to do so no later than November 1st, 2021. If there are a ton of questions, they will be grouped with corresponding answers for easy review. You can see what the outcome will look like [based on the first round](https://make.wordpress.org/test/2021/02/19/fse-program-answers-about-general-functionality/) and [second round](https://make.wordpress.org/test/2021/05/13/fse-program-answers-from-round-two-of-questions/). I will work in the open as I go in a collaborative Google doc that will be shared in [#fse-outreach-experiment](https://make.wordpress.org/core/tag/fse-outreach-experiment/) for anyone who wants to collaborate or check in on the work.  Once the post is published, I will follow up via email with everyone who left their email and a question in the form. For anyone who leaves a question as a comment on this post, I will @ your username in the recap post so you don’t miss out too! **What else will this effort help with? ** While the main outcome will be a lovely list of answers to grow community knowledge, this collective effort will also be useful for future documentation updates, potential tutorials, hallway hangout topics, and more. _For more information about the FSE outreach program, _[_please review this FAQ_](https://make.wordpress.org/test/handbook/full-site-editing-outreach-experiment/faq-for-fse-outreach-experiment/)_ for helpful details. To properly join the fun, please head to _[_#fse-outreach-experiment_](https://wordpress.slack.com/archives/C015GUFFC00)_ in _[_Make Slack_](https://make.wordpress.org/chat/)_ for future testing announcements, helpful posts, and more will be shared there. _ [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#fse-answers](https://make.wordpress.org/core/tag/fse-answers/), [#fse-outreach-program](https://make.wordpress.org/core/tag/fse-outreach-program/), [#full-site-editing](https://make.wordpress.org/core/tag/full-site-editing/) [ ](https://profiles.wordpress.org/danfarrow/) [Dan Farrow](https://profiles.wordpress.org/danfarrow/) 8:46 pm _on_ October 12, 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: 07 October 2021](https://make.wordpress.org/core/2021/10/12/css-chat-summary-07-october-2021/)󠁿 [The meeting took place here on Slack](https://wordpress.slack.com/archives/CQ7V4966Q/p1633640420151300). Thanks to [@dryanpress](https://profiles.wordpress.org/dryanpress/) for stepping in to facilitate at the last minute! [@danfarrow](https://profiles.wordpress.org/danfarrow/) wrote up these notes. ## Housekeeping * [@wazeter](https://profiles.wordpress.org/wazeter/) mentioned [this ticket about standardising hover effects (#48590)](https://core.trac.wordpress.org/ticket/48590), the goal of which relates to our custom properties project ## CSSCSS Cascading Style Sheets. Custom Properties (󠀁[#49930](https://core.trac.wordpress.org/ticket/49930)󠁿) * [@dryanpress](https://profiles.wordpress.org/dryanpress/) reported that [@circlecube](https://profiles.wordpress.org/circlecube/) has updated comments on his PRs and has been pinged about outstanding merge conflicts * [@dryanpress](https://profiles.wordpress.org/dryanpress/) is working on `.customize- controls.css`, continuing [@robertg](https://profiles.wordpress.org/robertg/)’ s extensive work on this 3000 line file * [@wazeter](https://profiles.wordpress.org/wazeter/) and [@dryanpress](https://profiles.wordpress.org/dryanpress/) reflected on the Custom Property project’s ongoing achievements, made possible by the many generous contributors * [@dryanpress](https://profiles.wordpress.org/dryanpress/) restated some points from last week’s meeting: - `custom-properties.css` needs organising and the addition of a table of contents - `box-shadow` declarations should be put into custom property - This is still the first-pass – there will be further consolidation of the custom-properties ## Open Floor / CSS Link Share * [@wazeter](https://profiles.wordpress.org/wazeter/) volunteered to facilitate next week’s meeting, on [Thursday October 14 at 21:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211014T2100) * [@dryanpress](https://profiles.wordpress.org/dryanpress/) shared a link to [Rich Tabor’s post on building Fluid Type Scales in the Theme.json](https://richtabor.com/fluid-type-scale-theme-json/) * [@dryanpress](https://profiles.wordpress.org/dryanpress/) shared a link to the [Twenty Twenty-Two](https://make.wordpress.org/core/2021/10/06/introducing-twenty-twenty-two/) project which promises to be the first default WordPress theme built for full- site editing and styled with `theme.json` – very exciting progress! * [@wazeter](https://profiles.wordpress.org/wazeter/) [shared a screengrab of his navigation and logo group block](https://wordpress.slack.com/archives/CQ7V4966Q/p1633642316186000), an exploration using `grid-template-areas` for a responsive layout without resorting to a hamburger menu ## Post-meeting chat! * [@dryanpress](https://profiles.wordpress.org/dryanpress/) and [@wazeter](https://profiles.wordpress.org/wazeter/) continued with [a long, interesting chat](https://wordpress.slack.com/archives/CQ7V4966Q/p1633642401188800) encompassing the [Tove theme’s header block pattern](https://themes.trac.wordpress.org/browser/tove/0.2.3/inc/block-patterns/header), the self-deception of “mobile first design”, the pros and cons of the nav 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., CSS Grid and [Tailwind’s Grid Template Columns](https://tailwindcss.com/docs/grid-template-columns), and [WordPress & the blockchain](https://sebastiaans.blog/) * [@dryanpress](https://profiles.wordpress.org/dryanpress/) also shared a couple of great CSS Grid learning resources: - [Layoutit Grid – a tool for building web layouts visually](https://grid.layoutit.com/) - [Sarah Drasner’s CSS Grid Generator](https://cssgrid-generator.netlify.app/) Thanks everybody! [#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/) 8:30 pm _on_ October 12, 2021 Tags: [5.9 ( 104 )](https://make.wordpress.org/core/tag/5-9/), [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 October 13, 2021](https://make.wordpress.org/core/2021/10/12/dev-chat-agenda-for-october-13-2021/)󠁿 Here is the agenda for this week’s developer meeting to occur on [October 13, 2021, at 20:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211013T2000). **Please note that depending on your timezone, the time may have changed with the end of daylight saving time.** ## Blogblog (versus network, site) Post Highlights and announcements Bringing to your attention some interesting reads and some call for feedback and/ or volunteers: * [A Week in Core – October 11, 2021](https://make.wordpress.org/core/2021/10/12/a-week-in-core-october-11-2021/) * [Core Editor Improvement: Continued progress on accessibility](https://make.wordpress.org/core/2021/10/06/core-editor-improvement-continued-progress-on-accessibility/) * [Proposal: Gutenberg Developer Hours series of events](https://make.wordpress.org/core/2021/10/07/proposal-gutenberg-developer-hours-series-of-events/) * [Navigation Editor and Block Hallway Hangout](https://make.wordpress.org/core/2021/10/11/navigation-editor-and-block-hallway-hangout/)( happening earlier than dev chat) * [WordPress.org Profiles now show GitHub activity](https://make.wordpress.org/meta/2021/10/11/wordpress-org-profiles-now-show-github-activity/) * [Proposal for a Performance team](https://make.wordpress.org/core/2021/10/12/proposal-for-a-performance-team/) ## Next releases status update * 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.: WP 5.9 👉 [WordPress 5.9 Planning Roundup](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/) 👉 [Introducing Twenty Twenty-Two](https://make.wordpress.org/core/2021/10/06/introducing-twenty-twenty-two/) ## 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/). [#5-9](https://make.wordpress.org/core/tag/5-9/), [#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/aristath/) [Ari Stathopoulos](https://profiles.wordpress.org/aristath/) 6:35 pm _on_ October 12, 2021 Tags: [performance ( 414 )](https://make.wordpress.org/core/tag/performance/), [proposal ( 38 )](https://make.wordpress.org/core/tag/proposal/), [team ( 4 )](https://make.wordpress.org/core/tag/team/) # 󠀁[Proposal for a Performance team](https://make.wordpress.org/core/2021/10/12/proposal-for-a-performance-team/)󠁿 _Note: a [follow up post](https://make.wordpress.org/core/2021/10/28/wordpress-performance-team-kick-off/) was published with information about next steps for this proposal_. We (the undersigned) believe that WordPress needs an official Performance team responsible for coordinating efforts to increase the performance (speed) of WordPress. This proposal outlines why we believe that this is necessary, how we envision such a team might function, and some potential initial areas of focus. It is authored by contributors from Yoast and Google. ## What problems are we trying to solve? Users expect and prefer fast experiences (consciously or otherwise). Research shows that fast websites can provide a better user experience, increase engagement, benefit SEO, increase conversion, and be more economically and ecologically friendly. References: * [A study into the impact of performance improvements on mobile websites](https://www2.deloitte.com/content/dam/Deloitte/ie/Documents/Consulting/Milliseconds_Make_Millions_report.pdf)( Deloitte, 2020) * [Documentation on how “page experience” influences Google’s search results](https://developers.google.com/search/docs/advanced/experience/page-experience)( Google, 2021) * [A variety of metrics and studies](https://blog.hubspot.com/marketing/page-load-time-conversion-rates)( HubSpot, 2021) * [A summary of 10 case studies](https://www.contentkingapp.com/academy/page-speed-resources/)( ContentKing, 2021) The benefits of improving performance driving investment across the web [[ref](https://twitter.com/Marie_Haynes/status/1393270374956142597)]. This further raises users’ expectations, and thus may comparatively ‘harm’ slow( er) things. Compared to other platforms (e.g., Wix, Shopify, Squarespace), WordPress is falling behind. Other platforms are on average faster – and becoming increasingly faster– than WordPress websites (see [The HTTP Archive’s Core Web Vitals report](https://datastudio.google.com/u/0/reporting/55bc8fad-44c2-4280-aa0b-5f3f0cd3d2be/page/M6ZPC?params=%7B%22df44%22:%22include%25EE%2580%25800%25EE%2580%2580IN%25EE%2580%2580WordPress%25EE%2580%2580WooCommerce%25EE%2580%2580Shopify%25EE%2580%2580Wix%25EE%2580%2580Squarespace%25EE%2580%2580Duda%22%7D)), and are actively investing in (and marketing) coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. performance- as-a-feature [[1](https://twitter.com/igrigorik/status/1432400252305244162), [2](https://support.wix.com/en/article/understanding-your-site-speed-dashboard)]. We can see the impact of this investment in the widening gap between the proportion of WordPress sites which achieve ‘good’ Core Web Vitals scores, vs other platforms. [[ Performance graph for CMSs on desktop clients. [[ Performance graph for CMSs on mobile clients. This gap continues to widen, despite the availability of [many performance plugins](https://wordpress.org/plugins/search/performance/) and [performance-focused themes](https://kinsta.com/blog/fastest-wordpress-theme/). This suggests that there’s a discovery and/or education problem, or an updating/ staleness problem – neither of which the 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. ecosystem solves for.  In order to meet the increasing needs and expectations of site owners and end-users, WordPress needs to be actively investing in performance in WordPress Core and beyond( e.g., core code, themes & plugins requirements, setup and onboarding processes, adminadmin (and super admin)/editing experiences, education for content creators). ## We believe that: * Performance is a fundamental part of user experience, and WordPress should aim to deliver a good user experience. * Achieving reasonable performance levels shouldn’t be plugin territory, but part of core (aka, “performance by default”), because; - All WordPress users (of all types) need a well lit path to good performance. - Average end-users can’t be expected to be performance experts. - Achieving high levels of performance requires technical considerations to be ‘built-in’ across the whole stack; and as this is often not the case with themes/plugins, performance solutions are limited to ‘brute-forcing’ performance solutions over non-performant behaviour (e.g., output buffering). - The plugin ecosystem doesn’t help users who don’t know that they need help, or who are poorly served by the plugin ecosystem. * Users determining which CMS to choose are / will be increasingly influenced by performance (and the associated UXUX User experience/SEO/conversion factors), and we’ll lose ground to faster platforms. * ‘Democratizing publishing’ requires that published content be discoverable; which will be less likely to occur via search engines (which influence or account for the majority of new content discovery) for slow(er) sites. [Web Vi](https://web.dev/vitals/)tals metrics provide a standardized and accepted mechanism for evaluating performance. ### Plugin territory Whilst we argue that _some_ (perhaps _most_) performance considerations should be part of core, there are definitely areas that should remain firmly in ‘plugin territory’. For example, the following areas should be handled by plugins: * Integrations with specific CDNs * Template transformation processes (e.g., AMP) * Any non-standardized performance technology * Any experimental standards (e.g., browser APIs / capabilitiescapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). with limited adoption) These distinctions will need exploring and lines will need drawing (and maintaining) as part of the team’s activity. ## Why a team? Performance is [already a focus in Trac](https://core.trac.wordpress.org/focus/performance) and [a label in the Gutenberg GitHub repository](https://github.com/WordPress/gutenberg/issues?q=is%3Aopen+is%3Aissue+label%3A%22%5BType%5D+Performance%22); but these alone don’t attract enough attention to the issues, nor unify efforts and priorities. Experienced and active contributors are not necessarily performance experts. A team gives more visibility to the effort: contributors that are not interested in working on Core as a whole can be attracted by working on performance specifically. It also opens up contributing to new types of contributors, like performance or data analysts. A performance team could also attract contributions from different groups; browsers, hosting, SEO companies, etc. ## Resources and efforts In practical terms, the creation of a performance team requires the following: * A performance 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.) on Make websites * A performance channel in SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/) * A meeting every two weeks; time to be determined * Two team representatives for administrative purposes: they will be responsible for:  - Giving a quarterly report to the project leadership - Assigning roles in the website * A team lead/product owner. They will be responsible to create a mission statement for the team, highlight the areas to tackle, outline the scope and the roadmap for the improvements that need to be made. * Representation in (and influence on) other Make verticals and processes (e.g., themes, plugins, etc) ## Next steps Next steps should be discussed and determined as part of the process of exploring and responding to this proposal. In the case that there are no objections, the next major steps are likely to be: * Set up Slack channel and meeting schedule, and make.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/) infrastructure. * Benchmark performance and define ongoing/future measurement & success criteria * Identify priority projects for CWV improvements with high-level timelines * Assign responsibilities for the projects identified ## Props Thanks to the following for this involvement in outlining this proposal. [@francina](https://profiles.wordpress.org/francina/), [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/), [@tweetythierry](https://profiles.wordpress.org/tweetythierry/), [@joostdevalk](https://profiles.wordpress.org/joostdevalk/), [@jonoaldersonwp](https://profiles.wordpress.org/jonoaldersonwp/), [@flixos90](https://profiles.wordpress.org/flixos90/), [@aristath](https://profiles.wordpress.org/aristath/) (in no particular order) [#performance](https://make.wordpress.org/core/tag/performance/), [#proposal](https://make.wordpress.org/core/tag/proposal/), [#team](https://make.wordpress.org/core/tag/team/) [ ](https://profiles.wordpress.org/audrasjb/) [Jb Audras](https://profiles.wordpress.org/audrasjb/) 1:29 pm _on_ October 12, 2021 Tags: [5.8.2 ( 16 )](https://make.wordpress.org/core/tag/5-8-2/), [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 – October 11, 2021](https://make.wordpress.org/core/2021/10/12/a-week-in-core-october-11-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 October 4 and October 11, 2021. * 16 commits * 30 contributors * 29 tickets created * 5 tickets reopened * 17 tickets closed The Core team is currently working on the next point (5.8.2) and major (5.9) releases 🛠 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=10%2F11%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 ### Administration * Allow 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. action links row to wrap – [#53275](https://core.trac.wordpress.org/ticket/53275) ### Build/Test Tools * Change 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. version used for testing the 5.6 branchbranch A directory in Subversion. WordPress uses branches to store the latest development code for each major release( 3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher – [#54223](https://core.trac.wordpress.org/ticket/54223) ### Bundled Themes * Twenty Twenty-One: Remove duplicate `width` and `height` values from social icons– [#54208](https://core.trac.wordpress.org/ticket/54208) ### Coding Standards * Use strict type check for `in_array()` in `register_block_script_handle()` – [#54206](https://core.trac.wordpress.org/ticket/54206), [#53359](https://core.trac.wordpress.org/ticket/53359) ### Docs * Add a `@since` note for the new `$parent_block` parameter of several filters – [#51612](https://core.trac.wordpress.org/ticket/51612) * Improve various inline documentation for adminadmin (and super admin) bar functions and 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. – [#53399](https://core.trac.wordpress.org/ticket/53399) * Miscellaneous inline documentation improvements, including: – [#53399](https://core.trac.wordpress.org/ticket/53399) ### Editor * Apply the `pre_render_block`, `render_block_data`, and `render_block_context` filters when rendering inner/nested blocks – [#51612](https://core.trac.wordpress.org/ticket/51612) ### External Libraries * Revert [[51900]](https://core.trac.wordpress.org/changeset/51900) for now to investigate test failures – [#54162](https://core.trac.wordpress.org/ticket/54162) * Update getID3 to version 1.9.21 – [#54162](https://core.trac.wordpress.org/ticket/54162) * Update jQuery UIUI User interface to 1.13.0 final – [#52163](https://core.trac.wordpress.org/ticket/52163) ### Permalinks * Move the NginxNGINX NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers. [https://www.nginx.com/](https://www.nginx.com/). documentation link to help sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. in` wp-admin/options-permalink.php` – [#39258](https://core.trac.wordpress.org/ticket/39258) ### Privacy * 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): Use red color for action buttons on the Erase Personal Data screen: – [#49603](https://core.trac.wordpress.org/ticket/49603) ### Site Health * Use an integer value as a fallback in the available disk space check – [#51857](https://core.trac.wordpress.org/ticket/51857) ### TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. 󠀁[https://codex.wordpress.org/Taxonomies#Default_Taxonomies](https://codex.wordpress.org/Taxonomies#Default_Taxonomies)󠁿. * Populate the `WP_Terms_List_Table::$items` property in `::prepare_items()` – [#54181](https://core.trac.wordpress.org/ticket/54181) ### Upgrade/Install * Introduce a `move_dir()` function – [#54166](https://core.trac.wordpress.org/ticket/54166), [#51857](https://core.trac.wordpress.org/ticket/51857) ## Props **Thanks to the 30 people who contributed to WordPress Core on Trac last week:** [@audrasjb](https://profiles.wordpress.org/audrasjb/) (4), [@SergeyBiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 4), [@azaozz](https://profiles.wordpress.org/azaozz/) (3), [@mukesh27](https://profiles.wordpress.org/mukesh27/)( 2), [@sabernhardt](https://profiles.wordpress.org/sabernhardt/) (2), [@hellofromTonya](https://profiles.wordpress.org/hellofromtonya/)( 2), [@Clorith](https://profiles.wordpress.org/clorith/) (2), [@noisysocks](https://profiles.wordpress.org/noisysocks/)( 2), [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) (2), [@aristath](https://profiles.wordpress.org/aristath/)( 2), [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/) (2), [@joedolson](https://profiles.wordpress.org/joedolson/)( 1), [@carike](https://profiles.wordpress.org/carike/) (1), [@arena](https://profiles.wordpress.org/arena/)( 1), [@desrosj](https://profiles.wordpress.org/desrosj/) (1), [@timlappe](https://profiles.wordpress.org/timlappe/)( 1), [@johnjamesjacoby](https://profiles.wordpress.org/johnjamesjacoby/) (1), [@jrf](https://profiles.wordpress.org/jrf/)( 1), [@gaambo](https://profiles.wordpress.org/gaambo/) (1), [@Presskopp](https://profiles.wordpress.org/presskopp/)( 1), [@laxman-prajapati](https://profiles.wordpress.org/laxman-prajapati/) (1), [@max-dayala](https://profiles.wordpress.org/max-dayala/)( 1), [@swissspidy](https://profiles.wordpress.org/swissspidy/) (1), [@mattoakley](https://profiles.wordpress.org/mattoakley/)( 1), [@mgol](https://profiles.wordpress.org/mgol/) (1), [@TobiasBg](https://profiles.wordpress.org/tobiasbg/)( 1), [@pbiron](https://profiles.wordpress.org/pbiron/) (1), [@galbaras](https://profiles.wordpress.org/galbaras/)( 1), [@afragen](https://profiles.wordpress.org/afragen/) (1), and [@ankit-k-gupta](https://profiles.wordpress.org/ankit-k-gupta/)( 1). **Congrats and welcome to our 3 new contributors of the week: **[@timlappe](https://profiles.wordpress.org/timlappe/), [@max-dayala](https://profiles.wordpress.org/max-dayala/), [@mattoakley](https://profiles.wordpress.org/mattoakley/) ♥️ **Core committers:** [@sergeybiryukov](https://profiles.wordpress.org/sergeybiryukov/)( 8), [@hellofromtonya](https://profiles.wordpress.org/hellofromtonya/) (3), [@azaozz](https://profiles.wordpress.org/azaozz/)( 2), [@johnbillion](https://profiles.wordpress.org/johnbillion/) (2), and [@desrosj](https://profiles.wordpress.org/desrosj/)( 1). [#5-8-2](https://make.wordpress.org/core/tag/5-8-2/), [#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/annezazu/) [annezazu](https://profiles.wordpress.org/annezazu/) 10:20 pm _on_ October 11, 2021 Tags: [agenda ( 1,141 )](https://make.wordpress.org/core/tag/agenda/), [core-editor ( 756 )](https://make.wordpress.org/core/tag/core-editor/), [core-editor-agenda ( 189 )](https://make.wordpress.org/core/tag/core-editor-agenda/), [meeting ( 405 )](https://make.wordpress.org/core/tag/meeting/)    # 󠀁[Editor Chat Agenda: 13 Oct 2021](https://make.wordpress.org/core/2021/10/11/editor-chat-agenda-13-oct-2021/)󠁿 Facilitator and notetaker: [@annezazu](https://profiles.wordpress.org/annezazu/) This is the agenda for the weekly _editor chat_ scheduled for [2021-10-13 14:00 UTC](https://www.timeanddate.com/worldclock/fixedtime.html?iso=20211013T1400). _This meeting is held in the [#core-editor](https://wordpress.slack.com/messages/C02QB2JS7) channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform [https://slack.com/](https://slack.com/). The WordPress community has its own Slack Channel at [https://make.wordpress.org/chat/](https://make.wordpress.org/chat/)._ * What’s new 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/)( 11.7). This release is planned for the day of the meeting. * [WordPress 5.9](https://make.wordpress.org/core/2021/09/03/wordpress-5-9-planning-roundup/)“ Go, no go” date and [priorities](https://make.wordpress.org/core/2021/08/13/preliminary-road-to-5-9/). This will be more of a heads up as the meeting now happens on October 14th rather than the 12th. * [Whats next in Gutenberg: Mid-September 2021.](https://make.wordpress.org/core/2021/09/17/whats-next-in-gutenberg-mid-september-2021/) * Updates based on [updated scope for site editing projects](https://github.com/WordPress/gutenberg/issues/33094): - 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. & Navigation Editor. - Template editor. - Patterns. - Styling. - Mobile Team. * Task Coordination. * Open Floor. If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion: * If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself. * If you have anything to share for the Task Coordination section, please leave it as a comment on this post. * If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below. [#agenda](https://make.wordpress.org/core/tag/agenda/), [#core-editor](https://make.wordpress.org/core/tag/core-editor/), [#core-editor-agenda](https://make.wordpress.org/core/tag/core-editor-agenda/), [#meeting](https://make.wordpress.org/core/tag/meeting/) # Post navigation [← Older posts](https://make.wordpress.org/core/2021/page/13/?output_format=md) [Newer posts →](https://make.wordpress.org/core/2021/page/11/?output_format=md)