What’s new in Gutenberg? (30 September)

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/ 9.1 is out with almost 200 commits and 77 contributors! The main focuses for this release are iterations on the main projects for WordPress 5.6: the Widgets Screen 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. 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..

Important progress has been made on the Global styles project with the possibility to use 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. config file to control the block editor features and presets (color palette, font sizes, enabling/disabling features).

Also, the release includes some nice little improvements to the UIUI User interface and several blocks. Among these changes, the block patterns are now organized per categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. in the block inserter to help navigate the list of available patterns.

9.1 🇲🇹

Features

  • Add “open in new tab” feature to Social Links Block. (25468)
  • Add Image Size control to the Media & Text block. (24795)

Enhancements

  • Inserter: Add block pattern category selection. (24954)
  • Reduce minimum height to 1px for the Spacer block. (25528)
  • Show the Fullscreen keyboard shortcut. (25395)
  • Improve the Audio block shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. transform to account for all sources. (25114)
  • Code block: Allow HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. editing & rich text content. (24689)
  • Remove appender from unselected Buttons and Social Icons block. (25518)
  • Widgets Screen:
    • Match the post editor inserter design. (25681)
    • Register legacy widgets as block variations. (24905)
    • Use the default block list appender for the 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. (25635)
    • Add titles to Legacy Widgets. (25638)
  • Buttons block: Lighten editor DOM. (23222)
  • Copy: Reword block settings menu item labels. (22955)
  • Add a tooltip to the Drag & Drop handle. (25606) (25614)
  • A11yAccessibility 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):
    • Add aria-haspopup property to the BlockNavigation component. (25605)
    • Add aria-haspopup property to the TableOfContents component. (25603)
    • Add aria-haspopup to the ToolSelector. (25600)
    • Add aria-haspopup to the MediaReplaceFlow button. (25597)
    • Add aria-haspopup attribute to CustomGradientBar component. (25571)
    • Add aria-haspopup to CircularOptionPicker component. (25564)
    • Add aria-describedby to featured-image button. (24888)
  • Don’t show heading ancestor blocks in Document Outline. (25599)
  • Support the default link config for the Gallery and Image blocks (image_default_link_type). (25578) (25582)
  • Social Icons Block: Let icons wrap. (25334)

New APIs

  • Add new ComboboxControl. (25442)
  • Data Controls: Add new syncSelect control. (25336)
  • DateTimePicker: Add support for highlighting days. (22032)

Bug Fixes

  • Widgets Screen:
    • Auto expand the last selected widget area when opening the inserter. (25669)
    • Ensure all widgets are properly initialized when they’re added, do not unmount widgets once they’re mounted. (25645)
    • Fix Legacy widget block previews and use iFrames. (25443) (14643)
    • Report save errors. (25408)
    • Fix global inserter. (24908)
  • Fix RangeControl direct entry in input field. (25609)
  • A11y:
    • Fix the color contrast in the code editor. (25593)
    • Fix Publish 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. Cancel button not usable through screen readers. (25441)
    • Fix keyboard navigation on the Image block toolbar. (25127)
    • More block: Use an actual placeholder for input text. (23836)
  • Fix nested container smart margins. (25527)
  • Fix add_filter instead of apply_filters. (25512)
  • Fix the WordPress embed preview in the editor. (25370)
  • Remove Embed block aspect ratio classes on url change. (25295)
  • Remove duplicate help item. (25283)
  • Fix Block Directory author average rating formating. (24732)
  • wordpress/api-fetch:
    • Fix preloading middleware referencing stale data. (25550)
    • Check nonce 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. value before skipping adding it. (25458)
  • Use esc_html instead of esc_attr in the Archives block. (25476)
  • Fix Canceling Drag and Drop using ESC key. (25317)
  • Cover block: Add explilcit box-sizing style. (25115)
  • Use a ComboboxControl for the post author selector to fix loading issues for sites with a big number of authors. (23237)

Performance

  • Avoid relying on DOM events to measure the loading time. (25288)

Experiments

  • Site Editor Screen:
    • Fix wrong close label in the block inspector. (25424)
    • Add basic template information to editor header. (25320)
    • Fix the footer styling. (25152)
    • Add a reset button to global styles sidebar. (25426)
    • Show document subtext if template part child is selected. (25544)
    • Add navigation panel. (25506)
    • Fix site base URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org. (25409)
  • Post and Site Blocks:
    • Add link option in PostTitle block. (25341) (25397)
    • Register the Site Logo block using register_block_type_from_metadata. (25289)
  • Themes and global styles:
    • Support defining colors and gradients config from theme.json. (25419)
    • Support defining font sizes config from theme.json. (25516)
    • Support custom units on theme.json. (25217)
    • Add separate support keys for color and background color. (25314)
    • Allow themes to enqueue custom CSSCSS Cascading Style Sheets. variables via theme.json. (25446) (25619)
    • Refactor theme.json format. (25301) (25407)
    • Update theme json documentation to account for latest changes. (25369)
  • Block API: Introduce useBlockWrapperProps hook to use light block DOM in the editor. (23034) (25679) (25554) (25515)
  • Navigation block and screen:
    • Handle block menu items. (24846)
    • Avoid auto-focusing Navigation block in Navigation screen. (25592)
    • Change the block description. (25531) (25555)
    • Allow Social Links within Navigation Block. (25357)
    • Wrap navigation editing features with filters. (25329)
    • Add move markers to list view. (25205)
  • Iterating on the Navigation Component (25608) (25495) (25572) (25540) (25520) (25507) (25367) (25364) (25340) (25327) (25281) (25280)

Documentation

  • Add a data format and flow architecture document. (25299)
  • wordpress/env: Add documentation for inspecting the docker compose file. (25666)
  • Add new block supports page to the handbook. (25647)
  • Block Directory: Add developer documentation. (25591)
  • Move custom-fields note to the ‘Register MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Field’ documentation. (25584)
  • Add Block Editor Components documentation:
    • AlignmentToolbar (25210)
    • BlockFormatControls (25573)
  • Add Caveats section for MAMP. (25444)
  • Add FormTokenField story. (25439)
  • Improve documentation for the data registry control and selector creators. (25335)
  • Update git workflow documentation. (25164)
  • Refresh the Getting Started guide. (25090)
  • Update JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. troubleshooting guide. (24105)
  • Enhance the Block Context documentation. (25272)
  • Typos: (25359) (25653)

