This post summarizes the weekly editor chat meeting (agenda here) held in Slack. Moderated by @andraganescu.
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/ 11.5 RC One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). launched today (Sep 8)
@mikeschroder released Gutenberg 11.5 RC. You can take it for a spin from here.
Important resources for the incoming period of time
@priethor added some details about where we should look for guidance around the incoming updates to WordPress in light of the 5.9 release:
There will be an upcoming What’s Next in Gutenberg post based on the preliminary road. It’s worth noting the “What’s Next” intent is to highlight issues where contributors can help, whereas the high-level plan is defined in the preliminary road post.
Key Project Updates
@get_dave shared this week’s update:
From mobile, @hypest offered the updates:
- 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. picker search.
- Inline previews for YouTube and Twitter embeds.
- Alignment options for embeds.
- New experimental Gallery block.
- Embed block.
- GSS Font size, line height, colors.
@mciampini shared some updates from the folks working on the components package:
Feel free to add items to this post if you weren’t able to make the meeting.
- Updated documentation to replace
withSelect HOC references with
- Worked with Riad to fix code data issue with
include query parameter.
- Checked on approved PRs, merged some, and left comments on others to see if authors have time to address the feedback. (Sorry if you received more notifications than usual)
I would appreciate feedback on the following PRs:
- 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. Fetch: Improve isMediaUploadRequest check
- FSE: Add basic support for child themes
- During the last week I updated the design of the mosaic view, I iterated on the engine to allow blocks to be aware of global styles, I proposed the PR to enhance the design of the new color picker and I did multiple PR reviews. I also started the effort to replace tinycolor with colord.
- For the next week I place on continuing the color library replacement, Iterate on the color picker design and pick another task related to the global styles new design.
@mciampini I plan on:
- In the area of alignments: landed a PR that makes the wide control only available if the theme provides a wide size and prepared another for fixing floats (left, center, right) for blocks that are not part of a container.
Will PHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher minimum required version change in WordPress 5.9?
@anil (Anil Sardemann) asked about the future min. PHP requirements of 5.9. @hellofromtonya explained that there are no plans to change the minimum supported PHP version in WordPress 5.9 since still more than 5% of WordPress runs on PHP 5.6.
Help with the future of Block Theme Switching
@annezazu brought more attention to the FSE Program Exploration: Help with the future of Block Theme Switching. This is a very new approach in that it’s all about gathering insights to help shape the potential designs rather than testing a specific flow. It’s neat to be able to be involved this early in solving a problem. Check it out, share your thoughts, and get creative!
Help needed with review
@faizan asked for a review on his patch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. on Ticket 50074