Editor Chat Agenda: 15 June 2022

Facilitator and notetaker: @bph

This is the agenda for the weekly editor chat scheduled for Wednesday, June 15 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/..

General Announcements and Links.

If you cannot 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.

Thank you for review to @priethor

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

Devchat summary, June 8, 2022

The weekly WordPress developers chat followed this agenda. @marybaum and @webcommsat facilitated.

Link to start of meeting on the Make 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/. coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. channel.

1. Welcome

The last meeting happened May 25, 2022. If you’re new to the chat or would like some perspective, you can check out its dev chat summary. The Core Team reps and 6.0 release leads skipped the June 1 meeting in favor of live events at the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/..

2. Announcements

WordCamp Europe 2-4 June 2022! In Porto, Portugal!

Lots of conversation, lots of catching up happened at the first live WordCamp in more than two years. Over the next several weeks, look for more discussions (and some proposals on doing things better) as they emerge from conversations that happened in Porto.

@matveb has been thinking about 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/ roadmap. He posted this view of how that should affect planning for the next major release, which is version 6.1.

Gutenberg 13.4 has landed! (June 8, 2022)
What’s New in Gutenberg 13.4 – post published June 10, 2022

3. Blogblog (versus network, site) posts

Co-host @webcommsat shared these important posts for the community to digest:

A week in core, June 6, 2022 from @audrasjb

Editor chat summary, June 1, 2022

Gutenberg 13.4 Release Candidate 1 – June 1, 2022

4. Upcoming releases

Version 6.0 landed in late May 2022. The next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope. will be 6.1.

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. will be 6.0.1, and it needs release co-ordinators and a schedule.

Editor Chat Summary – June 8, 2022
6.0.1 Editor Tasks project board

@priethor sent the group the following updates:

  • Gutenberg 13.4 stable has been released (the release post will be published later this week).
  • In an effort to shorten cooldown periods that happen after each major release, 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 contributors have kept pushing forward 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. fixes ever since the 6.0 feature freeze. Thanks to this, there is already a handful of patches ready for an early 6.0.1 release; nothing fixed is urgent, but all things combined can make for an impactful minor release.
  • The first thing these minor releases need is people to run them – a Core tech lead and an editor lead. You can raise your hand in the core slack channel or contact @priethor, @annezazu (the release leads for 6.0) @audrasjb or @marybaum (the Core reps) privately.
  • Last, but not least, I [@priethor] would like to remind folks that the 6.0 release retrospective will still be open until June 19, 2022. Please provide your feedback by filling out the survey or in a post comment.