Code Quality

  • Update the Dashicon component to rely on the font that ships with WordPress. (20003)
  • Add new $gray-200 SASS variable and use for skeleton borders. (25491)
  • Block Editor: Remove empty module focus-detector. (25561)
  • Image block: Avoid remounting to focus caption. (25493)
  • Add explicit boxSizing style to Placeholder component. (25463)
  • Remove classic block code used to support WP 4.9. (25365)
  • Add RichText value type definition. (25363)
  • Avoid global DOM dependencies. (25332)
  • Use controls from the Data Controls package instead of local ones. (25235)
  • RichText: Simplify withFormatTypes as hook. (23145)
  • Video block: Use 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.. (25513)
  • Remove wp_area 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.. (25497)
  • Post 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 redundant condition. (25490)
  • Move legacy-widget block over to edit-widgets package. (25371) (25404)
  • Don’t use percent units for line-height. (25398)
  • Change wording and names to not include “whitelist”. (25396)
  • Don’t discard all promises results when one of them rejects. (25302)
  • Block Directory: Switch to blocks.registerBlockType filterFilter Filters are one of the two types of 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.. (25264)
  • Fix some javascript warnings. (24996)

Various

  • Remove the Block-based widgets editor from the customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.. (25626)
  • Cover block: Remove default position (center/center) className from rendering. (25346)
  • Fix the default label position in SelectControl. (25427)
  • DropdownMenu tooltip default to true. (25391)
  • Pass block pattern name when using replaceBlocks and insertBlocks. (25165). (25433)
  • Babel Preset: Update Babel version to 7.11.x. (25351)
  • InputControl: Remove floating label variant. (25308)

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.

VersionLoading TimeKeyPress Event (typing)
Gutenberg 9.16.9s29.04ms
Gutenberg 9.06.5s29.19ms
WordPress 5.56.5s28.01ms

Kudos for all the contributors that helped with the release. 👏

#core-editor, #editor, #gutenberg, #gutenberg-new

Navigation Screen Removed from 5.6 Release Features

The Navigation Screen project was slated for inclusion in 5.6. Given the volume of work left to bring it to a stable state coupled with the imminence of the 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. 1 deadline for feature inclusion, contributors @andraganescu, @noisysocks, @talldan and myself, as Editor Tech Lead for 5.6, have decided to exclude it from this release. 

The Reasoning

The Navigation screen is still in experimental state 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/ 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/ or can be cost-based plugin from a third-party, so it hasn’t had any significant real-world use and testing yet. The deadline set to bring it out of experimental state was the Gutenberg 9.1 release, which would have allowed for 3 weeks of testing before Beta 1. That deadline was announced at Navigation triage on the 16th of September.

When the Gutenberg 9.1 RC1 was released on September 29th, there were still three major blockers unresolved: 

  •  Completion of the MVP redesign: needs design and 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) feedback and iteration, as well as substantial development work.
  • Adding Navigation editor to the Customizer: needs design and technical investigation on the development side, as well as actual implementation.
  • Adding Links block: needs substantial development work.

On top of this, there are multiple smaller issues still in need of design and development. Therefore, the Navigation screen did not seem stable enough to ship with Gutenberg 9.1. 

Additionally, there is another big feature slated for 5.6 that is close to completion but still needs some extra work: the Widgets screen. It is currently undergoing testing in the Gutenberg plugin, and contributors who were previously focused on the Navigation screen will now be able to bring their full attention to Widgets and ensure it lands smoothly in 5.6. 

Next Steps

The priority now is ensuring that the Widgets screen gets thoroughly tested so any bugs are uncovered before Beta 1. We ask anyone who is able to help with this effort to read this post with more details on how to help.

For those wanting to help with development, we encourage you to attend or review the weekly triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions in the #core Slack channel on Wednesdays at 7am UTC. The focus of these sessions has shifted from the Navigation screen to the Widgets screen, as of this week. 

As for the Navigation screen, active development will continue after 5.6 is ready, towards the end of November.

#5-6, #core-editor, #gutenberg

Editor chat summary: Wednesday, 16 September 2020

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, September 16, 2020, 14:00 UTC.

Thank you to all of the contributors who tested the 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. releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.

WordPress 5.6

Project board to track issues for inclusion in WordPress 5.6.

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/ 9.0

Gutenberg 9.0 was released on 16th September: 

Monthly Plan

September Monthly Priorities.

Updates on the key projects

@andraganescu

  • Both the navigation editor and the widgets editor need all the help they can get. The current target to get the Navigation editor out of experimental is Gutenberg 9.1, and if not it will not make it into WP 5.6 due to too little time for testing and consideration before beta 1
  • The work continues on the widgets editor with a lot of feedback since it was removed from experimental 
  • More details can be tracked on project boards for Navigation editor and Widgets editor

@ntsekouras

  • There is some ongoing work on Query 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 here is where design is discussed/iterated: https://github.com/WordPress/gutenberg/issues/25198.Since there are many things to consider, feedback is more than welcome.

@nosolosw

There’s been some momentum around the Global Styles project lately (with Jorge, Riad, myself, and others working on this), these are the highlights:

  • Gutenberg 9.0 is the first to come with a UIUI User interface for users to update the theme 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. at the site editor).
  • Most of the add_theme_supports have been ported to theme.json  allowing themes to have more fine-grained control about the features.
  • There’s been a reorganization of 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. (docs) to better clarify its purpose.
  • Discussion on allowing creating your own CSSCSS Cascading Style Sheets. variables via Global Styles

Task Coordination

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

@ntsekouras

  • Added search in Query block
  • Added option to make PostTitle block a link
  • Fixed aspect ratio related classes on embed block
  • Reviews, issues, and triaging

@zieladam

  • Fixed global inserter in widgets editor
  • Moved legacy-widget block to edit-widget package
  • Working on registering widgets as block variations

@nosolosw

  • I’ve been helping others land features related to theme.json (reviews), plus landed some bugfixes and minor follow-ups related to that.

@mcsf

  • Added tiny improvements to Gallery block, ID-less shortcodes fall to ShortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. block
  • Discuss server-side solutions for block-supports
  • Discuss global styles architecture
  • Release 8.9.3
  • Explore dynamic content solutions for FSE templates
  • Reviews

@addiestavlo

@soean

@mapk

  • Query block iterations
  • 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 feedback and followups

@andraganescu

  • I’ve picked up some issues from Navigation
  • Wrap navigation editing features with filters
  • Added edit in place for menu name

@vindl

@itsjonq

  • Continue to explore/refine Component 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. / style ideas in G2 Components
  • Lately, been focused on the figuring out structure details for control variations that render within Gutenberg via this G2 Layouts/Segmenting controls thread

@aristath

  • I’ve been working on FSE & Global styles, trying to build a theme as a way to discover issues and fix them. Lots of PR reviews, I’ll start working on the Query block next since I’m finding things as I go.

@annezazu

  • Launched the guide for devs navigating the community
  • Focusing on triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and testing this week to get back up to speed on the latest!

@copons

  • The main focus on the new Navigation component.
  • I’ve recently merged the initial PR which is not used anywhere yet and is exported as experimental.
  • The interface is in active development and will change a lot, though; while it works, it’s really not supposed to be used yet.
  • Meanwhile, it can be tested in the Storybook.
  • I’ve opened several issues for the next steps and discussions about style and accessibility.
  • Once the component is polished and fine-tuned enough, the plan is to start using it as template selector in the Site Editor

