Tag Archives: core-editor-summary

I’m currently looking into https://github.com/WordPress/gutenberg/issues/40528. I’m not able to reproduce the error. I would like others to have a look at it.

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

Aside of being the Editor Tech Lead for WordPress 6.0 alongside @gziolo, I’ve been automating the bulk of that role:
I will publish a post to share the details and the next steps of that.I’ve been also making Gutenberg Data framework easier and more accessible to use:

@welcher

I’ve got a PR in the works to allow creating dynamic blocks using @wordpress/create-block It’s a rough first pass so any input is appreciated – https://github.com/WordPress/gutenberg/pull/41289

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

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.

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

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

David Smith 5:12 am on May 19, 2022
Tags: core-editor ( 513 ), core-editor-summary, gutenberg ( 330 ), meeting notes ( 163 ), summary ( 560 )

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

The RC for Gutenberg 13.3.0 was released – thanks to @welcher for leading this one.
As we know WP 6.0 is nearly upon us and RC3 is available for testing now.
The final release of 6.0 is due on 24th May 2022
Key project updates:
The Project board for WordPress 6.0.1 (follow up!) is now available.

Task Coordination

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

@noisysocks:

I’ve been working on changes to the Status & visibility panel in the inspector sidebar.
Currently looking at redesigning the Date popover.
Here’s my full update.

@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:

I’ve been trying to fix a few things around the Nav block and creation of draft pages inline.
I want to draw attention to work going on to add support for more elements to Theme JSON so you can style buttons, caption…etc. Would be good to get more feedback on the approach.

@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

Paal Joachim Romdahl 9:48 am on May 16, 2022
Tags: core-editor ( 513 ), core-editor-summary, gutenberg ( 330 ), meeting notes ( 163 ), summary ( 560 )

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

Key project updates

Task Coordination

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

Birgit Pauli-Haack 7:55 pm on May 2, 2022
Tags: core-editor ( 513 ), core-editor-summary, editor ( 192 ), gutenberg ( 330 ), meeting notes ( 163 ), summary ( 560 )

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, 0 4 :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

continues to improve error handling in Media blocks. Here’s latest PR – https://github.com/WordPress/gutenberg/pull/40623 (merged now)
Also helping with some WP 6.0-related bugs.

@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!”

Read the complete transcript

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 👏

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

Fabian Kägy 5:04 pm on April 24, 2022
Tags: core-editor ( 513 ), core-editor-summary, editor ( 192 ), gutenberg ( 330 ), meeting notes ( 163 ), summary ( 560 )

Editor chat summary: Wednesday, 20 April 2022

General Updates

Async key project updates

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

Raised this PR: URLInput now always has an ID and accessible label which could use a review

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

Read the complete transcript

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?

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

Ajit Bohra 4:44 am on April 19, 2022
Tags: core-editor ( 513 ), core-editor-summary, editor ( 192 ), gutenberg ( 330 ), meeting notes ( 163 )

Editor chat summary: Wednesday, 13 April 2022

General Updates

Async key project updates

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 :

Patterns as Sectioning Elements.
Proposing the concept of sections as a block support hook mechanism.
Support other section-related tasks like Section specific theme.json and Section overview UI.

@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

zieladam 10:45 am on April 7, 2022
Tags: core-editor ( 513 ), core-editor-summary, gutenberg ( 330 ), meeting notes ( 163 ), summary ( 560 )

Editor Chat Summary: April 6, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on 2022-04-06 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.0 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 next release of the 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 is 13.0.0 and will be the last Gutenberg release included in WordPress 6.0. For this reason, the Release Candidaterelease 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). will be published on Friday 8th April, instead of Wednesday, giving a couple of extra days for PRs to be included in WordPress 6.0.

This release is managed by the Editor Tech Leads @zieladam and @gziolo.

The RC will shortly be followed by the WordPress feature freeze schedule in conjunction with Beta 1 on April 12th – it’s the Tuesday next week! Once that happens, new features will no longer be merged to the 6.0 release. Instead, it will be all about stabilizing the release and fixing the bugs.

WordPress 6.0