Message from @jeffpaul:
With 6.0 behind us and 6.1 in the planning stages I had a question about things likely more in the 2023+ time frame that have been asked to me privately but that I have no answers for and am hoping folks in dev chat might be able to chime in. Specifically editor collaboration. Is there any update on the plans on that phase of Gutenberg (with https://github.com/WordPress/gutenberg/pull/23129 & https://www.multidots.com/multicollab-editing-commenting-plugin-for-wordpress-gutenberg/ being the only two examples I know of so far on that route)?

Towards 6.1

Early Bug Scrub schedule for 6.1 – thanks to everyone who has been contributing to and to @costdev and @audrasjb for leading these. 

Link to Slack – info on 6.1 earlies bug scrub on June 8, 2022

5. Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org.

  • Proposed: A sprint to help update the Core Contributor Handbook on Monday June 20, 2022. Save the date. More details in a P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post and a spreadsheet to help async contribution to follow. If you would like to help with this, or you have a page of the handbook you would like to focus on, please contact @marybaum and @webcommsat who are pulling together some of the resources and links. Help for the sprint or preparing for it are welcome.
  • WordCamp Europe contributor day update (more updates will to come; some people are still travelling from the event).

    @webcommsat shared that lots of new people came to the core tables and to help work in cross-team areas. Thanks to @desrosj for organizing the core tables and all who helped lead areas of work or contributed. The group in Porto, and their online contingent, also did some cross-team work among core, documentation, training, community and marketing. More on this next week.
  • Next new Core contributor meeting: if you’re new to the channel or you’re here from WCEU. @sergey talked a little about the New Contributors meeting that happens every two weeks in Core channel on Slack, before dev chat. The next one happens in two weeks, on June 15, at 10:00 UTC. A new contributor session an hour before the dev chat on June 8 (link to it on Slack), the next one will take place in two weeks, on June 22, 2022 at the same time (19:00 UTC).
    WordPress Core Contributor Handbook FAQs to help new contributors to get started.

6. Open Floor

Component maintainers

  • @marybaum opened with a call to component maintainers.
  • @sergeybiryukov highlighted tickets #55852, which makes sanitize_url() the recommended function for sanitizing URLs instead of esc_url_raw() , and #55194, which makes wp_rand() work more like random_int() and mt_rand(). The full transcript of @sergey’s report.
  • @sergeybiryukov invited anyone interested in making 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 and theme updates in WordPress more reliable to test and leave feedback on the Rollbacks PR: https://github.com/WordPress/wordpress-develop/pull/2225.
  • From next week, reaching out to component maintainers will restart to find out if there are any updates or blockages that can be raised in dev chat. Please do add to the weekly dev chat agenda too or message @marybaum and @audrasjb if you have a particular issue. If you are interested in helping with a component, you can also reach out to them.

Editor fixes

Follow up on discussion started in the Core editor Slack channel, about how to land WordPress minor releases faster and more often. The full discussion.

@sergeybiryukov highlighted the feedback on these posts:
https://make.wordpress.org/core/2019/02/27/major-and-minor-version-release-cadence/
https://make.wordpress.org/core/2021/02/11/making-wordpress-releases-easier/

@hellofromtonya

  • Might be worth opening the discussion around minor release cadences to seek feedback on pain points and opportunities to potentially do a trial run.
  • The minor release schedule is flexible and can happen quickly as needed. Having a Core + Editor representation on the minor release squad provides the balance to make the decisions to go fast when needed and slow when not needed.
  • That mashup / pairing of Core and Editor leads leading the minor happened in the 5.9.x cycle. Might be worth doing it again in the 6.0.x cycle.
  • I’m not aware of anything that slows dow or bottlenecks minor releases. My impression is the minor release squad makes those decisions.

Possibly an idea is to:

  • monitor for pain points and bottlenecks during the 6.0.x minor cycles.
  • then do a retro afterwards to gather feedback
  • then refine the approach in the next cycle.
  • The retrospective and refinement are not new. Done after each cycle. But in this cycle, it could be an underlying project (or whatever to call it) of seeking process improvements. (edited) 

The next Dev Chat meeting will take place on June 15, 2022 at 20:00 UTC.

Props to @webcommsat for preparing the agenda and collating input,
to @marybaum and @webcommsat for leading the meeting,
to @marybaum for the summary, and to @webcommsat for reviewing.

#dev-chat, #summary

What’s new in Gutenberg 13.4? (8 June)

“What’s new in 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/…” posts (labeled with the #gutenberg-new tagtag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.)) are posted following every Gutenberg release on a biweekly basis, discovering new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Full Site Editing project.


It’s been a busy time in WordPress. The first WCEU since 2019 was held just a few days after the WordPress 6.0 “Arturo” release. Similarly, Gutenberg doesn’t rest and keeps bringing us goodies every other week! The 13.4 release comes with 25 enhancements and nearly 30 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. fixes.

Table of Contents

Support for button elements 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.

Gutenberg 13.4 adds support for button elements in theme.json, so themes can now add styles to their buttons using theme.json like this:

{
	"styles": {
		"elements": {
			"button": {
				"color": {
					"background": "black"
				}
			}
		}
	}
}

To make the most of this change, blocks like the Buttons, Search, Post Comments, and File blocks now make use of the new CSSCSS Cascading Style Sheets. class wp-element-button to support button elements in theme.json.

Block spacing is a very useful design tool for the Gallery block, but what if you wanted to set different horizontal and vertical gaps? Well, you can now do that by opting in to the new axial spacing available in the Gallery block’s dimension panel.

As part of the iterative improvements to the components and post sidebar, Gutenberg 13.4 brings a new look and feel to the Publish popover.

The Color UIUI User interface gets its share of improvements, too. The color-picking interface has been unified and now uses the ToolsPanel introduced in Gutenberg 12.6. This change comes with a few quality of life improvements, too, such as when pasting a hexadecimal color, the # gets automatically stripped for a smoother workflow.

Search Block variations now support query vars

Starting with Gutenberg 13.4, Search block variations can limit their search results based on the query variables provided. For example, you can create a custom Search block variation limited to search when post_type=product with the following registration:

registerBlockVariation( 'core/search', {
   name: 'test/product-search',
   title: 'Product Search Block',
   category: 'test',
   attributes: {
      query: {
         post_type: 'product'
      }
   }
} );

Performance Improvements

Performance is top of mind for WordPress, and Gutenberg 13.4 comes again with a few performance improvements.

On the frontend, Global Styles CSS is enqueued conditionally only for the blocks currently in the page being loaded, resulting in serving smaller pages to the client.

As far as the Editor is concerned, the autocomplete performance has been improved. Last, but not least, the ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Spring dependency has been upgraded, resulting in more efficient resource usage when the Block Editor is idle.

13.4.0

Enhancements

Block Library

  • Block deprecations: Provide context when blocks.registerBlockType is applied to deprecations. (36628)
  • File Block: Makes the button an element button. (41239)
  • Gallery: Opt-in to axial (column/row) block spacing controls. (41175)
  • Gallery block: Update the gallery gap to load styles in the headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. for block themes. (41015)
  • Navigation: Remove unnecessary ‘role’ attribute. (41360)
  • Post Author Name: Add to and from Post Author transformations. (41151)
  • Post Comments: Make the button an element button. (41251)
  • Search Block: Ability to specify additional search query vars. (40585)
  • Site Logo: Update/site logo constrain image. (41298)

Components

  • Allow removing the bottom margin from SelectControl. (41269)
  • ColorPicker: Only display detailed inputs. (41222)
  • ColorPicker: Strip hash from pasted hex values in ColorPicker. (41223)
  • Design updates to the Publish popover (DateTimePicker). (41097)
  • Spacer: Add RTL support. (41172)

Global Styles

  • Add support for button elements to theme.json. (40260)
  • Button Element: Add support to Site Editor. (41246)
  • Button Element: Update the button element selector. (41240)

Design Tools

  • Unify color UI. Refactor panel color gradient settings to use a tools panel. (41091)

Full Site Editing

  • Site Editor: Update single default template copy. (41302)
  • FSE Templates: Add info to templates created from wp suggestion. (41387)

New APIs

  • Move the visible blocks state to the block editor store. (41104)

Bug Fixes

  • Fix customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. block toolbar after popover refactor. (41312)
  • Get_style_nodes should be compatible with the parent method. (41217)

Block Library

  • Columns: Add default fallback gap value in block.json, and set it to 2em for Columns blocks. (41098)
  • Cover: Fix duotone when the background is set to fixed. (40554)
  • Gallery: Lower the priority of the gallery gap CSS so it loads after the block layout CSS. (41423)
  • Gallery: Support gaps that define column/row gaps to avoid PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher Warning/Fatal. (41125)
  • Group: Check variation is registered before displaying it in the toolbar. (41305)
  • Image: Revert error handling. (41221)
  • List: List split bugs if one of the splits is empty. (41283)
  • Navigation: Fix broken Page title for pages created inline within in Nav block. (41063)
  • Navigation: Remove all references to the navigation areas. (41205)
  • Query: Inherit author from the global query. (40648)
  • Table of Contents: Convert <br> tags to spaces in headings. (41206)
  • Table of Contents: Fix list block check. (41351)

Block Editor

  • Block Variations: Fix block variation registration when the icon is an object and contains transform scope. (41457)
  • Handle no variation case in the block transform menu. (41328)
  • Update the block popover position as we scroll the container. (41402)
  • Writing Flow: Fix browser formatting with shortcuts on multiple selections. (41207)

Components

  • BorderBoxControl: Fix right border control alignment on small viewports and RTL styles. (41254)
  • ColorPalette: Update label correctly when value is CSS variable. (41461)
  • InputControl: Fix undo when changing padding values. (40518)
  • Popover, CustomGradientPicker, Dropdown: Fix positioning of popover when used in a dropdown. (41361)
  • Style Variations: Set min-width for styles preview. (41198)

CSS & Styling

  • Block styles: Account for style block nodes that have no name. (41446)

Site Editor

  • Code Editor: Avoid content loss when switching between editors. (41407)
  • Fix description in GetTemplateInfo. (41394)
  • Navigation MenuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site. Sidebar: Fix vertical alignment of rows in navigation panel. (40883)
  • Persist new template’s description on creation. (41281)

Performance

  • Improve autocomplete performance. (41197)
  • Load block CSS conditionally. (41160)
  • Update React Spring. (41185)

Experiments

  • Remove Navigation screen from experiments page. (40878)

Documentation

  • Add missing entries to components package CHANGELOG. (41159)
  • Added example for getSaveElement. (41211)
  • Block support docs: Update blockGap notes. (41225)
  • Change ‘author’ to ‘categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.’ in onCategoryChange. (41299)
  • Components: Link Storybook in readme. (41182)
  • Create Block: Improve block templates. (41273)
  • Fix spelling mistake browser to browser. (41137)
  • Improve inline documentation. (41209)
  • SlotFill: Remove note about portals being unstable. (41359)
  • Update Page URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org. (41188)

Code Quality

  • Entity configuration types. (40995)
  • Remove unused color panel files. (41148)
  • Remove the tooltip from the block selection button. (41154)
  • Search: Avoid double escaping. (41147)
  • Upgrade Rememo to v4. (41415)

Components

  • Refactor Autocomplete to pass exhaustive-deps. (41382)
  • Refactor BorderControl to pass exhaustive-deps. (41259)
  • Refactor ColorPalette to disable exhaustive-deps check for now. (41253)
  • Remove ‘useCombinedRef’ hook. (41186)
  • Update @types/react-dates. (41266)
  • Refactor AlignmentMatrixControl to pass exhaustive-deps. (41167)
  • Surface: Convert component to TypeScript. (41212)
  • TextareaControl: Convert component to TypeScript. (41215)

Tools

Build Tooling

  • jest-console: Add types directory to “files”. (41386)
  • Scripts: Convert file extension to js in block.json during the build. (41068)
  • Scripts: 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-zip to include root path files. (41439)

Plugin

  • Updates tested up to with 6.0 version. (41272)

Project Management

  • Limit TimothyBJacobs codeowners to the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.. (41411)

Testing

  • CheckboxControl: Add unit tests. (41165)
  • Enable iframeiframe iFrame is an acronym for an inline frame. An iFrame is used inside a webpage to load another HTML document and render it. This HTML document may also contain JavaScript and/or CSS which is loaded at the time when iframe tag is parsed by the user’s browser.-inline-styles end-to-end test. (35171)
  • Migrate code block tests to Playwright. (41136)
  • Migrate HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. block test case to Playwright. (41231)
  • Migrate preformatted block tests to Playwright. (41128)
  • Migrate revert template test to Playwright. (41310)
  • Migrate separator block tests to Playwright. (41130)
  • Migrate template part test to Playwright. (41048)
  • Refactor check-local-changes script. (41074)
  • Rewrite flaky tests reporter into its own package. (41106)
  • Revert “Enable iframe-inline-styles end-to-end test”. (41369)
  • Upgrade Playwright and use the official role selector engine. (41389)
  • Use @testing-library/user-event in BoxControl tests. (41422)
  • Use @testing-library/user-event in TimePicker tests. (41270)

wp-env

  • Allow skipping setting a configuration value by specifying it as null. (41084)
  • Fixed run Argument Passing. (41179)
  • Remove explicit git 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". fallbacks for wp-env and update readme. (41043)

Performance Benchmark

The following benchmark compares performance for a particularly sizeable post (~36,000 words, ~1,000 blocks) over the last releases. Such a large post isn’t representative of the average editing experience but is adequate for spotting variations in performance.

Post Editor

VersionTime to the first blockKeyPress Event (typing)
Gutenberg 13.45.47s49.19ms
Gutenberg 13.35.05s51.38ms
WordPress 6.06.09s47.62ms

Site Editor

VersionTime to the first blockKeyPress Event (typing)
Gutenberg 13.46.53s42.94ms
Gutenberg 13.36.38s41.7ms
WordPress 6.06.12s41.17ms

Contributor props

The following contributors merged PRs in this release:

@aaronrobertshaw @adamziel @aduth @amustaque97 @andrewserong @aristath @chad1008 @ciampo @CWBudde @dd32 @derekblank @draganescu @ethitter @fluiddot @geriux @getdave @glendaviesnz @gvgvgvijayan @gziolo @jameskoster @jorgefilipecosta @jostnes @JustinyAhin @kevin940726 @Mamaduka @matiasbenedetto @mirka @noisysocks @ntsekouras @ObliviousHarmony @pooja-muchandikar @ramonjd @SavPhill @scruffian @SiobhyB @stokesman @t-hamano @talldan @tellthemachines @TimothyBJacobs @tomasztunik @torounit @walbo @xconsau @youknowriad @ZebulanStanphill

The following PRs were merged by first-time contributors:

Kudos to all the contributors that helped with the release, not just with PRs but in any shape or form! 👏


Thanks to @jameskoster for the visual assets and @angelasjin for the peer review.

#gutenber, #gutenberg-new

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

Dev Chat Agenda, June 8, 2022

[Updated 8 June – link for last Dev chat summary – @webcommsat]

This weekly WordPress Developers Chat takes place in the #Core channel of the Make 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/. on Wednesday 8 June 2022, 21:00 UTC. All welcome.

1. Welcome

Dev Chat summary from the meeting on May 25, 2022

2. Announcements

Roadmap to 6.1 from @matveb **

3. Blogblog (versus network, site) posts of note

A week in core, June 6, 2022 from @audrasjb

Editor chat summary, June 1, 2022

Gutenberg 13.4 Release Candidate 1 – June 1, 2022

4. Upcoming releases

i) Recently published major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.: any updates on 6.0 release and 6.1 **

WordPress 6.0 “Arturo” 

ii) 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. – 6.0.1

