This post summarizes the weekly editor chat meeting on Wednesday, 20 October 2022, 14:00 UTC held in Slack.
WordPress & 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/ releases
WordPress 6.1 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). was released yesterday from the editor side things are going smoothly.
WordPress 6.0.3 & 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 14.3.1.
There were some security issues fixed and included in the 6.0.3 release and release for all the lower versions with auto-updates. Some of these fixes were editor related, so a new version of Gutenberg was also released 14.3.1.
Please ensure that all your websites have Gutenberg and core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. updated!
Key project updates
There is a big PR in progress that redesigns the UI User interface, introduces a browse mode, and makes things much more intuitive for end users. Please leave your feedback at #44770.
Building with patterns project
The Gutenberg team merged a redesign to the pattern inserter #44028. With the aim of making it more user-friendly.
@annezazu shared the following on the agenda:
Before a 6.2 roadmap post similar to the ones that have come before is shared, lots of work has been done to revamp the following issue to make it the source of truth for the months ahead: https://github.com/WordPress/gutenberg/issues/33094 If you’re looking for ways to help in the coming months, please take a look at this issue and know it’ll be kept up to date! You’re also welcome to join a hallway hangout in the FSE Outreach Program
Please have a look into the issue and in case there is any feedback leave a comment!
Thank you @annezazu for sharing this with us ensuring the issue will keep being updated!
It is good to have a single issue as the main source of truth for the work that will be done in the coming months.
Let’s try our best to ship the things there, and wrap up the customisation/ site editor phase.
Collaboration with the a11y 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) team
@annezazu shared this topic on the agenda:
Wanted to call out a great collaboration between the 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) team and core editor team in this issue: https://github.com/WordPress/gutenberg/pull/44028 It’s worth reviewing to learn from and was called out specifically by @alexstine (a11y team member) saying, “This needs to be highlighted as a good working example. It took much longer, but saves work in the future to go back and make it right.”
@jorgefilipecosta thanked @annezazu for bringing this topic to chat and thanked @alexstine for highlighting this collaboration, congratulating all the people involved in that issue.
Feedback on the Closing List view after selecting 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.
@alexstine said the following on the agenda:
This is one I could use some feedback on.
This issue has been stale for some time. I am never closed to hearing other ideas, I just would really like a way forward so everyone can maximize the use of the list view since it gets more accessible every release. If my suggestion would not work for you, what would?
@jorgefilipecosta and @ndiego shared feedback/insights on the pull request.