The current efforts are tracked on the Project Board. Note that it is not a list of must-haves. Rather, it is a tracker that reflects the status of current developments. The remaining in progress Pull Requests can use all the help they can get!

The Backport PHP changes for WordPress 6.0 release tracking issue prepared by @gziolo reflects the status of backporting the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes from the Gutenberg repository to the WordPress SVNSVN Subversion, the popular version control system (VCS) by the Apache project, used by WordPress to manage changes to its codebase. trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision.. If you’ve worked on one of the pull requests listed in there – your help and feedback will help smoothly merge them into WordPress 6.0!

Finally, there is a tracking issue for all the APIs marked as __experimental. This is the longest list so far! If you’ve worked on any experimental 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., your participation in that issue will help stabilize it.

Key project updates

Task Coordination

@paaljoachim

Here are some PRs I have given feedback to:
Try: Reusable block edit locking
[Block Library – Post Terms]: Add dynamic variations of custom taxonomies
Add: Option to pick a pattern on page creation.
Update query block creation and replacement flows

I looking for more feedback on Reusable edit lock PR: https://github.com/WordPress/gutenberg/pull/39950

@zieladam

Releasing Gutenberg 13.0 and leading merging it to WordPress 6.0 with @gziolo
Worked with @dmsnell on bringing the TypeScript support to the @wordpress/core and @wordpress/core-data modules. This effort is tracked in the following two PRs:
- TypeScript signatures for core-data selectors
- [data] Fill out type definition for data registry

WordPress 6.0 Project board

The WordPress 6.0 DevNotedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. tracking issue is now updated. https://github.com/WordPress/gutenberg/issues/39654. Everyone pinged there is invited to write their dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. and connect with me if there are blockers or questions

Open Floor

Announcements, questions and discussions.

@ndiego

Asked what kind of issues are fit for being added to the 6.0 Project Board. The answer was to focus more on PRs than issues as, at this stage, it’s like the sprint before the 13.0 is released. Also, adding something to the board is not a permanent commitment so adding something extra is fine. A new column called “After Gutenberg 13.0” was added.

@cbravobernal

Asked if PRs stabilising experimental features should be landed today. The answer was to merge them before Friday for the purposes of WordPress 6.0, and after Friday for the purposes of WordPress 6.1. Notably, the number of experimental features increased greatly since the previous WordPress release, and @zieladam will start a discussion to find the solution.

@gziolo also noted that experimental features like new coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blocks need to be promoted to stable as otherwise their code gets removed during the build process in WordPress core,

@paaljoachim

Brought two Pull Requests to everyone’s attention:

[Block Library – Post Terms]: Add dynamic variations of custom taxonomies that makes the Custom Post TypeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. terms show in the Query LoopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. 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.. Unfortunately, it isn’t merged right now and would benefit greatly from all the reviews it can get.

Add: Option to pick a pattern on page creation that displays a new patterns modal whenever a new page is created. Paal hoped to find an alternative, more subtle solution.

Props to @paaljoachim for reviewing!

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

Andrei Draganescu 5:52 pm on March 30, 2022
Tags: core-editor ( 513 ), core-editor-summary, gutenberg ( 330 ), meeting notes ( 163 ), summary ( 560 )

Editor chat summary: 30 March, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, March 30 2021, 03:00 PM GMT+3 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/ 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 12.9 is released.

The new version of Gutenberg brings a significant number of improvements to building blocks themes, working with content in the editor and managing complex 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. structures, along with the usual hundreds of updates and fixes.

WordPress 6.0

Wednesday, April 6th, Gutenberg 13.0.0 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). will be released, which is the last release to be merged in WordPress 6.0.

Project board for Dev Notes

If your PR is already merged, you don’t have to wait to write your DevNotedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase., the best time is now 🙂

Coordinate backporting PHP changes for WordPress 6.0

Everyone who worked on the PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher changes in the WordPress 6.0 release cycle is invited to check the issue linked above and report the status of the code introduced.

Key project updates

Task Coordination

My main focus was WP 5.9.3; RC should be released later today.
Planing to continue working on the remaining tasks for Block Locking.