Discussion items: release coordinator(s) and timing. A number of tickets are in the milestone.

5. Core ContributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org.

a) Proposed: A sprint to help update the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Contributor Handbook on Monday June 20, 2022. Save the date. More details in a P2P2 A free theme for WordPress, known for front-end posting, used by WordPress for development updates and project management. See our main development blog and other workgroup blogs. post and a spreadsheet to help async contribution to follow.

b) WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. update (if available, if not will move to next week’s agenda if people are still traveling)

c) Next new core contributor meeting – for any new joiners to the channel or from WCEU!

6. Open floor

If you can not attend the meeting live, please do add comments to this post with items or tickets you wish to highlight and related requests.

a) Components Maintainers – any ticketticket Created for both bug reports and feature development on the bug tracker. issues or volunteers to assist with components?

b) From discussion in Core editor, about how to quicken the landing of 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/ 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 core through minor releases? It was suggested to bring this topic to the weekly Core Dev Chat for broader discussion on how to do faster, more frequent minor releases to ship fixes faster.

c) Any tickets from Core or Gutenberg to highlight?

d) Any other items?

Reminder: if you have any items for Open Floor, please add them in the comments below. This helps plan the meeting and give enough time for any particular areas needed.

Thanks to @webcommsat and @marybaum for working on the agenda and planning,
and the contributions from core team members.
If you can help with the summary, please reach out to
core team reps @marybaum and @audrasjb

