Jb Audras 11:08 pm on September 7, 2021
Tags: , , , ,   

Dev Chat Agenda for Sept 8, 2021

Here is the agenda for this week’s developer meeting to occur at September 8, 2021, at 20:00 UTC.

Blogblog (versus network, site) Post Highlights and announcements

Bringing to your attention some interesting reads and some call for feedback and/or volunteers:

Components check-in and status updates

  • Check-in with each component for status updates.
  • Poll for components that need assistance.

Open Floor

Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?

Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.

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

#5-8-1, #5-9, #agenda, #core, #dev-chat

Francesca Marano 8:05 pm on September 7, 2021
Tags: , ,   

Upgrade/Install Meeting Notes, September 7

Quiet but productive chat, only two attendees, @afragen and @francina, but here is a quick recap 🙂 Slack logs.

#51857

@afragen stress tested it but didn’t find any concerning blockers. I asked @sergeybiryukov about commit: he is going to do another round of code review tomorrow, September 8, and if everything looks good, it will be committed. The solution addresses Outcome 1 and 2 of the initial feature proposal.

Outcome 3 – Have managed updates (database migrations)

This is going into the icebox momentarily. It needs a new 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. to work. If anyone is interested in picking it up, join our meetings on Tuesdays, at 17:00 UTC.

Outcome 4 – Create a unified 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. convention for requirements and dependencies.

This nine-year-old issue was revived. Worth reading through it all.

Here is @afragen TL;DR

  1. Any 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 that requires a dependency should degrade gracefully if that dependency is not present.
  2. Dependencies should have notices to install and later activate the dependency.
  3. Some notification of which plugin is a dependency of what other plugin.

There is also the potential for abuse, with plugins reporting dependencies that aren’t really dependencies.

Andy also suggested making a proof of concept plugin, instead of creating a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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..

What say you?

Do you want to add to the conversation? Please comment on the TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. ticketticket Created for both bug reports and feature development on the bug tracker. (beware, comments in GH will be shown in Trac, but not the other way around, so please use Trac, thank you 🙏). We are in the “feedback, validate, outreach, test, inform, reply to questions” 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. stage. Join us!

See you next week 👋

#core-auto-updates, #updater, #upgrade-install

Francesca Marano 1:46 pm on September 7, 2021
Tags: , ,   

Upgrade/Install component meeting agenda for September 07, 2021

The next meeting is scheduled on Tuesday, September 7, 2021, at 17:00 UTC and will take place on #core-auto-updates 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.

The aim of the chat is to check the status of the [Feature project] Updates on updating the updaters.

Got something to propose for the agenda? Please leave a comment below.

See you later!

#core-auto-updates, #updater, #upgrade-install

Paal Joachim Romdahl 8:38 am on September 7, 2021
Tags: , , ,   

Editor Chat Agenda: 8 September 2021

Facilitator and notetaker: @andraganescu

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

  • What’s new in Gutenberg (11.4).
  • 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/ 11.5 RC will be released Wednesday.
  • Whats next in Gutenberg: July and August. (September version has not been posted yet.)
  • Updates based on updated scope for site editing projects and WP 5.8:
    • Navigation BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. & Navigation Editor.
    • Template editor.
    • Patterns.
    • Styling.
    • Mobile Team.
  • Task Coordination.
  • Open Floor.

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

Dan Farrow 9:36 pm on September 6, 2021
Tags: ,   

CSS Chat Summary: 02 September 2021

The meeting took place here on Slack. @danfarrow facilitated and wrote up these notes.

Announcements & Housekeeping

  • @danfarrow shared a document he worked on after last week’s meeting: a CSS Chat Facilitator’s Guide
  • The document includes a facilitator schedule – anybody interested in running a future CSSCSS Cascading Style Sheets. Chat or CSS Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. session is very welcome to add their name!
  • @notlaura let us know that her attendance will be spottier than usual for the next couple of months, but we are lucky to have had some new attendees join the meetings recently

