Editor chat summary: June 22, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, June 22. 2022, 03:00 PM GMT+1 in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. Moderated by @fabiankaegy.

GutenbergGutenberg 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/ pluginPlugin 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

Gutenberg 13.5 got released by @annezazu. You can find the Changelog in the What’s new in Gutenberg 13.5? (22 June) post.

WordPress 6.0.1

WordPress 6.0.1 project board

Key project updates

The list of GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ tracking issues was updated to reflect the updated Roadmap for Gutenberg Phase 2 for WordPress 6.1 Matias Ventura published earlier this month.

Task coordination

Nothing was discussed during the meeting.

Open floor

@andrewserong

Shared an update on some of the work they’ve been doing to explore a potential path forward for refactoring how the Layout blockBlock 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. support works.

@ramonopoly

Shared an update about the work on the Fluid Font Size feature.

@daveloodts

Asked a question regarding styles that get added for image alignment in the editor.

@mamaduka

Shared a Proposal for Weekly Editor Bug Scrubs

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor chat summary: 15 June, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, June 15 2022, 03:00 PM GMT+1 in Slack. Moderated by @bph.

GutenbergGutenberg 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/ pluginPlugin 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 releases

Latest release Gutenberg 13.4

Gutenberg 13.5 RC 1 as released shortly after the meeting by @annezazu – Final release scheduled for Jun 22.

WordPress 6.0.1

WordPress 6.0.1 project board

Key project updates

The list of GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ tracking issues was updated to reflect the updated Roadmap for Gutenberg Phase 2 for WordPress 6.1  Matias Ventura published earlier this month.

Thank you for updates 
@siobhyb for the Mobile Team update
@getdave for the Navigation Block update

Task Coordination

@siobhyb

We’re currently making plans for Q3 on the mobile team, but it’s likely that we’ll have a focus on maintenance and fixing existing bugs.

@mamaduka

I’m mostly catching up on GitHub notifications after WCEU and my vacation. I’ll be focusing on PR reviews this week.

Open Floor

Announcements, questions, and discussions.

@hellofromtonya

Mentioned on the discussion on how to do faster, more frequent minor releases in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to ship fixes faster. Here a few links:

Next steps suggested by @hellofromtonya

  • Form the minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. squad > folks need to raise their hands (#6-0-release-leads channel)
  • list of pain points, bottlenecks, and ideas could be generated and then shared for discussion with the minor release squad

6.0 retrospective is still on its way. Deadline Jun 19th.

@johnstonphilip

Requested help to making sure duotone code is not present on the page unless required? (PR #38299) After the meeting, @skorasaurus chimed in

@alexstine

Needs technical feedback on this proof of concept PR for accessibility, even if it’s not a full code review “getting some input on if it is a good idea or how to make it a better idea would be great.” Stine wrote.
Related discussion: Improve keyboard navigation experience in all the block editors.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor chat summary: 8 June, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, June 8 2022, 03:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

GutenbergGutenberg 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/ pluginPlugin 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 releases

Gutenberg 13.4 was released 8 June.

WordPress 6.0.1

WordPress 6.0.1 project board

Key project updates

Task Coordination

No tasks shared.

Open Floor

Announcements, questions and discussions.

@ndiego

Highlight:
I would love to get some additional eyes on this issue: Backport fixes for wp/v2/block-patterns/patterns and /wp/v2/pattern-directory/patterns endpoints to Gutenberg issue. The related PRs need to be backported to Gutenberg and I am not sure what that process looks like.

Once these are backported, I have a fix for When removing core pattern, allow theme.json pattern slugs to be listed in inserter.

@luehrsen

Question:
I wanted to ask for guidance around this issue: Explore options to add back semantic classnames to block wrappers. Where can we help, what can we do to move this forward? This affects our day to day business, so we are more than happy to help. Especially since 6.0 rolled out features that ignore semantic classnames. (Group Row/Stack)

@torounit

Question:
PR: Migrate list block test to Playwright.
The e2e test passes on GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/-Actions, but when I run it on my machine some tests fail. ( tests with names starting with should undo asterisk transform with backspace )
This problem does not occur when I run step by step. ( use debug mode. )Adding new Promise( ( resolve ) => setTimeout( resolve, 300 ) ); to the line after createNewPost succeeds, but it doesn’t seem like a good way.
Is there a better way?

Question:
Do we still need wp.blocks in our documentation? PR: Add supports to basic sample code.
@import metadata “. /block.json” I thought it would be easier to understand.

@skorasaurus

Highlight:
I triaged the issue WP 5.9 adds default Duotones before closing the body there are users who feel burned about the decision that was made (to introduce duotones) and load them by default. Several users are still unsure how to dequeue/remove them. This is representative of a broader pattern where Gutenberg is introducing new features or options without the means of disabling them and the need to communicate these decisions more clearly.

We had multiple questions/comments during the Open Floor which still need feedback.

To get more details go directly to the Open Floor discussions in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor Chat Summary: June 1st, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on 2022-06-01 14:00 UTC in Slack. Moderated by @andraganescu.

GutenbergGutenberg 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/ 13.4 RCrelease candidate 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).

The 13.4 RC version of Gutenberg was released on June 1st by @priethor. Check it out here.

WordPress 6.1

It’s time to focus on the next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. of WordPress, version 6.0.1. It already has a project on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ concerning fixes and backports from Gutenberg.

Key project updates

Task Coordination

@andraganescu

@hellofromtonya

  • I’m working on wrangling web font needs to support 6.1 tasks. First step is to create a single epic issue that shares the vision (from Matías), a list of open work, prioritizations, and status.
    • Goal is to have this epic ticketticket Created for both bug reports and feature development on the bug tracker. available this week

Open Floor

Announcements, questions and discussions.

@mdxfr

Asked about support for current-menu-ancestor in the navigation blockBlock 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..

@mdxfr

Asked about how to quicken the landing of gutenberg fixes/improvements (already made within pluginPlugin 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) into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. through minor releases?

  • @andraganescu suggested  labeling with Backport to WP Minor Release merged PR’s that should sooner into core and monitoring the WordPress 6.0.1 project on GitHub
  • @hellofromtonya suggested to bring this topic to the weekly Core DevChat for broader discussion on how to do faster, more frequent minor releases to ship fixes faster.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor Chat Summary: May 25, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on 2022-05-25 14:00 UTC in Slack. Moderated by @zieladam.

GutenbergGutenberg 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/ 13.3

The 13.3 version was released on May 25th by @welcher. Find out more in the What’s New in Gutenberg 13.3.0 post.

WordPress 6.0

The long-awaited WordPress 6.0 stable version has been released this Tuesday!

The highlights include:

  • Enhanced Writing Experience
  • Style Switching
  • More Template Choices
  • Integrated Patterns
  • Additional Design Tools

Key project updates

Task Coordination

@amustaque97

@mamaduka

  • I’m mostly doing PR reviews last couple of days

@isabel_brison

  • I’ll mostly be migrating flaky e2e tests to Playwright this week

@zieladam

@welcher

@ntsekouras

  • I’ve started the work for expanding the templates in site editor. The first part will be for custom post types and their archive pages.

Open Floor

Announcements, questions and discussions.

@markhowellsmead

Asked about the motivation behind moving coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. inline.

This change has directly lead to many specificity problems, not least that it’s very difficult (and somtimes impossible) to override inline styles using rules in external CSS files.
Ref. https://github.com/WordPress/gutenberg/issues/38719
Ref: https://github.com/WordPress/gutenberg/issues/40159

Mark and other theme developers have seen feedback that hints how editor devs (in some cases) don’t want to “allow” others to modify layout or logical decisions through the use of code in themes or plugins. By blocking access to allow themes and plugins to override what should be simple core CSS rules, we’re being forced towards a complete deactivation of core CSS in some projects.  It’s admirable to release devs from the burden of basic CSS by way of the Style Engine, but there are limitless requirements for custom-built themes which neither belong in core, nor which can be solved by a generic APIAPI 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..

@amustaque97

Asked whether https://github.com/WordPress/gutenberg/issues/40809 is a bugbug 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. or enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature.. @zieladam thought it was a bug since it reports a mismatch between the editor and the website.

@welcher

Asked whether anyone is aware of any commits that need to be cherry-picked.

@manfcarlo

Reported that https://github.com/WordPress/gutenberg/issues/29484 is currently closed but it needs to be re-opened. The issue has been reopened since then.

@greenshady

Requested feedback on https://github.com/WordPress/gutenberg/issues/41324. The vertical alignment options for Row and Buttons (flex) blocks is always centered on the front end, even when choosing something like top alignment. This seems to be an issue with WordPress 6.0 branchbranch 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". but not with Gutenberg 13.2.2 active.

@bph

Proposed a theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. ‘allow-list’ to limit the number of patterns offered to the users through the patterns directory.

To get more details go directly to the Open Floor discussions in the Core Editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor Chat Summary: 18th May 2022

This post summarises the weekly editor chat meeting (agenda here) held on 2022-05-18 14:00 UTC in Slack. Moderated by @get_dave.

Status Updates

Task Coordination

The following items were shared by folks to update us on what work is in progress or where help is needed:

@noisysocks:

@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 patchpatch 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 BlockBlock 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.

@vcanales:

  • I’ve created a draft PR with a small proof of concept on creating random color palettes in the betaBeta 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

@get_dave:

@tomasz:

  • 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.

@zieladam:

  • I’ve been working with @gziolo on merging the GutenbergGutenberg 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 branchbranch 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 blockerblocker A bug which is so severe that it blocks a release. before shipping TypeScript types for getEntityRecord and other coreCore 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 UIUI 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.

Open Floor

The full Open Floor discussion is available on SlackSlack 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 a11yAccessibility 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 (:hover, :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.
  • @get_dave requested input from folks experienced with Global Styles and Theme JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. to discuss the potential data structure for such a feature.
  • @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 APIAPI 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.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor chat summary: 11 May, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, May 11 2022, 03:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

GutenbergGutenberg 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/ pluginPlugin 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 releases

Gutenberg 13.2 released 11 May.
Whats new in Gutenberg 13.2.

WordPress 6.0

WordPress 6.0 Project board
Project board for Dev Notes
Help Wanted: Test WordPress 6.0

Key project updates

Task Coordination

@amustaque97

I will be looking into issue: Post Comments block: Whitespace on top of warning message

@tomasztunik

A while ago I’ve shared a core Search Block extensibility feature request to give the ability for blockBlock 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. variations to provide custom search query parameters. Since then I’ve also shared a proposed implementation and I’d love some feedback. This would allow projects like WooCommerce or other projects that introduce custom post types to re-use the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. search experience to provide custom search components for their extensions.But it would also allow creating custom searches for core WordPress experience ie. searching only within specific categories, tags or authors.

Open Floor

Announcements, questions and discussions.

@annezazu

I’d like to start a discussion around adding a new label to the new label to the Gutenberg repo around issues that impact adoption. The aim would be to have an easier way to see, at a glance, what big issues are impacting the adoption of Gutenberg.

  • Would folks find value in having those issues clearly communicated?
  • Does a new GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ label seem like the right approach? If not, what other approaches would work well?
  • If a new GitHub label works well, what name would work best?

Here are a few suggestions:

  • [Type] Adoption Blockerblocker A bug which is so severe that it blocks a release.
  • [Type] Impacts Adoption

@marybaum
I like Adoption Blocker.
Could also make it active: Blocks Adoption.
@fabiankaegy
I also like the idea of that. Though it is difficult to really gauge the actual impact it has on the party that is blocked from adoption. I guess I’d like to understand what requirements a ticketticket Created for both bug reports and feature development on the bug tracker. needs to fulfill in order to “justify” getting that label applied.
@tomasztunik
I think if people had this at the back of their heads when triaging issues or evaluating feature requests this could shift the perspective toward the product and ecosystem more than the problem itself. Like another “standard” question to ask yourself when evaluating something.
@priethor
This is an example of an issue that would need that label: something already existing in WP but that Gutenberg doesn’t support, preventing Gutenberg adoption and users needing to stick with classic implementations:
https://github.com/WordPress/gutenberg/issues/3144
@mikachan
Another alternative for the label itself could be ‘migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. blocker’ (or ‘impacts migration’ / ‘blocks migration’).

@ndiego

This is a thought-provoking question that I asked earlier in #6-0-release-leads (SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.). When we fix bugs in Gutenberg (and also in Core), they can have unintended consequences when users upgrade to the new versions where the bugs have been fixed. Thought I would share it here as well.

To get more details go directly to the Open Floor discussions in the Core Editor Slack channel.

#core-editor, #core-editor-summary, #gutenberg, #meeting-notes, #summary

Editor chat summary: Wednesday, 27 April 2022

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, April 27 2022, 04:00 PM GMT+1

General Updates

Brian Alexander had a few suggestions in his post Help Test WordPress 6.0

Async key project updates

We used to exchange key project updates synchronously during the chat. However, many of the key GutenbergGutenberg 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/ projects sustain a regular cadence of updates on their tracking issues on GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.

The attendees are encouraged to read the latest updates directly from the following tracking issues at everyone’s leisure:

Task Coordination

@mamaduka

@ndiego

  • If you create an issue or PR that fixes a bugbug 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. related to the 6.0 release, please ensure it is added to the 6.0 Project Board. That is the best way to make sure we do not miss anything. Thanks!

Note: Anyone reading this summary outside the meeting, please drop a comment in the post summary, if you can/want to help with something.

Open Floor

@get_dave

I’ve got a PR which promotes __experimentalFetchLinkSuggestions to non-experimental API.
It will now be fetchLinkSuggestions. As this APIAPI 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. has been around in experimental form for a number of years, renaming it could cause regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. in 3rd party Plugins. Therefore, I want to raise awareness of the change well in advance

As a general rule ‘__experimental*’ APIs are undocumented, not maintained, can change at any time and are not backwards compatible.
@fabiankaegy commented: “In an ideal world I would love it if the __experimental API’s need to be stabilized before shipping in WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..”
@get_dave noted: “We have a lot of experimental stuff now. Needs to be whittled down.”

Side note: Discussion on how to approach reducing experimental and unstable APIs on the Gutenberg development has started on GitHub

@diego

“We are running Core Editor bug scrubs on Tuesdays at 14 UTC. This was started recently to prepare for the 6.0 release. What does everyone think about making this a standard thing moving forward, even after the release? We have thousands of issues and having a dedicated time each week to start wading through them as a team, I think, would be beneficial. Just trying to get some initial feedback on this idea.”

This was received with excitement. Nick will conceptualize it and prepare a Make Core post for public comment and to raise awareness.

@priethor

“I just wanted to take the opportunity to celebrate @Tomasz has become part of the Gutenberg contributor team. It’s always great to see new folks joining our efforts!”

@mamaduka

I wanted to mention this report about the Site Editor “freezing” for some users. It needs more testing and a way, we can constantly reproduce the problem.

@tomaszwp

“A while ago I shared some questions about contributing to core  Search BlockBlock 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. extensibility and shared the first proposal and PR (with some questions) that adds the ability to extend the search block with custom query vars.  Would love some feedback there to the proposed take.”

Props to @paaljoachim for his review 👏

Read the complete transcript

#core-editor-summary, #editor, #gutenberg, #meeting-notes, #summary

Editor chat summary: Wednesday, 20 April 2022

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, April 20 2022, 03:00 PM GMT+1

General Updates

Async key project updates

We used to exchange key project updates synchronously during the chat. However, many of the key GutenbergGutenberg 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/ projects sustain a regular cadence of updates on their tracking issues on GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.

This week we tried async updates. The attendees are encouraged to read the latest updates directly from the following tracking issues at everyone’s leisure:

Task Coordination

@fabiankaegy

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Open Floor

@zieladam

Announced that there is a new Pull Request template that got introduced lately, it follows the What? Why? How? format. In today’s discussion, some feedback to that template was surfaced, such as:

  • What? Why? How? may read abrupt
  • Achieving additional clarity seems easy
  • More discussion would make for a great next iteration

And so I opened this issue to iterate on the template: https://github.com/WordPress/gutenberg/issues/40470

@mamaduka

Raised that he wants to propose removing the Reusable blockBlock 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. edit locking feature from WP 6.0. He commented summary of the recent discussion in the tracking issue – https://github.com/WordPress/gutenberg/issues/29864#issuecomment-1103592492.

@nickdiego

Raised that if anyone had PRs/Issues that are related to WordPress 6.0, please make sure they are added to the 6.0 Project Board. This is the first place we are looking when triaging issues and we don’t want to inadvertently miss anything.

@Yann

Raised that after watching the 6.0 Product Walk-Through, he didn’t find the following blocks in WordPress 6.0 BetaBeta 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. 2:

  • Post Author Name
  • Post Comments Count
  • Post Comments Form
  • Post Comments Link

With WP 6.0 Beta 2, it’s not possible to build a comment section as there is no Post Comments Form, and the Post Comments block has been deprecated. Will they be included in WordPress 6.0?

@joyously

Raised that they were trying to test #45021, they got this jarring click ignore. I suppose that’s not a Media issue though, is it? They wanted to figure out whether it was already an issue, that the click is being ignored?

Read the complete transcript

#core-editor-summary, #editor, #gutenberg, #meeting-notes, #summary

Editor chat summary: Wednesday, 13 April 2022

This post summarizes the latest weekly Editor meeting (agenda, slack transcript), held in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel, on Wednesday, April 13, 2022, 14:00 UTC.

General Updates

Async key project updates

We used to exchange key project updates synchronously during the chat. However, many of the key GutenbergGutenberg 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/ projects sustain a regular cadence of updates on their tracking issues on GithubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.

This week we tried async updates. The attendees are encouraged to read the latest updates directly from the following tracking issues at everyone’s leisure:

@jorgefilipecosta

  • Patterns project we merged some big changes recently.
  • A new UIUI User interface for the query blockBlock 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. pattern selection UI And a pattern-based mechanism that allows the user to prefill the content of a page with a click is part of 6.0.
  • For the page patterns one right now we did not create page patterns into the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. or a core default theme so users don’t see anything yet.
  • We should discuss if the core should ship a default page pattern or if a core theme like 2022 should do that.

Task Coordination

@jorgefilipecosta

For the next two weeks, my plan is to focus on :

@tomasz

  • Wrapped up work on some of the tasks from the bugbug 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. scrub.
  • If somebody sees they are overflowing or some low-hanging fruits giving a lot of value ahead of final release I’m happy to support anything that leans more on the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors./TS/ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. and continue learning the ins and outs.
  • Got a couple of issue numbers I’ve seen popping up on the list that I’ll pick if nobody does before but feel free to pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me – working along @paaljoachim gave a lot of insights so don’t be a stranger.

Note: Anyone reading this summary outside of the meeting, please drop a comment in the post summary, if you can/want to help with something.

Open Floor

Extending core search block

@tomasz

Proposed improving the ability to extend the Search Block to make it possible to easily use it as a block variation to provide a basic search experience for extensions that introduce new post types.

This would be helpful for creating standard patterns for things like e-commerce headers.

@jeffpaul

Search block extensibility would be nice, speaking from a place of interest of the elastic press team and possible integrations we might consider as well

Github issue with a detailed proposal will be created for further discussion.

Usage of CSSCSS Cascading Style Sheets. :where selector

@glendaviesnz

A question has been raised about the increasing use of the :where selector. The use of it in the block frontend output is of more concern than its use in the editor CSS. The concern is that this is unsupported in a reasonable percentage of older browsers, and doesn’t necessarily degrade gracefully.
It would be good to have this discussed wider, and a decision made about its continued use.

Read complete transcript

#meeting-notes, #core-editor, #editor, #gutenberg, #core-editor-summary