#agenda, #core, #dev-chat

Performance team meeting summary 7 June2022

Meeting agenda here and the full chat log is available beginning here on Slack.

Announcements

@shetheliving

  • Huge thank you to everyone who participated in any way in our work at WCEU! Feedback was extremely positive and we have lots of new people who are interested in contributing
  • Our weekly chat is held in the #performance channel on Tuesdays at 15:00 UTC and our GitHub repo is here; feel free to take a look at open issues and add new issues
  • You can watch @flixos90‘s talk from WCEU here

Focus group updates

Images

@adamsilverstein @mikeschroder

GitHub project

Feedback requested

Object Cache

@tillkruess @spacedmonkey

GitHub project

Feedback requested

Site Health

N/A

GitHub project

Feedback requested

Measurement

N/A

GitHub project

  • We’re seeking 1-2 POCs for this group; if you’re interested, please comment here or ping in Slack
  • No updates

Feedback requested

JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/.

@aristath @sergiomdgomes

GitHub project

  • @aristath (async): Working on ways to apply some tree-shaking to 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. styles. Created a proof of concept in Tree-shaking block styles on the frontend #41020 and would appreciate feedback. Also working on an alternative method which would not require 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. changes to block.json, but worried about server-side performance. Current implementation in the POC is far from perfect but enough to be a good conversation starter to move this forward.

