This post summarises the weekly editor chat meeting (agenda here) held on 2022-05-18 14:00 UTC in Slack. Moderated by @get_dave.
The following items were shared by folks to update us on what work is in progress or where help is needed:
@manfcarlo (not present – shared by @paaljoachim):
- I want to draw attention to Page Break block ( core/nextpage ) not working as expected.
- It was patched in January but there are some problems with the 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. that will need to be re-patched.
- Details are in the latest comment on the issue.
@mamaduka – I got sidetracked with shiny new issues, but I plan to continue working on the 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. Locking feature.
- I’ve created a draft PR with a small proof of concept on creating random color palettes in the 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. Styles panel, with colors that work well together in terms of legibility.
- It’s very early on, but I’ll be updating that PR with whatever issues I can surface. I’ll also come back every week to ask for input
- I wanted to call for a review of Search Block extensibility: search query vars (now merged).
- I would really appreciate a review of the proposed implementation as this would enable our team at Woo to provide more contributions around the Search Block if we could rely on this extensibility feature.
- I’ve been working with @gziolo on merging 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/ changes into the WordPress 6.0 release branch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch"..
- The RC3 was released yesterday as @get_dave mentioned, next stop: RC4 and a stable version next week.
- I’ve shipped [Gutenberg Data Tutorial] Part 4: Creating pages
- I’ve proposed Typescript Entity configuration types – the last blocker A bug which is so severe that it blocks a release. before shipping TypeScript types for getEntityRecord and other core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-data selectors for a great autocompletion experience
@glendaviesnz (not present – shared by @paaljoachim):
- There have been some requests for the addition of spacing presets in Gutenberg, similar to the font size presets that are already available, to allow theme designers to specify a select list of spacing values that can be applied to blocks.
- It would be good to get some design feedback on this, in terms of the feasibility of adding this to the UI User interface, and how the UI for this might be structured.
- I think there has been some ongoing discussion about the suitability of the current UI for selecting the font size presets, so would be good not to repeat any problems that might exist there.
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/..
Right click action on List View (and in wider editor)
- @andrewserong would like to surface this PR which explore adding right click behaviour to the List View.
- He’d love feedback on whether overriding the native right click behaviour is something we want to do in Gutenberg.
- @get_dave, @zieladam and @mamaduka were in favour so long as it considered 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) concerns.
- @paaljoachim had reservations around discoverability.
- It was noted that @alexstine had already provided a11y feedback and an opt out via editor settings has been added to the PR.
- @hypest also noted that it should consider mobile interactions as well.
- Agreed to leave further feedback on the Issue/PR itself.
Request for feedback: enabling styling of interaction states in editor
- @get_dave wanted to surface these design explorations on enabling styling of interaction states (
:focus .etc) within the editor.
- Now is a good time to provide feedback and raise concerns in order that the first iteration of the interface can be as good as it can be.
- Folks were broadly in favour of this functionality being added.
- @fabiankaegy was concerned about adding a lot of additional clicks to every interaction – felt this would be better served with a persistent setting instead of a local state in every component.
- @tomasz noted it would be nice to have a full overview of the state ie. color + typography etc. rather than split between different panels. A summary would avoid having to keep a mental map in your head of all interactions.
- Please continue to discuss on the Issue.
Breaking change: promoting
experimentalFetchLinkSuggestions to stable 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.
- @get_dave would like to flag a PR which renames a long-standing experimental API to stable.
- There’s been lots of discussion around experimental APIs and the deprecation strategy recently, so I wanted to flag this one final time before it gets merged.
- Hopefully the impact is minor but it’s worth being aware of as it’s been around as
__experimental for quite some time.
- Noted that outreach has been done to community Plugins making use of the API.
- Will merge this week unless there are any blockers raised.
Thanks to everyone who attended the meeting.