CSS Custom Properties (#49930)

  • @robertg asked about indicating pull requests in the planning document’s Claimed & Unclaimed Files list. @danfarrow clarified that they should be marked with a link “Pull request” linking to the PR 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/. Merged PRs are indicated by striking through the entire line
  • @Erik raised the subject of polyfilling, as the ticketticket Created for both bug reports and feature development on the bug tracker. mentions Internet Explorer. @danfarrow pointed out that the ticket was created before WordPress dropped IE support so it’s no longer an issue. It’s always fun to be reminded of this fact, so thanks @Erik!
  • @robertg shared his WIP PR adding custom properties to customize-controls.css, which is littered with border-* properties
  • @ryelle announced that anybody who has claimed a file but not been able to work on it is free to unclaim it, with no strings attached. @danfarrow welcomed this sentiment as he may well fall into this categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging.
  • @danfarrow noted that all but 2 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS files have been claimed, and 11 PRs have been merged. He asked about the next step to which @ryelle responded that we will want to circle back to the unresolved subject of handling colours with opacity
  • @Erik noted an rgba based approach e.g. background: rgba(var(--color--), .9); which led to an interesting threaded discussion on the subject
  • @danfarrow asked @ryelle about progress in relation to her projected roadmap. @ryelle responded that at the current pace things are looking good

On that encouraging note the meeting drew to a close. Thanks everyone!

#core-css, #summary

Jb Audras 9:31 pm on September 6, 2021
Tags: , , ,   

A Week in Core – September 6, 2021

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 August 30 and September 6, 2021.

  • 23 commits
  • 61 contributors
  • 41 tickets created
  • 12 tickets reopened
  • 52 tickets closed

The Core team is currently working on the next point (5.8.1) and major (5.9) releases.

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

  • Double escape quotation marks(“) for 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/. “messages” – #52644
  • Clean css/dist as part of the webpack build step – #53719
  • Add missing @covers tags for Tests_Admin_IncludesComment – #39265
  • Add missing @covers tags for Tests_Admin_wpCommunityEvents – #39265
  • Add missing @covers tags for actions’ tests – #39265

Code Modernization

  • Code Modernization: Fix parameter name mismatches for parent/child classes in WP_List_Table::column_default() – #51553
  • Apply coding standards on CSSCSS Cascading Style Sheets. – #53866

Customize

  • Add wp-embed-responsive class to body if using widgets 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 – #53609

Documentation

  • Correct the post_submitbox_minor_actions hook description – #54045
  • Fix typo in a comment in WP_Customize_Manager::get_return_url() – #53399
  • Improve documentation in wp-signup.php – #41566
  • Move @since notes from the safe_style_css filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to the safecss_filter_attr() function – #53731
  • Provide a more accurate description for a few script and style functions – #54044
  • Сlarify that term_id is a valid value for the $field parameter of get_term_by() – #54065

Editor

  • Update block editor packages for WordPress 5.8.1 – #54052, #52818

Media

  • Remove documentation detailing specific edge cases in the image_editor_output_format filter – #53955
  • Apply the wp_editor_set_quality filter not only when loading an image in the editor but also when saving an converted image, after the mime-type of the output image has changed – #53667
  • Media: fix showing of the “Filter Media” filds when replacing an image from the media modal – #53833

Site Health

  • Remove MySQLMySQL MySQL is a relational database management system. A database is a structured collection of data where content, configuration and other options are stored. https://www.mysql.com/. query cache size from the Site Health Info screen – #53845

Widgets

  • Pass correct context to get_block_categories() calls – #53757
  • Rename and soft deprecate retrieve_widgets() – #53811
  • Show title and media select fields in AccessibilityAccessibility 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) Mode – #53641

Props