Feedback requested

Infrastructure

@flixos90

GitHub project

Feedback requested

Open floor

  • @clarkeemily: Working on collating photos and stories from WCEU and will share with the wider group soon

Help wanted

#core-js, #core-media, #performance, #performance-chat, #summary

#hosting-community

Editor Chat Agenda: 8 June 2022

Facilitator and notetaker: @paaljoachim

This is the agenda for the weekly editor chat scheduled for Wednesday, June 8 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

A Week in Core – June 6, 2022

Welcome back to a new issue of Week in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between May 30 and June 6, 2022.

  • 23 commits
  • 24 contributors
  • 65 tickets created
  • 3 tickets reopened
  • 41 tickets closed

The Core team is currently working on the next major releasemajor release A release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope., WP 6.1 🛠

Worth noting that the WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe 2022 contributors day gathered more than 800 contributors in Porto last week. This was the largest Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. ever held!

Ticketticket Created for both bug reports and feature development on the bug tracker. numbers are based on the Trac timeline for the period above. The following is a summary of commits, organized by component and/or focus.

Code changes

Build/Test Tools

  • Add some test cases for path_join() with Windows paths – #55897
  • Add unit tests for path_join()#55897
  • Clean up test images before performing assertions in image resize tests – #55652
  • Consistently pass the $force_delete parameter to wp_delete_attachment()#55652
  • Correctly confirm the previous workflow run was triggered by a push event – #55652
  • Don’t overwrite image metadata in a wp_calculate_image_srcset() test for zero width – #55652
  • Prevent inaccurate “fixed” notifications 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/.#55652
  • Require the zip PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher extension in 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. templates export file test – #55652
  • Update the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org to the documentation 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 environment variables – #55652