@jorgefilipecosta

  • Updated the global styles setProperty mechanism and solved an issue that made custom gradients not work on global styles
  • Refactored the global style’s shape
  • Added separate support keys for color and background-color
  • Continued the iterations on the font-family and font-weight PR’s
  • Did some PR’s reviews and participated in discussions around the repository

Open Floor

@jonsurrell

Some discussion around more descriptive post title for “The Gutenberg Release notes”. suggestion to add 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/ or can be cost-based plugin from a third-party version for more clarity. There was no decision and further discussion for same to be done before next release post.

@pierlo

Asked if extending the external preview links dropdown would be included for WP 5.6. A PR is in the work which should very likely be merged well before the 5.6 beta begins 20th October.

@aristath

Some discussion around Query block to inherit default from the global query and allow the user to customize them as needed. This will avoid overriding the global query and replacing loops. No decision, to be discussed further.

#meeting-notes, #core-editor, #editor, #gutenberg, #core-editor-summary

What’s new in Gutenberg? (16 September)

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/ 9.0 is out! The main focuses for this release are improvements to the Navigation Screen and to the Query 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..

The Navigation screen has a new and improved look, and now supports drag and drop inside the list view:

Lots of cool features have been added to the Query block, including search, filtering by author and support for tags. Here are some pics of the updated interface:

9.0

Features

  • Query block:
    • add search. (25222)
    • add filtering by author support in Query block. (25149)
    • add order and order by support. (24691)
    • add tags support. (25005)
  • Navigation screen:
    • add drag and drop to List View. (23952)
    • implement redesign of screen. (25178)
    • add support for advanced menu item properties. (25062)

Enhancements

  • Drag&Drop: add drag handle to block toolbar. (24852)
  • Drag&Drop: improve single block case. (25107)
  • Include the block variations on the inserter selector. (25182)
  • List view styling improvements. (25143)
  • Update pencil icon. (25135)
  • Refactor and make consistent post and site headers. (25134)
  • Limit the block slash inserter to 9 items and show most used by default. (25113)
  • Polish menu item icon locations. (25106)
  • Improve the block and patterns search algorithm. (25105)
  • Template part: attribute feature parity with group block. (25029)
  • Allow sharp gradients. (24967)
  • Post content: show placeholder if trying to render itself. (24010)
  • Add reusable block icon. (23552)
  • Let ID-less gallery shortcodes fall to ShortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. block. (25144)
  • Mirror WordPress 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/ or can be cost-based plugin from a third-party install text for blocks. (25084)
  • Allow inserting an h1 using # + space. (25075)
  • Widgets screen: add plugin area. (25074)
  • Add title attribute to Navigation Link block. (24993)
  • Add a way to change template parts. (24990)
  • Transform multiple heading blocks to list or paragraphs. (24977)
  • Remove redundant type badges in navigation link control. (24885)
  • Fix multiple trailing inserters for nested InnerBlocks. (24836)
  • Search Block: Add button, label, and width options. (24666)
  • Display labels instead of icons in top toolbar. (24304)
  • Add option to show icon labels. (24234)
  • Add a "reinstall" button when a block type is not found. (22631)

Bug Fixes

  • Template part: fix rename before customize 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.. (25206)
  • Template part: fix auto-drafting to support sub-directories. (25063)
  • Template part: use cleaned slug to query. (25030)
  • Classic block: optional chain on possibly null editor. (25163)
  • Classic block: show contents on load. (25162)
  • Embed Block: Fix crash in isFromWordPress helper if preview.htmlHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. is false. (25140)
  • Cover block: fix width regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. 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.. (25103)
  • Navigation block: reduce subnavigation arrow padding. (24200)
  • GlobalStyles: fix nested features algorithm. (25215)
  • GlobalStyles: fix settings name. (25040)
  • Widgets screen: convert the toolbar to ARIA toolbar. (25111)
  • Widgets screen: add labels for settings and close button. (25101)
  • Navigation screen: fix creating Navigation from pages or menu with HTML in title. (24673)
  • Element: add and upgrade @types/{reactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/.,react-dom} dependencies. (25086)
  • Add safeguard to AuthorSelect component until authors are fetched. (25214)
  • Fix PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 error when users don’t have access to the Appearance menu. (25073)
  • Polish horizontal movers. (25037)
  • Fix PHP Notice: Check that the query arg exists before using it. (25006)
  • Fix gradient swatches stacking badly with scrollbar. (25002)
  • Fix unlinked padding controls JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. error. (25000)
  • Show external icon on help button. (24622)
  • Check if block attributes exist before splitting. (25229)
  • Revert "InnerBlocks: Introduce prop to specify render callback for each block.". (25196)
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Data: Bring back support for nested _fields values. (25083)
  • Prevent TypeError for projects without a local Prettier configuration. (25068)
  • Image Block: Properly show errors on drag n drop. (25004)
  • Add block inspector virtual bubbling option. (24991)
  • Remove extra slash from $block_json_file. (24829)
  • Inserter: Test to make sure the Inserter menu is closed. (24610)
  • Date: Update moment-timezone package to support string timezones. (22866)
  • Fix enqueue presets for global styles. (25286)
  • Fix stylesheet generation. (25293)

Experiments

  • Group block: add padding support. (24966)
  • Control the block editor via 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.:
    • support for custom link color. (25148)
    • support for custom spacing. (25141)
    • support for custom line heights. (25043)
    • support for custom font sizes. (25038)
    • support for custom gradients. (24964)
  • Navigation component: composition proposal. (25057)
  • Replace accessibilityLabel by label on RadioGroup. (25128)
  • Global styles:
    • add 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. at edit site screen. (24250)
    • print minified css. (24924)
    • centralize style & support mappings for blocks. (25185)
    • centralize client side global styles mappings. (25056)
    • set property to change one property accept all lodash paths. (25159)

Documentation

  • Add readme for UngroupButton. (25142)
  • Fix typo in AlignmentMatrixControl readme. (25125)
  • Update AlignmentMatrixControl readme. (25124)
  • Add preview options component readme. (25104)
  • Add block types list component readme. (25066)
  • Fix typo in block base themes tutorial URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org (25024)
  • Update block inspector component readme. (24998)
  • Add block variation picker component readme. (24995)
  • Update Versions in WordPress doc to include 5.5.1. (24988)
  • Add block parent selector component readme. (24962)
  • Add block icon component readme. (24947)
  • Update dev environment setup. (24871)
  • Correct since version for block parser package. (24819)
  • Add BlockCard component readme. (25150)
  • Fix link to ubuntu docker notes. (25060)
  • Fix/block parent selector component readme. (24997)
  • Update Storybook URL from text to a real link. (24974)
  • Update triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. doc to include pull request mentions. (23105)