Thanks to the 61 people who contributed to WordPress Core on Trac last week: @audrasjb (8), @hellofromTonya (5), @pbearne (4), @jrf (4), @azaozz (4), @sabernhardt (4), @desrosj (3), @zieladam (2), @walbo (2), @kevin940726 (2), @johnbillion (2), @andraganescu (2), @netweb (2), @sergeybiryukov (2), @peterwilsoncc (2), @mukesh27 (2), @circlecube (2), @zodiac1978 (1), @noisysocks (1), @antonvlasenko (1), @terraling (1), @dariak (1), @vladytimy (1), @bedas (1), @ramonopoly (1), @timothyblynjacobs (1), @mikeschroder (1), @mkaz (1), @mhuntdesign (1), @hudson-atwell (1), @mark-k (1), @alexstine (1), @Enchiridion (1), @mt8biz (1), @westonruter (1), @jayupadhyay01 (1), @joen (1), @aristath (1), @toro_unit (1), @juanmaguitar (1), @gazchap (1), @tmatsuur (1), @muhammadfaizanhaidar (1), @ankitmaru (1), @pbiron (1), @ayeshrajans (1), @hareesh-pillai (1), @oandregal (1), @gziolo (1), @ntsekouras (1), @jblz (1), @talldanwp (1), @ribaricplusplus (1), @youknowriad (1), @paaljoachim (1), @kreppar (1), @ellatrix (1), @ajlende (1), and @mamaduka (1).

Congrats and welcome to our 7 (!) new contributors of the week! @terraling, @bedas, @hudson-atwell, @Enchiridion, @juanmaguitar, @gazchap, and @muhammadfaizanhaidar ♥️

Core committers: @sergeybiryukov (8), @hellofromtonya (5), @desrosj (4), @azaozz (2), @ryelle (1), @noisysocks (1), and @peterwilsoncc (1).

#5-8-1, #5-9, #core, #week-in-core

Josepha 9:51 pm on September 3, 2021
Tags: ,   

WordPress 5.9 Planning Roundup

Happy September no matter where you are in the world! Since we’re halfway through the alpha period for the next big release of WordPress, it’s time to gather all the pieces of planning into one place. This post will include all the best guesses and targets for dates, features, and squads.

This release will follow the same general cadence as the other releases this year, with a long alpha period (132 days) and a short 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. period (14 days) before 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). phase.

Proposed WordPress 5.9 Schedule

These are my best guesses at the milestones:

MilestoneDateDays from
Alpha (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. open for 5.9 release)June 30, 2021
Go/no go DateOctober 12, 2021104 days after Alpha
Feature freeze/Bug FixesNovember 9, 202142 days after go/no go
Beta 1November 16, 20217 days after Feature Freeze
Release Candidate 1November 30, 202114 days after Beta 1
General releaseDecember 14, 202114 days after RC1
WP5.9 Schedule

This schedule puts Beta 1 the week of a major US holiday and a few major commerce dates worldwide. It does avoid putting RC1 during that week.

Proposed WordPress 5.9 Scope

The main goal for 2021 is getting full site editing to all WordPress users. For WP5.9 the following features are in the suggested roadmap:

  • Blocks + intrinsic web design
  • Navigation menus
  • Interface for 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.
  • Refining editing flows 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. themes
  • New default theme
  • Additional design tools

There are also a few roadmap hopefuls out there.

  • Pattern insertion + creation
  • Unzip/Rollback Failsafes
  • PHPUnit Tests
  • Improved compatibility with PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.0 and 8.1

Proposed WordPress 5.9 Leads

  • Release LeadRelease Lead The community member ultimately responsible for the Release.: Matt Mullenweg
  • Release Coordinators:
  • Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Lead:
  • Editor Tech:
  • Editor Design:
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Tech:
  • Theme Lead:
  • Technical Writer: Jonathan Bossenger
  • Docs Lead:
  • Marketing & Comms: Josepha Haden
  • AccessibilityAccessibility 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) Lead:
  • Test Lead:

How to help!

I think we will need a slightly larger release squad for this final release of the year, so I’m opening calls for volunteers. As we approach the go/no go date and get a better idea of what features will really land in the release, we’ll get more squad leads assigned.