Bundled Themes

  • Twenty-Twenty: Alignment fix on Separator Block editor styles – #55896
  • Twenty-Twenty: Fix paragraph block alignment issues when used on a RTL website – #49447
  • Twenty-Twenty: Improve Quote block style consistency between front and back-end – #55931

Docs

  • Correct method reference format in some DocBlocks – #55928
  • Replace “updated” with “deleted” in wpdb::delete return description – #55646
  • Use third-person singular verbs for method descriptions in wp-includes/post.php, as per docs standards – #55646
  • Various fixes in wp-includes/pluggable.php docblocks, as per documentation standards – #55646

Formatting

  • Make sanitize_url() the recommended function for sanitizing a URL – #55852

General

  • Ensure wp_rand() returns 0 when $min and $max values are equal to 0#55194
  • Remove redundant ltrim() from path_join()#55897
  • Replace all esc_url_raw() calls in core with sanitize_url()#55852

I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill.

  • Use consistent context for the “Add New” string when referring to media – #55876

Media

  • Add support for WebP images in the Thickbox library – #55786

Text Changes

  • Improve consistency of adminadmin (and super admin) error notices – #50785

Props

Thanks to the 24 people who contributed to WordPress Core on Trac last week: @SergeyBiryukov (5), @audrasjb (4), @mukesh27 (3), @benjgrolleau (3), @sabernhardt (2), @peterwilsoncc (2), @iamjaydip (2), @whaze (2), @karlijnbk (2), @amirkamizi (1), @larrach (1), @ilunabar (1), @tobifjellner (1), @mihaidumitrascu (1), @transl8or (1), @cadlec (1), @umesh84 (1), @joyously (1), @mayankmajeji (1), @dd32 (1), @kajalgohel (1), @hasanuzzamanshamim (1), @ianbelanger (1), and @graham73may (1).

Congrats and welcome to our 6 new contributors of the week: @benjgrolleau, @whaze, @karlijnbk, @amirkamizi, @mihaidumitrascu, @cadlec ♥️

Core committers: @sergeybiryukov (13), @audrasjb (8), and @desrosj (2).

#6-0, #core, #week-in-core

Performance Chat Agenda: 7 June 2022

Here is the agenda for this week’s performance team meeting scheduled for June 7, 2022, at 15:00 UTC.


This meeting happens in the #performance channel. To join the meeting, you’ll need an account on the Making WordPress Slack.

#agenda, #meeting, #performance, #performance-chat

Roadmap to 6.1

It’s time to look ahead at the main areas of work for WordPress 6.1. The tune of the release will be to refine the experiences introduced in 5.9 and 6.0, weave the various flows into more coherent and fulfilling experiences for users, maintainers, and extenders, and close some gaps in functionality as we start to look towards Phase 3 of 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/ roadmap.

Keeping this concise so people can expand through the main Phase 2 project overview.

Template Editor →

Introduce the ability to browse, visualize, and edit the structure of the site. Provide more clarity between global elements (templates, template parts, styles) with the aim of unifying the template editor and the post editor experiences.

There’s a subset of work here around improving the navigation block →

Building With Patterns →

We should be better prepared to fully unlock the potential of patterns as outlined in “Building with Patterns”, which was put together a bit late in the 6.0 cycle. Allow patterns to be a central piece of the creative experience, including tailoring them for custom post types, 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. types, improving the locked down experience, manage saved patterns, etc.

Global Styles →

Blocks & Design Tools →

Continue to make progress on the global styles interface while improving the support for restrictions, privileges, and curated presets. Allow managing webfonts, implement responsive typography, and expand the toolset available to blocks with an eye towards consistency, reliability, and delight.

Themes & Gradual Adoption

There are also several issues around the ability to adopt features like template parts gradually on existing themes, as well as the possibility of getting broader access to 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. editing. It’s also important to continue to look towards theme switching flows and how to best make use of the new possibilities of styles and templates.

#6-1, #gutenberg