Code Quality

  • Repo: Add .gitattributes to specify text=auto. (25224)
  • Block Directory: Use Array.filterFilter Filters are one of the two types of 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. to implement new/unused block selectors. (25211)
  • Data: Remove flowRight call from metadata reducer. (25180)
  • Data: Add a comment about why we normalize resolvers to objects with fulfill method. (25102)
  • Api-fetch: Remove redundant next parameter from middleware calls. (25001)
  • Api-fetch: Simplify the code that executes the handlers. (24999)
  • Block Supports: Ensure consistent output in different PHP versions. (25240)
  • Add regression end-to-end test for the classic block initialization issue. (25169)
  • Update or retire deprecated colors. (25213

Build Tooling

  • Env: Update docker volumes during wp-env start. (24778)

Various

  • Update package-lock.json. (25223)
  • Update gradle-node-plugin to use actively maintained fork. (25208)
  • Bump @storybook/react major version. (25161)
  • Use WordPress Menu 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.. (25132)
  • Update modularity.md. (25007)
  • Remove Embeds for Facebook and Instagram. (24472)

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.

VersionLoading TimeKeyPress Event (typing)
Gutenberg 9.06.96 s28.99 ms
Gutenberg 8.96.97 s28.98 ms
WordPress 5.56.97 s27.54 ms

Kudos for all the contributors that helped with the release. 👏

#core-editor, #editor, #gutenberg, #gutenberg-new

Editor chat Summary: 9 September, 2020

This post summarizes the weekly editor chat meeting (agenda here) held on 2020-09-09 14:00 UTC. in Slack. Moderated by @paaljoachim.

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/ 8.9 release

Gutenberg 8.9 that was released on 2nd September and has been updated to 8.9.3.

Monthly Priorities

September monthly priorities.

Comment from @youknowriad
Most projects are properly on track and doing good progress.
Focus on Widgets screen, Navigation screen and Global styles.
The first experimental version of the Global styles UIUI User interface landed in 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/ or can be cost-based plugin from a third-party.

Task Coordination

@karmatosed

  • Working on options and iterating the options panel.

@ntsekouras

  • Add tags and filtering by author support in Query 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. ( 25005, 25149).
  • Experiments with Query block.

@andraganescu

  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. and code review.
  • Worked on the Navigation editor (making menu name editable).

@youknowriad

  • Working on 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. 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. to control the editor: 20588
  • Worked on the slash inserter behavior and the block search algorihm.
  • Plan to work on: Custom CSSCSS Cascading Style Sheets. support for Group block.

@paaljoachim

@mapk

  • 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 – helping to keep it moving forward. Designs are ready for implementation.
  • Query block – Exploring flows and settings.

@justinahinon

  • Working on documenting block editor packages.
  • A few PRs are on hold. Some are ready and will need a review before commit (25150, 25142, 24947). Others need refine/minor changes, plan to be done this week.

@aristath

  • Focus on performance & sustainability for FSE Themes:
  • Progressive rendering of blocks.
  • Load only styles for blocks that are used: PR 25220

@nrqsnchz

  • Working on designs and prototypes for allowing users to upload subtitles and other types of tracks to the Video block: 7673

@nosolosw

  • Details to merge 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. at edit-site: 24250
  • Helped with assorted reviews.
  • Next week, focus on follow-ups and pressing issues I should work on next.

@get_dave

  • Focused on triaging PRs marked as “Needs Testing” and providing fixes. Review on PR of transformation from the ‘audio’ shortcodeShortcode A shortcode is a placeholder used within a WordPress post, page, or widget to insert a form or function generated by a plugin in a specific location on your site. to the Audio block: 25114 whereby valid attributes for a source such as `mp3` and `wav` were ignored. (Could use some input.)
  • Check of PR which addresses an issue whereby the content of the HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. block isn’t parsed from its serialized form correctly: 25120 (Could use some input.)

Open Floor

Discussing Widgets

During open-floor @bph referred to the Widget screen: Adding a consistent wrapper issue. The answer: Theme developers can target the block in the block area with class names. Example: .my-widget-area .wp-block-latest-posts – 

On another issue with the comment Legacy Widget block: Identify the widget in the toolbar and/or settings sidebar @bph explored what will change for widgets. “I am utterly confused on what the future widget handling entails in respect to  widget registration, functions” and if there is a goal of feature parity. 

“The APIs you raise are probably something to look at and see whether support is possible, but we shouldn’t be expecting 1-1 parity”

  • The widgets themselves should work as close as possible with the new editor. The registration and other widget related functions should also be unchanged.
  • There will be incompatibilities in hooking into the widget editor itself as the new screen uses a completely different architecture
  • If there is anything that cannot be implemented then that will break backward compatibility. If it is possible to support things it should be attempted to be supported
  • It’s a different paradigm since it will just wrap the whole list of blocks. Widgets don’t map to blocks.
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Widgets vs. Core blocks, if a core widget like recent posts has a block equivalent, the core widget doesn’t appear in the inserter for the Widget screen. “Authors have the option to hide widgets if block equivalents are provided”. 
  • A theme developer declares block areas
  • All “clear evidence that we should be cautious with opt-in opt-out in Core” 

Check out the widget screen discussion.

Discussing A11yAccessibility 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) concerns.

@zebulan
Opened a PR to improve PanelBody’s add to give a summary when the section is collapsed. Intended to provide a solution to the a11y problems with prepublish checks and elsewhere. 25170 Needs a review. It complements: 24024

Noticed PRs involving UI changes/additions getting merged without getting any a11y feedback. Zeb had to pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” the a11y team to check after the PR’s have been merged.
Important to remember the checklist on the bottom in the PR template.

@mkaz
I’m not sure every UI request must require a11y feedback, shouldn’t we all be learning a11y techniques and proper usage. It should only be required for a new control. Using the base framework should be a11y compliance if it’s not something new.

@zebulan
The a11y team is working on a list of anti-patterns. Pointing people to something like that could help.
Perhaps modify the PR template checklist to include checkbox for “does my PR not use any 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) anti-patterns?”

There is discussion in this issue: 20877 in relation to creating a standard dropdown or popover. Which would really support the a11y effort.

Check out the Open Floor discussion Zeb began.

#core-editor, #core-editor-summary, #gutenberg

Editor chat summary: Wednesday, 2 September 2020

This post summarizes the weekly editor chat meeting on Wednesday, 2 September 2020, 14:00 UTC held in Slack.

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/ 8.9

@jorgefilipecosta announced Gutenberb 8.9 was going to be released in some hours.

The big highlight of the release is that Widgets moved out of experiments. On the FSE front, multiple FSE blocks were implemented and are now available for testing in the FSE experience (“Site Editor”). With regards to the widgets screen, more details are shared below.

Aside from these two focuses, Gutenberg 8.9 contains some small new features, multiple 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 some performance improvements.

Monthly plan updates

Global Styles

The PR that implements the Global styles sidebar on the edit site is now out of the draft state. https://github.com/WordPress/gutenberg/pull/24250. The PR allows us to have something more concrete to test the global styles mechanism and should probably be merged soon.

