Editor chat summary: Wednesday, February 15, 2023

This post summarizes the weekly editor chat meeting on Wednesday, 15 February 2023, 14:00 UTC, held in Slack.

General Announcements.

Gutenberg 15.1 was shipped last week.

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/ 15.2 was planned for later in the day.

WordPress 6.2 release process is going smoothly, and we had beta two the day before the chat.

Key project updates.

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., Site editor, and templates

@jorgefilipecosta shared that now we have a modal that allows us to choose between starting blank or starting from the fallback when creating a new template. https://github.com/WordPress/gutenberg/pull/46248

Soon we will also be able to choose from a set of patterns: https://github.com/WordPress/gutenberg/pull/47322

On the navigation in the 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. front, We are already showing the navigation items on the sidebar using the same components used by the navigation block. Now some enhancements make this system work for more complex menus with page lists etc. https://github.com/WordPress/gutenberg/pull/47853.

Style Engine

@jorgefilipecosta said that some updates in progress are making its code simpler and modular, which he hopes will make things easier for advanced block creators and extenders https://github.com/WordPress/gutenberg/pull/47908.

Phase two updates

@annezazu compiled a summary of the current status of phase 2 work https://github.com/WordPress/gutenberg/issues/33094#issuecomment-1421394281. From now on to improve the signal-to-noise ratio, this summary will be monthly https://github.com/WordPress/gutenberg/issues/33094#issuecomment-1430358353.

Task coordination.


Last week:

Next week;

  • Iterate and merge my current PRs related to the navigation sidebar.
  • Plan on also fixing some issues on the OffsiteNavigation editor that are affecting the navigation sidebar


Open floor


i would hightlight a very annoying 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. on Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop.
Editor preview is different from the frontend view
This issue was first reported in March, 2021, and is still accurate.
That impacts WooCommerce Product Blocks (this block extends the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. one). The demo video was added by the WC Team within that issue.
> could you please add the bugfix as target on 6.2 ??? I know everyone is busy, but, i feel this one is important to make the Query Loop Block more usable… it impacts many of us.

@jorgefilipecosta pinged @ntsekouras; that is more inside the query loop work.


I also just wanted to share an issue because I’m hoping to get some context. https://github.com/WordPress/gutenberg/issues/47990

Currently there doesn’t seem to be a mechanism to leverage the global styles system for any custom settings. Such as for example the “overlay” color in the cover block.

This is starting to become a major limitation when building custom blocks and I’m just wondering if this has been an intentional choice or whether this is something that can be opened up more.

@jorgefilipecosta said applying an overlay color may require additional logic for some blocks. With CSSCSS Cascading Style Sheets., only background and text colors can be applied. A solution to this problem would involve an 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. that maps color applications to a specific CSS selector. Such an API could extend elements like the link color or take another form. Balancing this addition with other potential future features is necessary.

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