@paaljoachim

Working on “Bulk Edit” Missing The Ability To Edit Tags
Testing Custom Post Type Terms (Categories and Tags)

@andraganescu

Continuing to work on adding featured image support to the cover block
Battling a failing test in my work to make the nesting in navigation configurable
Released Gutenberg
Next week I hope to be able to give some love to my reduced interface exploration which would work awesome with the new text selection features added recently

Open Floor

Announcements, questions and discussions.

Daisy Olsen @DaisyO holds regular Block Theme Discussions on Fridays via WordPress Social Learning.

April 1st, 15:00 UTC: JSON Schema
April 8th, 15:00 UTC Supports in theme.json
April 15th, 15:00 UTC Presets in theme.json

WordPress 6.0 Project board
Project board for Dev Notes

Every Thursday Ryan Welcher @welcher runs live programming streams at 14:30 UTC on his Twitch Channel covering block and Gutenberg development topics. Tomorrow he will work on how to create a plugin custom settings screen in preparation for his WCEU Workshop

@zeb

The PR to re-enable the Table of Contents block is fully ready for merge and needs just one approving review. @mamaduka invited the help of more Gutenberg CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. developers for the PR.

@priethor

Posted a friendly reminder regarding the WordPress 6.0 timeline: we are only one week away from Gutenberg 13.0 RC, which will be the last Gutenberg release included in WordPress 6.0. If you’d want the RC to be rescheduled for Friday, April 8th instead (2 additional days) post here some details.

@gziolo and @annezazu already expressed their desire to move the Gutenberg 13.0.0 RC release date.

@annezazu

There are 64 unlabeled issues in the Gutenberg repo currently. Let’s try and bring that number down.

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

Paal Joachim Romdahl 8:30 am on March 24, 2022
Tags: core-editor ( 513 ), core-editor-summary, gutenberg ( 330 ), meeting notes ( 163 ), summary ( 560 )

Editor chat summary: 23 March, 2022

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, March 23 2021, 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

What’s new in Gutenberg 12.8 (16 March).
Gutenberg 12.9 RC is released.

WordPress 6.0

Key project updates

Task Coordination

I would like to bring attention towards the following PR, need feedback and suggestions:
Code Block: add keyboard shortcut to indent lines inside code block.

@mmaattiiaass

I have been working on this PR around a11y testing for rendered blocks.
It got a few reviews and I’m currently working on a few improvements:
Implement a way to indicate 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) rules that need to be ignored.
Remove the 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/ action.
I would like to know what do you think about it.

I’m looking for feedback/code reviews on the new 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. Editor locking setting and block-level supports flag.
@audrasjb and I are planning to release WP 5.9.3 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). next week.

@isabel_brison and @andrewserong

Project update for Tracking: Add a Style Engine to manage rendering block styles.

@zebulan

I’ve made some improvements and optimizations to the Table of Contents block PR, and I believe it is fully ready to merge. All I need is one approving review.

@scruffian

I’ve been working Theme Exporting, specifically this fix – Theme Export: Add missing properties to theme.json.
I plan to work on this issue next: Theme Export: CSS variables encoded on export

@noisysocks

I tried to document Gutenberg’s desired PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher file structure and some best practices in a new lib/README.md file. Give it a read and, if you’re a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team member, feel free to add anything that I missed.
@kevin940726 has merged the necessary infrastructure to write E2E tests using Playwright.
This is the first step towards migrating our E2E tests from Puppeteer to Playwright. (Context here and here.)
If you’re keen to be an early adopter, there is some initial documentation on how to write Playwright tests and migrate Puppeteer tests to Playwright. README.md and MIGRATION.md.
For now there’s no expectation that new tests should be written in Playwright.

@justinahinon

Published a Make/Core post: Migrating WordPress E2E tests to Playwright

@ramonopoly

I have added an update note in relation fluid typography adventures over at Typography Tools: Tracking #34345.
Currently I’m concentrating on offering a backend option for fluid typography based on existing fontSizes presets in 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..

Open Floor

Announcements, questions and discussions.