Besides the main global styles PR, @jorgefilipecosta said that we have proposals for font family and font-weight picking in https://github.com/WordPress/gutenberg/pull/24868 and https://github.com/WordPress/gutenberg/pull/24978.

Navigation screen and 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.

Regarding the navigation block task @andraganescu said:

They’re both being worked on. For the Navigation editor (screen) the goal currently is to bring it into a sort of MVP state (outlined in https://github.com/WordPress/gutenberg/issues/24875 and then take the same steps that we took for the Widgets editor.
Recently the editor got drag and drop into its version of the ListView.
The Navigation block is getting updates via the work on the editor.
One thing that is a bit of a blockerblocker A bug which is so severe that it blocks a release. now is the uncertainty around the “edit in toolbar” feature suggested for the LinkControl, feature which is also present in some of the editor’s interactions.

Widgets screen

Besides the big update that widgets are going to move out of the experimental state on WordPress 8.9, @andraganescu added that call for testing post in progress, and it should soon make it on the make coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site).

Full Site Editing

Regarding full site editing @ntsekouras, is experimenting with the query block. Namely, adding tags, order, and some orderby support and transform multiple heading blocks to list or paragraphs.

Monthly plan preview

@annezazu shared a small preview of the monthly plan for September:

  • Global Styles & Editor focused APIs: hope is that work on editor focused APIs can be wrapped up in the month ahead.
  • 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. Screen: launched out of experimental, hoping for lots of feedback, working on an updated design, and have a nice set of a11yAccessibility 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) issues to work through.
  • Navigation Screen: discussing blockers to this being moved out of experimental & working on various items including nestinga fresh designenabling edit links in toolbar etc.
  • Full Site Editing: focused on milestone #2.

Task coordination

@jorgefilipecosta

Shared the following update:

Last week I was involved in helping the editor side tasks of WordPress 5.5.1. I reviewed multiple global styles related PR’s and shared some insights in the discussions that were happening. And I proposed the font family and weight picking mechanism.

Next week I will continue the reviews on global styles related PR’s. I will try to take the open PR’s I have to the finish line, and I will try to have a prototype of how to use and load third-party fonts.

@youknowriad

  • Working on 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. APIs to control the editor.
  • Adding spacing controls to the group block
  • Custom CSSCSS Cascading Style Sheets. for the group block (depending on the available time)

@mapk

  • Finalized Widget Screen design iterations.
  • Digging into Query block.
  • Reviewed and helped iterate on text-only topbar.

@itsjonq

@itsjonq shared the following update:

I’m continuing to work on the G2 Components project. Currently focusing on creating (also supporting the creation) of larger pieces.
One of the ways this is manifesting is through prototyping more complete UIs/experience (e.g. Navigation, and soon FSE/Global styles).
Also exploring how G2 components could be used in WP-Adminadmin (and super admin). Another focus to evaluate potential integration into Gutenberg (via `@wordpress/components`).
One of the results from this is splitting parts from the core system so that smaller chunks can be migrated (e.g. Style system)I’ve continued to host Zoom session calls + blog G2 components updates on the blog:
https://g2components.wordpress.com/Also updating the documentation as I go:
https://g2-components.com/As always, open to feedback + suggestions! From UIUI User interface designs to workflows, to documentation, etc…
I’ve received a few already, which have been lovely.

@michaelarestad

@nosolosw

Shared the following update on the agenda:

  • This week: I’ve made progress on adding an initial prototype for the global styles sidebar in the Site Editor. Just today the PR moved from draft state to open for reviews. It still needs some tweaks, but, fundamentally, it’s a candidate for merging. I’ve also been helping here and there with feedback and reviews.
  • Next week: keep pushing this work forward.

Open floor

Justify use of “Needs… Feedback”

@isabel_brison wrote on the agenda post:

I’m wondering if we should try/encourage adding comments to justify use of “Needs… Feedback” labels in Gutenberg, as it’s not always obvious which aspect of the issue/PR needs feedback. It would help if the person adding the label elaborated a little on where feedback would be useful.

@jorgefilipecosta said it makes sense that when someone uses a feedback label to also include a comment saying exactly what feedback is needed. As sometimes, the discussions get big passed by many topics, and it is not easy to know what actionable feedback is needed.

@youknowriad said that adding process over process is just raising the bar for contribution. And added that it’s also fine to ask “Why did you add the Needs thing feedback”?

@mapk referred he noticed that many designers do list out the feedback they’re looking for when a design is proposed. @jorgefilipecosta said that we should probably expand that practice to non-design PR’s.

#block-editor, #chats, #core-editor, #core-editor-summary, #gutenberg, #meeting-notes

What’s new in Gutenberg? (2 September)

The big focuses throughout this release cycle were full site editing (FSE) and the widgets screen. On the FSE front, multiple FSE blocks were implemented and are now available for testing in the FSE experience (“Site Editor”). With regards to the widgets screen, more details are shared below.
Aside from these two focuses, 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/ 8.9 contains some small new features, multiple 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 some performance improvements.

Widgets moved out of experiments

One of the objectives of WordPress 5.6 is to allow using blocks in widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. areas. This is a complex task, and for now there is no decision on whether the new screen should be available for all users or a subset of users. Your feedback may help weigh the options.

In Gutenberg 8.9, the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience.-based widgets screen is enabled by default and replaces the default WordPress widgets screen. Themes and plugins are able to opt out of this screen by calling remove_theme_support( 'widgets-block-editor' ) or by using the gutenberg_use_widgets_block_editor filter respectively.

Your testing, feedback, and insights are very useful to inform the direction of the next iterations. If you come across any bugs, please submit a new issue in the Github repository.

8.9.0 🇧🇯

Features

  • Enable the block-based widgets screen. (24843), (24087)
  • Add character count to the info panel. (24823)
  • Latest Post Block: Allow adding links to featured images. (24548)
  • List block: Add color controls. (21387)

Enhancements

  • Disable the tools menu while the code editor is enabled. (24923)
  • Add picture keyword to the Image block. (24755)
  • Adding a maximum height to the long blocks previews. (24493)
  • Add “read more” keyword to the More block. (24794)
  • Improve the UXUX User experience of inactive widgets area on the widgets screen. (24790)
  • Trim whitespace from rendered widgets. (24789)
  • Block Directory: Explicitly close the inserter on block add. (24709)
  • Make strings translatable in block patterns. (24647)
  • Improve the UIUI User interface of the custom gradient pickers. (23802)
  • Adds suggestions for categories and formats to link controls. (22600)
  • Clarify the font size control label. (24619)
  • Convert all px values in front-facing styles to relative (em) units. (24523)

