Editor chat agenda: 18th May 2022

Facilitator and notetaker: @get_dave.

This is the agenda for the weekly editor chat scheduled for 2022-05-18 14:00 UTC.

This meeting is held in the #core-editor channel in the Making WordPress 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/..

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

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 Agenda: 11 May 2022

Facilitator and notetaker: @paaljoachim

This is the agenda for the weekly editor chat scheduled for Wednesday, May 11 2022, 04:00 PM GMT+1. This meeting is held in the #core-editor channel in the Making WordPress 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/..

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

Editor chat summary: Wednesday, 4 May 2022

This post summarizes the weekly editor chat meeting on Wednesday, 4 May 2022, 14:00 UTC held in Slack.

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.2 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).

George Hotelling is going to release Gutenberg 13.2 RC. The PR’s part of the release are available at https://github.com/WordPress/gutenberg/milestone/177. The release contains 154 PRs.

WordPress 6.0 Project board & 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. 4 & WordPress 6.0 RC 1

WordPress 6.0 RC was released on the 3 of May. Everything is going according to the plan no critical or blocking issue has been found. There are still some tasks on the 6.0 board https://github.com/orgs/WordPress/projects/27, these tasks will probably be part of 6.0.1.

Help Wanted: Test WordPress 6.0

Any help testing the latest version and making sure there are no issues there can have a great impact. Please try your development website with the last RC. And in case you find any issue please report it so the team can fix it.

Key projects updates

Patterns & Styles

@jorgefilipecosta share the updates for patterns and styles as follows:

Right now, we have a style object on the blocks that follow a similar shape to the 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. styles, but they are not equivalent, and also, not everything theme.json supports is supported there. The idea is to have blocks support local settings and style objects @oandregal started the work on the settings part. On the styles front we had tremendous progress that makes the style theme.json object color and typography keys be supported https://github.com/WordPress/gutenberg/pull/40332. Thank you @ramonopoly!

In order to have settings with semantic meaning, a 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. instance needs to have a name and probably information related to the type of section keywords, etc. @jorgefilipecosta started and iterated on the work to implement the metadata infrastructure for these sections https://github.com/WordPress/gutenberg/pull/40393.

Comments

@santosguillamot said regarding comments he just published an update on the tracking issue of the PRs that have been merged and included later in the RC.

Task coordination

@jorgefilipecosta

Plans:

  • To merge the section’s metadata PR.
  • Help the exploded view PR get merged and the refactors it involved including the popover.
  •  Finish some tasks I have pending related to the list v2 block.

@paaljoachim

Has earlier been giving feedback through issues to various Comments block features and Going forward plans on testing WP 6.0 Beta/RC releases.

@mamaduka

Has worked on performance improvements for Navigation blocks and a few more last-minute fixes for the WordPress 6.0 release.

Open floor

UIUI User interface to create a single template

@jessica asked if there is a specific reason we can’t add single templates in the site editor?

@jorgefilipecosta said he thinks that the task is available for someone to pick.

@jessica submitted a PR fixing the issue after https://github.com/WordPress/gutenberg/pull/40830.

Wide alignments on nested blocks

@cbirdsong asked why when theme.json is enabled one can not use wide/full alignments on nested blocks liking to the issue https://github.com/WordPress/gutenberg/issues/33374. Adding that, This is the core reason my custom theme builds don’t use theme.json, and as more features are gated behind using it, he was wondering if there is any chance of some re-evaluation of disallowing nested wide/full alignments.

The team discussed this issue and concluded the issue could be divided into two parts:

  • First, the cover block is missing a layout panel.
  • The default for blocks is not “inherit default layout”.

@cbirdsong will follow up and create the two issues.

#agenda, #core-editor, #editor, #summary

Editor Chat Agenda: 4 May 2022

Facilitator and notetaker: @jorgefilipecosta

This is the agenda for the weekly editor chat scheduled for Wednesday, May 4 2022, 04:00 PM GMT+1. This meeting is held in the #core-editor channel in the Making WordPress 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/..

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

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 Agenda: 27 April 2022

Facilitator and notetaker: @bph

This is the agenda for the weekly editor chat scheduled for Wednesday, April 27 2022, 03:00 PM GMT+1. It follows the proposed new format with more emphasis on the Open Floor discussion.

This meeting is held in the #core-editor channel in the Making WordPress 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/..

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda#core-editor#core-editor-agenda#meeting

Share this:

#agenda, #core-editor, #core-editor-agenda, #meeting

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 Agenda: 20 April 2022

Facilitator and notetaker: @fabiankaegy

This is the agenda for the weekly editor chat scheduled for Wednesday, April 20 2022, 03:00 PM GMT+1. It follows the proposed new format with more emphasis on the Open Floor discussion.

This meeting is held in the #core-editor channel in the Making WordPress 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/..

If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:

  • If you have an update for the main site editing projects, please feel free to share as a comment or come prepared for the meeting itself.
  • If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
  • If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.

#agenda, #core-editor, #core-editor-agenda, #meeting

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