This post summarises the weekly editor chat meeting (agenda here) held on 2022-09-21 14:00 UTC in Slack. Moderated by @get_dave.
- Version 14.1.0 of the 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/ 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 was released. You can read what’s new in Gutenberg 14.1.0.
- Following this, Minor release 14.1.1 was released 2 days ago to fix a bug 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. with searching for blocks.
- Zooming out a bit, the WordPress 6.1 release schedule is proceeding.
- Beta 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 was supposed to be yesterday but it turns out that’s been moved to today (21st September 2022).
- Just in case it moves again, you can check out the full development cycle plan.
- The last version of Gutenberg that made it into WP 6.1 was 14.1 RC1.
Updates based on updated scope for site editing projects
The following items were shared by folks to update us on what work is in progress or where help is needed:
@alexstine (not present – shared from agenda):
- Working on
- the FSE Program Testing Call #17: Guiding the Gutenberg Gallery (everyone is welcome to participate).
- co-core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor triage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. duties for 6.1.
- a Core related roadmap companion post for Make Core with a few folks.
- a core editor improvement post on the various design tools coming to 6.1.
- a draft of an 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) improvements roundup for 6.1.
- Lots of writing, testing, and sharing info with folks where I can!
@mamaduka – I am planning to start work on the new entity permission selector; it would be like `canUser` but easier to use with entities.
- I’m switching focus to work on bugs. Found some interesting issues around LinkControl and also 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..
- Continuing to iterate in the background on using slugs for Navigation blocks, and also ability to add Custom Labels to the List View.
- I’m really keen on trying to review the latest roadmap for 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. and love the organized outline of features, but almost feel overwhelming and hard to know where one might focus on reviewing and providing feedback. So, any guidance is appreciated.
- @hellofromtonya responded to say: right now, it’s blocked until the re-architecturing work is done.
- For 6.1 we, Michael and I, added the label
needs-dev-note to quite a few PRs in our first round of triaging.
- Next steps is to add them in topical order to the Dev Note tracking issue. It might take another few more days to finish it.
- Please continue to leave comments on the issue, or the PRs. I’ll catch up with you quickly.
The full Open Floor discussion is available on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. It was a quiet meeting…
Critical Bug Reporting for WordPress 6.1
As @annezazu alluded to, right now, my main focus is testing, testing, testing. But we need more help to ensure 6.1 is as polished as possible. I just wanted to reiterate that if anyone finds a critical bug, especially if it’s related to 6.1 features, please add it to the 6.1 Project Board and we will triage it from there.
Thanks to everyone who attended the meeting.