Bug Fixes

  • Fix infinite 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. in the Disabled component. (24935)
  • Fix wp-env start for non-english WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. sources. (24884)
  • Invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. structure on the widgets screen. (24866)
  • Fix 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. flickering caused by the block preview border. (24739)
  • Don’t use an offset when dragging using a draggable chip. (24707)
  • Fix Image alignment controls styles in the Latest posts block. (24655)
  • Improve the focus state of the tags control remove button. (24632)
  • Fix Crash after undoing with the top toolbar on. (24629)
  • Avoid double borders on the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. boxes panels. (24627)
  • Fix Inline text-color regex edge-case. (24621)
  • Fix inserter z-index. (24614)
  • Missing selected block highlighting in the list view. (24609)
  • Fix the Pullquote block text color after unsetting the main color. (24600)
  • Fix style specificity for Button blocks with outline style and background colors. (24599)
  • Remove references to $default-font from front-facing styles. (24567)
  • Center-align the block variations buttons. (24547)
  • Fix categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. select in QueryControls component. (24516)
  • Image Block: Prevent Alt and caption written during image upload from being discarded. (24471)
  • Correct the Unicode character used to represent the macOS Control key. (24452)
  • Fix undefined $block_type->supports PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 error. (24411)
  • Fix adminadmin (and super admin)-theme colors in the editor canvas. (24408)
  • Limit the number of fetched tags to avoid infinite queries. (23841)
  • Fix error when inserting a 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.) with an apostrophe. (21693)
  • Fix the alignment of the trashTrash Trash in WordPress is like the Recycle Bin on your PC or Trash in your Macintosh computer. Users with the proper permission level (administrators and editors) have the ability to delete a post, page, and/or comments. When you delete the item, it is moved to the trash folder where it will remain for 30 days. post button. (24889)
  • Make legacy widgets support for non-class-based widgets. (24861) (24792)
  • Remove WP_Widget_Block from the legacy dropdown list. (24787)
  • Fix isSavingWidgetAreas selector. (24788)
  • Inserter: Update the search form placeholder text when changing tabs. (24697) (24802)
  • Avoid lossy HTML entities encoding by setting charset. (24645)
  • Embeds: Don’t transform into specialized embed block variation if it’s not registered. (24559)

Performance

  • Fix getBlocks selector performance issues causing typing lags on Gutenberg 8.8.0. (24835)
  • Preload widgets on the widgets screen. (24855)
  • Only request the required fields to populate the parent page list. (23637)

New APIs

  • Core Data: Implement _fields data reuse for entities. (19498)

Experiments

  • Site Editing: Blocks
    • Add Post Comment block. (24781)
    • Add Post Comment Date block. (24854)
    • Add Post Comment Author block. (24824)
    • Add Post Hierarchical Terms Block. (24091)
    • Adds icons and descriptions to Post blocks. (24603)
    • Make Site title block render a link. (24725)
    • Add heading level toolbar to the Site title block. (24758)
  • Site Editing: UI
    • Alert when trying to leave the Site Editor with unsaved changes. (24659) (24719)
    • Update Template Part Block Placeholder Button Styles. (24633)
    • Template Part block – add border states in the editor. (24498)
  • Global Styles and 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. APIs:
    • Allow enabling/disabling custom colors from theme.json config. (24761) (24932)
    • Rename features.colors to features.color. (24933)
    • useEditorFeature: Take block context into account. (24416)
  • Navigation block and screen:
    • Add Post, Page, Category and Tag variations to Link. (24670)
    • Add block inspector to nav screen. (24669)
    • Add opt-in Navigation block rendering. (24503)
    • Support drag-and-drop for submenus of navigation blocks. (24479)
    • Fix invalid textarea markup. (24641)
    • Add unit tests for edit-navigation store. (24681)

Documentation

  • Document Components
  • Update tutorial Creating a block-based theme. (24736)
  • Correct BoxControl values in README examples. (24717)
  • Add ToggleControl at related components section in FormToggle documentation. (24636)
  • Typos and tweaks: (24857), (24811), (24695), (24650), (24628).

Code Quality

  • Keep the default color CSSCSS Cascading Style Sheets. variables for npm package consumers. (24890)
  • Refactor components as functional components:
  • Refactor and move drag and drop geometry code. (24715)
  • Only update state if we have a valid reference. (24496)
  • Add state for storing dragged block client ids to block-editor store. (24782)
  • Remove commented-out blank line. (24858)
  • Simplify gutenberg_widgets_init when $hook === ‘widgets.php’. (24793)
  • Refactor block drop event handlers into a single hook to support drag and drop in List View. (24649)
  • Move DOM utility functions from wordpress/blocks to wordpress/dom. (24618)
  • Fix ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. warning on text color formatter. (24686)

Build Tooling

  • Update package lock file. (24815)
  • Update the minimum version and the tested up to flag of the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. (24693)
  • Build: Make the watch rate slower to avoid using a lot of CPU while developing. (23998)
  • Fix Performance Tests on CI. (24925)
  • Add tests for slashing behavior. (24785)
  • Add permissions PHPUnit tests. (24784)
  • Update browserlist dependency. (24756)
  • Allow local Prettier configuration to take precedence in the recommended ESLint configuration. (24590)

Performance Benchmark

Gradual changes in the editor have made its rendering pipeline more asynchronous. As a result, the usual metrics (loading time, typing time) that we collect in the performance benchmarks may have not always represented the performance gains and losses experienced by some users.

We are improving the way times are measured to account for the more async nature of the editor rendering. We will update this post with performance results once we are confident that they accurately measure the performance of the editor.

The synchronicity changes in question only affect Gutenberg 8.8 and 8.9.
The numbers shared for previous releases are still an accurate way of measuring the editor’s performance.

#core-editor, #editor, #gutenberg, #gutenberg-new

What’s new in Gutenberg (August 19)

With the release of WordPress 5.5 (🎉) comes a new release of 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/! Gutenberg 8.8. Contributors have continued to squash bugs, refine experiences, and make progress on several big projects.

Full site editing has progressed with updates to Global Styles, the Post 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. suite, and Template management. The back-compatibility of the new Widget Screen was improved. The Widgets screen is a project that’s part of a wider effort to add more block enabled sections to the WordPress experience.

This release also saw important 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) and mobile improvements to user-interfaces like the Toolbar, navigation menus, and Popovers.

All this and more in the wonderfully jam packed change log below:

8.8.0 🇳🇬

Enhancements

  • Copy: Use “block patterns” strings consistently. (24457)
  • Remove hardcoded color from the Recent Comments block. (24410)
  • Remove hardcoded styles from the Separator block. (24366)
  • Block toolbar: Split switcher from mover and simplify styles. (23971)
  • Use the block label 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. for BlockTitle component. (23847)
  • i18ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.: Translate all strings inside the Large 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. Button block pattern. (24499)
  • Block Movers: Use a bigger mobile touch target. (23761)
  • Block Movers: Use a bigger visible focus rectangle. (23760)
  • Update the top toolbar buttons color. (24420)
  • Remove editor styles from front-facing stylesheets. (24439)
  • Block Toolbar More Menu: Switch back to the vertical ellipsis icon. (24426)
  • Removes hardcoded body text color from some block patterns. (24424)

