This post summarizes the weekly editor chat meeting (agenda for 9th of August meeting) held on Wednesday, August 12 2023, 03:00 PM GMT+1. in Slack. Moderated by @paaljoachim.
WordPress 6.3 was released on the 8th of August.
Gutenberg 16.4 RC1 is available for testing.
Final version of Gutenberg 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/ 16.4 will be released Wednesday.
A big thank you to @mikachan for handling the Gutenberg plugin 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 release.
Sarah is using this checklist.
Key project updates:
The WebFonts API 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. – work is currently underway on the new Font Library. The initial Fonts Library: Backend PR is currently being worked on, and there are more related issues in [Tracking] Fonts Library. Stage 1: Google and Local fonts. It would be great to get more reviews on the backend PR, and also some more input on this discussion about where to store the list of Google Fonts. Thanks!
I’m working on accessibility 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) enhancements around the Navigation block 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 try and address some outstanding concerns. Also exploring ways to improve the responsive layout of the Navigation block. Still at the thinking/exploration phase. Also re-focusing a bit on allowing custom labels for items in List View.
I’m Andrei, I’m one of the developers of the Blocksy theme.
Question: is there way to bypass namespacing the styles for some of the $styles from the editor settings?
From the discussion that happened a new issue was created:
Allow inserting un-namespaced editor styles into the iframe.
I wonder if it might be possible to shine some light on this discussion:
Query Block doesn’t seem to provide settings to a Post Template in a pattern/template-part
I tried to use synced patterns in the
Post Template block but there seems to be a disconnect on the front-end as long as it’s a pattern.
I registered some block variations for the core Core is the set of software required to run WordPress. The Core Development Team builds WordPress./button block and added isDefault: true to one of them, but when adding a new core/buttons block in the editor that variation is not used as the inserted button.
Issue created here: core/buttons does not respect isDefault for core/button variation.
Here is an associated issue: core/button variations doesn’t appear in core/buttons inserter.
Read complete transcript