However, there are a couple of roles we really could use some volunteers for right now:

  1. Triage Lead
  2. Release Coordinators

If you’re interested in lending a hand, please share your interest in the comments!

Props to @francina for early versions of this post, and @jeffpaul + @desrosj for wrestling calendars with me.

#5-9, #planning
Dan Farrow 6:25 pm on September 2, 2021
Tags: ,   

CSS Chat Agenda: September 02, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is today, Thursday September 02, at 21:00pm UTC in the #core-css channel in 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/..

There will also be a CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. starting at 20:00pm UTC, an hour before the meeting.

Meeting Agenda

  • Welcome (21:00pm UTC)
  • Announcements & housekeeping
  • CSS Custom Properties (#49930)
  • Open floor / CSS link share

See you there!

#agenda

Francesca Marano 8:26 am on September 2, 2021
Tags: , , ,   

Dev chat summary, September 1, 2021

@hellofromtonya led the chat on this agenda. You can also read the Slack logs.

Highlighted blogblog (versus network, site) posts

The attendees did not add comments to the posts highlighted in the agenda.

Worth mentioning

Thanks to the 34 people who contributed to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. last week, including 2 new contributors! Kudos to the 8 core committers of the week, too

A Week in Core – August 30, 2021

Announcements

  • WordPress 5.8.1 RC 1 was released right before the dev-chat.
  • @webcommsat announced that the 6th edition of WordPress Translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. Day has started on September 1st and will run through the whole month: you can check the dedicated website.
  • @annezazu reported that a proof of concept for a migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. to Playwright was shared during the core editor meeting and well received thus far.
  • Tonya noted that the Test team is working on updating the local testing docs in the handbook to include not only wp-env but also multiple workflow alternatives.

Empower everyone to contribute!

Tonya Mork

Component maintainers

Build/Test Tools

Work continues on improving the PHPUnit test suite and PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.1 fixes.

Help/About

@webcommsat and @marybaum are meeting to plan ahead for WordPress 5.9 and what are the implications of auto-updates on the About page.

Upgrade/Install

Open Floor

Tonya brought up #53450 and asked for feedback. Two committers added positive comments so it looks like it’s a good candidate for WordPress 5.9.

Abha reminded everyone about the resources and links that the Marketing team created to promote multiple Make teams.

Michale Rehnert asked about how to set up a Docker container for contributing purposes. @helen suggested two resources:

Colin Stewart asked for feedback on #53152.

See you next week!

#5-8-x, #5-9, #dev-chat, #summary

annezazu 2:50 am on September 2, 2021
Tags: , , ,   

Editor chat summary: 1 September, 2021

This post summarizes the weekly editor chat meeting (agenda here) held in Slack. Moderated by @annezazu.

Announcements

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/ 11.4 launched

Release notes coming soon after a quick fix. For now, some highlights:

  • The Gallery 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. now acts as a wrapper for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Image Blocks thanks to the Gallery Block Refactor. 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 authors, please do check out out this dev note to get up to speed on backwards compatibility
  • The Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. block now has the option to add duotone filters so you now have even more ways to add your own style to your content.
  • Padding support was added to the Buttons Block making it easier to get the spacing just right.

5.8.1 RC launches today (Sept 1)

Based on the schedule previously shared, 5.8.1 RC will launch today with the release coming on September 8th. If you can, please help test the release.

Final day for the current FSE call for testing (Sept 1 )

It’s the last day to explore the current FSE Outreach Program call for testing. If you have time, share your thoughts! If you don’t, please help amplify by sharing with others.

Reminder: monthly block theme meeting in #themereview

A reminder was shared that there is a block theme meeting in for anyone keen to chat about what’s happening with block themes. This is a recurring monthly meeting so if you missed today’s, don’t worry!

Monthly Priorities & Key Project Updates

The overarching plan for September has not yet been shipped yet so we based today’s conversation on the July & August Plan. As a reminder to those working on these projects, async updates are both welcomed if you can’t make the meeting and needed.

Navigation Editor

For the Navigation Editor portion, @talldanwp shared a lovely update. Here are some highlights:

  • A plan has been formed for migrating from the customize 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. 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/. in the navigation editor.
  • The nav editor 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.’s design has been refreshed.
  • Some conversation is underway around extensibility of the editor (join in if you’re interested). 

Mobile

Shipping:

  • Block picker search

 Notable fixes:

  • Fixed an npm install breakage on Gutenberg’s trunk 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". due to third-party dependency we were building that had an unpinned typescript dependency.

In Progress:

  • Embed block (hoping to release some inline previews in our next release)
  • GSS Font size, line height, colors

Patterns

For patterns, some context was shared amongst the core editor wranglers from @paaljoachim that the design tool overview enhancements will ultimately also trickle down to make pattern creation easier, more responsive, etc.

Styling

I’m going to reuse part of the async update from André since he’s done a ton of work there. Lots of work is underway with adding duotone support in theme.json along with a PR around enabling global styles to all themes. Expect work to continue on this path for the week ahead.

No update for the Template Editor or the Navigation Block

If anyone has any context to add around the Template Editor or the Navigation Block, feel free to chime in below in the comments.

Task Coordination

Feel free to add items to this post if you weren’t able to make the meeting.

@mikeschroder

Shipped:

  • Closed 32024 via [51677]. Thanks everyone for your help, including with the follow-up tests commit! 
  • Opened two Video Block poster related PRs (34415 and 34411).

This week, planning to investigate 33437.

@oandregal

@zieladam

@youknowriad

  • I’ve worked a bit on performance. I want to get back to some layout related work.
  • I’ve reviewed a number of PRs as well.
  • I’ve spent some time this week exploring some wild ideas for block registration (both to make easier and more universal/language independent). For the curious, the repo is here https://github.com/youknowriad/blocky it’s no where near ready but I’d love to learn more about your custom blocks, if you have examples or ideas about how you’d ideally write them and what use-cases would you want to see for the simplified “view” property.

@joen

@gziolo

@annezazu

  • Recapping and responding to the current call for testing for the outreach program.
  • Finalizing the next call for testing(more exploration than call for testing right now on theme switching).
  • Drafting some core editor improvement posts + assisting with an upcoming News post
  • Shipped a YouTube video all about patterns.
  • Triaging unlabeled PRs (down from over 100 to in the 20s). The unlabeled PRs that are left I am not quite sure what to do with so feel free to jump in.

Open Floor

Offer to run a Gutenberg Release for the first time. Raised by @mikeschroder.

If folks are interested, after shadowing @talldanwp (thanks again!), I would love to try running a Gutenberg release for the first time. Whenever it works best for the team is okay with me!

Next step: @priethor will coordinate since he helps wrangle the release process.

Proposed migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. of E2E specs to Playwright. Raised by Bart Kalisz.

A proof concept was shared and well received thus far as part of a proposed migration to Playwright. At this point, a wider discussion needs to happen with impacted parties to ensure that folks are willing to follow the proposed changes. A few folks chimed in agreeing that a wider discussion needs to happen along with perhaps a comparison with Cypress (mentioned by @swissspidy). Depending on how things go, a Make Core post might make sense.

Next steps: Bart alerted the crew in #core-test and @annezazu will ensure that it gets discussed in the Core Dev meeting for wider attention.

Call for community ideas for FSE Outreach testing calls. Raised by @annezazu.

I’d love to start experimenting with community members sharing ideas for what to test in the outreach program. If you’d like to suggest an idea for a call for testing, know it’s very welcomed and all ideas will be weighed against current project priorities to figure out what makes the most sense to pursue. You can share ideas directly in the #fse-outreach-experiment 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 or via DM to me! In case you’re curious about how calls for testing have been wrangled in the past, it’s typically been a combination of monthly project priorities/release priorities + my own testing/what I can make happen + conversations with contributors.

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