New APIs

  • Support the default block classnames in dynamic blocks. (24546)
  • Support the custom classnames hook in dynamic blocks. (24483)
  • Stabilize the accessible Toolbar component and deprecate the old usage. (23316)
  • Add store icon to Icons package. (23867)
  • Allow POST requests in <ServerSideRender>. (21068)

Bug Fixes

  • Fix inserter expecting experimental settings to exist in the context. (24554)
  • Fix Image block caption jumps on Safari. (24540)
  • Fix Media Text block: Always show images on top on mobile. (24468)
  • Hide Preview menu on small viewports. (24537)
  • Fix canInsertBlockType selector returning true for blocks that don’t allow inner blocks. (24514)
  • Fix the huge font size on the editor when using the default font sizes presets. (24492)
  • Fix Cover block: Impossible to reset the minimum height value. (24490)
  • Fix Post preview button only appearing on small screens. (24487)
  • Fix deduplication of style rules for server-side block support flags. (24486)
  • Fix the quick inserter results limit for block variations. (24481)
  • Fix tiny editor preview when using Mobile or Tablet options with metaboxes enabled. (24478)
  • Fix custom gradient picker unable to change predefined gradients with hex colors. (24470)
  • Fixing duplicated wp-block classes in block-list. (24466)
  • A11yAccessibility 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):
    • Make the inserter behave as a popover. (24429)
    • Fix incorrect aria description in the Block List View. (24533)
    • Add arrow navigation in Preview menu. (24465)
    • Add arrow navigation to Warning dropdown menu. (24333)
    • Add an example to the buttons block to avoid focus loss issue. (24434)
  • Fix rendering non-Latin characters on aligned Cover blocks. (24447)
  • Remove --wp-admin-theme-color reference from frontend styles. (24436)
  • Prevent links from being focusable inside the Disabled component. (24397)
  • Image Editing: Fix alignment of aspect-ratio button. (24343)
  • Fix retrying of post-processing of edited images. (24081)
  • Set error state when there is an upload error in during file upload. (24017)
  • Block Directory: Decode entities in block title & description. (24172)
  • Preview menu: Remove redundant “opens in a new tab” hidden text. (24427)
  • Fix uploading PDFs in the File block. (24318)

Experiments

  • InnerBlocks: Introduce prop to specify render callback for each block. (24232)
  • Navigation:
    • Display children of inner block controllers in the block navigator. (24083)
    • Add font-size support to the the Navigation block. (24531)
  • Template Parts and saving flow:
    • Move the title to the block toolbar. (24450)
    • Fix Template Part renaming error. (24500)
    • Fix Site Title Save Bug. (24302)
  • Post Blocks:
    • Post Tags block: Fix 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. where no tags are rendered. (24082)
    • Post Tags block: Support color, font-size and line-height customization. (24069)
  • Full Site Editing:
    • Load php files only if experiment is enabled. (24182)
  • Global Styles:
    • Consider any user changes to global styles as publishable. (24293)
    • Add support for more style properties in the global context. (24298)
  • Widgets screen:
    • Refactor the widgets screen to rely on dedicated endpoints. (24290)
    • Make the list of widgets excluded from the legacy 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. block extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. via a filterFilter Filters are one of the two types of 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.. (24271)

Documentation

  • Add undocumented global styles blocks & properties. (24421)
  • Remove “experimental” from title of editor filters. (24382)
  • Add instructions for disabling the Block Directory. (24357)
  • Remove duplicate questions in FAQ. (24355)
  • Indicate custom-fields support is required for registering metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.. (24325)
  • Add block directory submission guidelines. (23545)
  • Typos and tweaks: (24511) (24244) (24491) (24361) (24340)
  • Update the “Create a Block” Tutorial. (24545)
  • Getting started: Add a MAMP section. (24241)

Code Quality

  • Refactor embed block to single block with block variations. (24090)
  • Upgrade ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. version to 16.13.1. (21289)
  • Update lodash to 4.17.19. (24401)
  • Register the block attributes server-side for blocks with support flags. (24400)
  • Refactor components as functional components:
  • Remove unnecessary selector from the PostTitle block. (24418)
  • Remove unnecessary ad-hoc class application for dynamic blocks. (24223)

Build Tooling

  • Run wp-env start before PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 unit tests in package scripts. (23797)
  • Upgrade eslint-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/ or can be cost-based plugin from a third-party-jsdoc to latest version. (24586)
  • Add full parameters for emulateNetworkConditions. (24144)
  • Add an end-to-end regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. 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. test for the “Browse All” inserter button. (24396)

Performance Benchmark

Update: Gradual changes in the editor have made its rendering pipeline more asynchronous. As a result, the usual metrics (loading time, typing time) that we collect in the performance benchmarks may have not always represented the performance gains and losses experienced by some users.

We are improving the way times are measured to account for the more async nature of the editor rendering. We will update this post with performance results once we are confident that they accurately measure the performance of the editor.

The synchronicity changes in question only affect Gutenberg 8.8 and 8.9.
The numbers shared for previous releases are still an accurate way of measuring the editor’s performance.

A big thanks to all the wonderful contributors that helped with this release! 👏

#core-editor, #editor, #gutenberg, #gutenberg-new

Editor chat Summary: 12th August, 2020

This post summarizes the weekly editor chat meeting agenda. Held on 2020-08-12 14:00 UTC in Slack. Moderated by @paaljoachim.

WordPress 5.5

WordPress 5.5 was released on 11th August.

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/ 8.7

The latest release of Gutenberg, version 8.7 was released 5th of August.

The Monthly Priorities

The monthly plan for August.

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

Scroll back to Navigation block chat.

Task Coordination

@zebulan

@youknowriad

  • I’ve been working on the server-side support for 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. support flags.
  • Upgrading some libs (ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/., lodash)
  • I’m planning to focus more deeply on the “Editor controlling APIs”
  • I’ll probably spend some time on the forums to check 5.5 feedback and issues.

@aristath

  • This week I’ve been working on prep work regarding block styles and FSE/Global-Styles: Removing hardcoded colors from block-styles, separating editor & front-facing styles, converting absolute units to relative etc.

@ntsekouras

@zieladam

@mapk

  • Accordion block. I’ll have some style variations up this week.
  • Topbar labels for icons with @tellthemachines.
  • New icons for Post blocks.
  • 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.-block editor designs (Figma file).

@annezazu

@joen

  • Catching up and reviewing. Always happy to review.

@mcsf

  • Helped @ntsekouras land his changing of Embed blocks to block variations.
  • Been reviewing PRs such as refactors or Global Styles-related items.
  • Triaging issues.
  • Team support.

@shaunandrews

@sageshilling

@q

  • Focus on experiments on evolving the Editor UI.
  • Taking a deep look into wordpress/components, and seeing how it can be improved to address many pain-points + missing features we have today, and setting up the UIUI User interface layer for success for the future. One of the many drivers for this is my involvement in improving editor Design Tools, which relies very heavily on the UI layer. I’ve started sharing some of these updates with folks via Zoom sessions, GithubGitHub GitHub is a website that offers online implementation of git repositories that can 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 be the repository owner. https://github.com/ posts, and most recently, a dedicated blogblog (versus network, site) (published yesterday) https://g2components.wordpress.com/
  • I’m planning on hosting another collab Zoom session today.

@noahtallen

  • Working on moving Global Styles forward and how that looks/feels within the editor (will be getting these into an issue soon) [Full Site Editing]
  • Moving the first iteration of Multi-Entity Saving forward with engineering [Full Site Editing]

Comment by @paaljoachim

  • Let’s be sure that any Full Site Editing UI adjustments are also reflected back to the regular Gutenberg content creation where it is applicable to do so.

Open Floor

From the agenda post.
@zebulan brings focus to the work done by @aristath on the usage of relative units (rem, em) in relation to block styles in themes and removing hardcoded colors. PRs.
https://github.com/WordPress/gutenberg/pulls/aristath

@psykro
Getting workshops up on learn.wordpress.org. One of the workshops is a beginners guide to block development, following by a group discussion. It would be helpful to have Gutenberg developers present. We need feedback. The group discussion details (including date and time) are on the 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/. 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. event – https://www.meetup.com/learn-wordpress-discussions/events/272503390, the actual workshop you can watch any time on learn.wordpress.org.

@aristath
Supporting prefers-color-scheme queries.
Gutenberg has no option to set a Dark scheme in relation to user preference and a11yAccessibility 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) issues. Discussion: prefers-color-scheme media-query
@paaljoachim
Check the experimental design tools by @q as color schemes is one of the areas he is experimenting with.

@mkaz
“Remove Embeds for Facebook and Instagram”
https://github.com/WordPress/gutenberg/pull/24472
Basically Facebook is changing the FB and Instagram embeds on Oct 24, so older embeds will no longer work. So at what point should we remove from WP?
@paaljoachim
Brought up the above issue during the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Dev chat in the #core channel on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Link to discussion: https://wordpress.slack.com/archives/C02RQBWTW/p1597265852021400

@itsjusteileen
Andrei are there notes or follow up on the Nav meetings?
@andraganescu
Not yet.
@itsjusteileen
The idea being theme authors need to look at building progressive enhancements, and keeping up with this feature even if it is exploratory would have benefit to FSE and communicating with the theme team. I can take a look at today’s meeting then and go from there.
@paaljoachim
Back scroll link to Navigation meeting held in #core channel on Slack.

#core-editor, #core-editor-summary, #gutenberg

Editor chat summary: Wednesday, 29 July 2020

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, July 29, 2020, 14:00 UTC.

WordPress 5.5 RC 1

The first release candidate for WordPress 5.5 is now available. This is an important milestone in the community’s progress toward the final release of WordPress.

Thank you to all of the contributors who tested the 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. releases and gave feedback. Testing for bugs is a critical part of polishing every release and a great way to contribute to WordPress.

Project Board For WordPress 5.5

The remaining issues are located in the Project board.

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/ 8.6

Gutenberg 8.6 was relased on 22nd July.

Monthly Plan

What is next in Gutenberg for July.

Task Coordination

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

@annezazu

@ntsekouras

Refactor embed 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 be a single block ( with block.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. ) and block variations. (https://github.com/WordPress/gutenberg/pull/24090)

@sageshilling

Working on coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. media block editor proposal

@shaunandrews

Design work continues for the new editor sidebar

@mapk

@itsjusteileen

Testing in FSE. Moving to a new machine and will need to give @paaljoachim, @mkaz, and @Noah Allen dev environment tutorial a run on setting up from scratch for testing Gutenberg.

@nrqsnchz

  • Merged the last remaining PRs for Block Patterns and tested across Core default themes.
  • Been helping with testing and feedback on various a11yAccessibility 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)-related issues

@mcsf

  • WP5.5: Review fix/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. PRs, review/help with dev notesdev 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 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.
  • Review many PRs or comment in issues
  • Try to improve Docker performance on macOS (24001)
  • Support some other contributors at an individual level

@andraganescu

@michael-arestad

I’m working on a flow for creating a template from scratch – Currently, I’m  exploring “designing” a layout via document-level grid. I’m also planning a jam session or two next week. 

@zieladam

  • Focused on in-toolbar link editing (#24021)
  • Investigating the way forward for the widgets editor
  • Working on fixing e2e tests on the AutosaveMonitor fix in #23962

@itsjonq

  • Continuing with Design Tools Efforts (in general)
  • Focus lately has been advancing @wordpress/components in the spirit of the new “G2” designs. Approaching it systematically from foundations (much needed IMO) rather than applying tweaks on top.

@zeb

  • Got a PR merged that moves the reusable block’s “Convert to regular blocks” button to the block toolbar! https://github.com/WordPress/gutenberg/pull/24066
  • A few days ago I created a PR to implement an `itemWrapper` prop for `InnerBlocks` that allows child blocks to each be wrapped with a given element. It’s a rather significant change and there may be better ways of implementing it, so any technical feedback and ideas are much appreciated! https://github.com/WordPress/gutenberg/pull/24232

@isabel_brison

  • I’m working on adding labels to the editor icon buttons (10524 and 15311). I’ve done an initial PR to add an option to show labels, but it only affects the post editor for now. I think we’re going to need this functionality in the site editor too, and am wondering what would be the best way of having a setting that works across both editors. Thoughts welcome!

Open Floor

Patterns and WordPress 5.5

@joyously asked about the pattern, are they part of GB or part of WP? The reason is that the images are stored on .org, and the text goes through .org translations. @youknowriad clarified that Patterns live in Core codebase and the images are hosted in wp.org like the block examples.

Cherry picking from Gutenberg 8.7 for WordPress 5.5

@jeffpaul asked are there any 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 performance improvements that are planned to be cherry-picked from Gutenberg 8.7 to merge into WordPress 5.5? To prepare WordPress 5.5 Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page.. @youknowriad mentioned that the potential addition fixes might not be worth mentioning.

Documentation “Keeping up with gutenberg” Index

@annezazu shared about a new page in the core handbook called “Keeping up with Gutenberg”. It’s an index of Gutenberg related posts from various Make blogs to make it easier to follow development. Feedback is very welcome to improve it. Props to @bph and @williampatton who led these efforts. @swissspidy raised if there is a way we can somehow automate that list of posts? as currently its manually curated and seems tedious to maintain.

Galleries as composed image block

@andraganescu raised @Zeb added https://github.com/WordPress/gutenberg/pull/24232 and @noisysocks raised the PR for discussion here as it affects some implementations that count on InnerBlocks including the blocks in navigation feature and the implementation of galleries as composed image blocks

Some discussion around wrapper for the inner block but no decision. Further discussion to continue on the PR for introducing prop to specify the wrapper

Missing post update action

@paaljoachim highlighted the issue of missing “Update post” action when there’s an autosave.

#meeting-notes, #core-editor, #editor, #gutenberg

#core-editor-summary