Performance team meeting summary – November, 23 2021

This is the agenda for the meeting. You can read the logs here on Slack.

Focus group projects discussion

Image focus

@adamsilverstein shared an update for the Image focus. The group plans to go through the ideas in this document to discuss the impact, level of difficulty, etc. and generally prioritize our work. Also, in addition to taking some time during the regular media meeting, the group members are proposing a regular second “performance image focus” meeting in a friendly timezone to APEC contributors. The first try for that meeting will be November 25, 2021, at 02:00 UTC.

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/. focus

The JavaScript focus update was shared by @gziolo. The team is still collecting ideas for issues to work on in this document. They also discussed during the last week during #core-js office hours how to bring ES Modules and Import Maps to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.. The next office hour, focused on issues prioritization is planned on next Tuesday.

Object caching focus

@spacedmonkey put together a list of related tickets he is willing to work on.

Measurement focus

@wp-source stated that the team has some interesting projects ideas. Now, there is a need for some short and regular sync chat for the focus group members to discuss this project. If you are interested in attending one of these chats, please share your interest in this thread on Slack.

Performance features development coordination

@flixos90 shared some insights about the coordination repository proposal. Here are the main outcomes of these:

  • WordPress has historically relied on feature plugins to test future WordPress core features “in the wild”. The proposal here is to follow that approach, however by creating modules in a single “performance features wrapper 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”.
  • By centralizing these efforts in 1 plugin instead of x plugins, the hope is to significantly reduce maintenance, encourage cross-collaboration between different performance efforts, and have a centralized place for any performance-related conversations.
  • For example, a central 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/ repository could be used to open issues with new performance enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. ideas, discuss them etc, even if they don’t right away lead to a new performance module.
  • A single wrapper plugin also can help from an adoption perspective, essentially interested users can install the plugin once and then will get access to any new performance features as soon as they are added – they can then enable whatever they are interested in to try out.

There have been several discussions about where this repository should be created. The main locations being the Gutenberg repository, and under the GitHub WordPress organization.

After a vote, the repository has been created under the GitHub WordPress organization, and you can find it here.

#meeting, #performance, #performance-chat, #summary

A Week in Core – November 22, 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 November 15 and November 22, 2021.

  • 76 commits
  • 138 contributors
  • 48 tickets created
  • 6 tickets reopened
  • 73 tickets closed

The Core team is currently working on the next major release, WordPress 5.9 🛠

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

Administration

  • Restores “Customize” menu item for non-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 and moves for block themes – #54418

Build/Test Tools

  • Add the ruleset file to the cache key for PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS. and PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher compatibility scans – #54425
  • Cache the results of PHP_CodeSniffer across workflow runs – #49783
  • Restore the httpsHTTPS HTTPS is an acronym for Hyper Text Transfer Protocol Secure. HTTPS is the secure version of HTTP, the protocol over which data is sent between your browser and the website that you are connected to. The 'S' at the end of HTTPS stands for 'Secure'. It means all communications between your browser and the website are encrypted. This is especially helpful for protecting sensitive data like banking information. URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org for browserify-aes – #54337
  • Update all 3rd party 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 to the latest versions – #53363

Bundled Themes

  • Update the “Tested up to” 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. to 5.9#53797
  • Twenty Nineteen: Apply coding standards fix from running composer format#54392
  • Twenty Sixteen: Correctly align columns within table blocks as configured in the editor – #54317
  • Twenty Twenty-One: Check if anchor exists before triggering in-page navigation – #53619
  • Twenty Twenty-One: Correct description of Dark Mode in the 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.#53892
  • Twenty Twenty-One: Prevent notice thrown in twenty_twenty_one_get_attachment_image_attributes()#54464
  • Twenty Twenty-One: Remove RSS feedRSS Feed RSS is an acronym for Real Simple Syndication which is a type of web feed which allows users to access updates to online content in a standardized, computer-readable format. This is the feed. widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. icon link – #52880
  • Twenty Twenty-Two: Import the latest changes from GitHub – #54318
  • Twenty Twenty-Two: Sync updates from GitHub – #54318

Coding Standards

  • Wrap some long lines in js/_enqueues/admin/post.js per the JSJS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. coding standards for better readability – #53359

Comments

  • Change new comment required text class – #16206
  • Don’t output “cancel comment reply link” if comments aren’t threaded – #37267
  • Fix PHP Notice “trying to get property of non-object” in comments_open() and pings_open()#54159

Commit Standards

Database

  • Check if the $args[0] value exists in wpdb::prepare() before accessing it – #54453

Docs

  • Add missing null allowed type for the $id parameter of wp_set_current_user()#53399
  • Add missing parameters in in_plugin_update_message-{$file} 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.#40006
  • Corrections relating to types used in inline documentation for comment ID and site ID proprties – #53399
  • Improve the documentation for registering block patterns and block pattern categories – #53399
  • Remove instances of the “eg.” abbreviation in favor of “example” or “for example” – #53330
  • Restore [51733], accidentally reverted in [52212]#40006
  • Update documentation for the $plugin_data parameter of various hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.#53399
  • Various corrections and improvements relating to types used in inline documentation – #53399

Editor

  • Add missing label to new-post-slug input on Classic Editor – #53725
  • Check the correct post type support property for initial_edits#53813
  • Do not provide initial_edits for properties that are not supported by the current post type – #53813
  • Fix fatal call to add_query_args() – #54337
  • Fix how the Site Editor is linked to – #54337
  • Fix incorrect access of ID field – #54337
  • Load iframed assets in Site Editor – #54337
  • Update wordpress packages – #54337

External Libraries

  • Update the regenerator-runtime package to version 0.13.9#54027

Formatting

  • Add additional support for single and nestable tags in force_balance_tags()#50225

HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. 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.

  • Remove empty ? when only anchor remains in add_query_arg()#44499

KSES

  • Use correct global in wp_kses_xml_named_entities()#54060

Login and Registration

  • Wrap long usernames in login error message – #54168
  • auto-focus the reset password field – #40302

Media

  • Add support for v1 and v2 gallery block in get_post_galleries()#43826
  • 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. modal loads only selected image – #42937
  • Featured image modal loads only selected image – #53765
  • Move dismiss upload errors button after errors – #42979
  • Revert media uploader input change in [52059]#42937
  • improve error message for failed image uploads – #53985
  • Add audible notice on menu item add or remove – #53840

Posts, Post Types

  • Increment post_count option value during blogblog (versus network, site) creation – #54462, #53443
  • Increment post_count option value only on multisitemultisite Used to describe a WordPress installation with a network of multiple blogs, grouped by sites. This installation type has shared users tables, and creates separate database tables for each blog (wp_posts becomes wp_0_posts). See also network, blog, site installations – #54462
  • Multisite: Decrement post_count option value when a post is deleted – #53443
  • Use global post as the default for wp_get_post_parent_id()#48358

Query

  • Correct and standardise the metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. query documentation – #53467

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

  • Make the templates controller follow core REST patterns – #54422
  • Remove experimental block menu item types – #40878

Script Loader

  • Document path as an accepted value for $key in wp_style_add_data()#53792

TaxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies.

  • Allow get_*_*_link() and edit_term_link() functions to accept a term ID, WP_Term, or term object – #50225
  • Clarify the taxonomy labels for customizing the field descriptions on Edit Tags screen: – #43060

Themes

  • Check both parent and child themes for a theme.json file – #54401
  • Force a scrollbar on the Themes page to prevent visual shake on hover – #53478

Toolbar

  • Refine “Edit site” link.php – #54441

Upgrade/Install

  • Add timezone info to last checked update time – #53554
  • Correct the weekly cron event for clearing the temp-backup directory: – #51857
  • Deactivate 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/ 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 if its version is 11.8 or lower – #54405
  • Differentiate en_US version strings from localized ones – #53710
  • Improve the accuracy of the auto_update_{$type} filter docblockdocblock (phpdoc, xref, inline docs)#53330
  • Remove 5.8 function and fix deactivate Gutenberg plugin version compare < 11.9 – #46371

Users

  • Prevent infinite 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. when using capability checks during determine_current_user on multisite – #53386

WPDB

  • Call wp_load_translations_early() in wpdb::_real_escape()#32315
  • Call wp_load_translations_early() in wpdb::query() and wpdb::process_fields()#32315
  • Capture error in wpdb::$last_error when insert fails instead of silently failing for invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. data or value too long – #37267

Widgets

  • Wraps long widget titles in classic Widgets screen – #37451

Props

Thanks to the 138 (!) people who contributed to WordPress Core on Trac last week: @hellofromTonya (20), @sabernhardt (16), @audrasjb (13), @costdev (10), @sergeybiryukov (7), @johnbillion (7), @desrosj (6), @poena (5), @afercia (5), @SergeyBiryukov (4), @peterwilsoncc (4), @davidbaumwald (4), @birgire (4), @jeffpaul (3), @dilipbheda (3), @henry.wright (3), @pbearne (2), @TimothyBlynJacobs (2), @swissspidy (2), @shaunandrews (2), @glendaviesnz (2), @antpb (2), @kjellr (2), @talldanwp (2), @pento (2), @ramonopoly (2), @manishamakhija (2), @melchoyce (2), @dlh (2), @jrf (2), @dd32 (2), @chaion07 (2), @hareesh-pillai (2), @joedolson (2), @anthonyeden (1), @anandau14 (1), @asif2bd (1), @dpegasusm (1), @datainterlock (1), @mnelson4 (1), @ovann86 (1), @dlt101 (1), @xkon (1), @sabrib (1), @pankajmohale (1), @ianhayes94 (1), @hitendra-chopda (1), @gkloveweb (1), @drewapicture (1), @bravokeyl (1), @fpcsjames (1), @nettsite (1), @galbaras (1), @henrywright (1), @TobiasBg (1), @chrisvanpatten (1), @sourovroy (1), @jorbin (1), @szaqal21 (1), @PieWP (1), @danielbachhuber (1), @benitolopez (1), @ocean90 (1), @soniakash (1), @rachelbaker (1), @jigneshnakrani (1), @zoiec (1), @jdgrimes (1), @woodyhayday (1), @travisnorthcutt (1), @skunkbad (1), @richardfoley (1), @psufan (1), @procodewp (1), @nlpro (1), @david.binda (1), @lukecarbis (1), @lucasw89 (1), @liammitchell (1), @kwisatz (1), @justindocanto (1), @mista-flo (1), @celloexpressions (1), @Mamaduka (1), @kafleg (1), @umesh84 (1), @robertghetau (1), @musabshakeel (1), @rixeo (1), @marybaum (1), @felipeloureirosantos (1), @tmatsuur (1), @hasanuzzamanshamim (1), @wetah (1), @ravipatel (1), @mukesh27 (1), @westonruter (1), @mjaschen (1), @saju4wordpress (1), @otto42 (1), @joen (1), @flixos90 (1), @clucasrowlands (1), @beafealho (1), @luminuu (1), @netweb (1), @richtabor (1), @ovidiul (1), @h71 (1), @andy-schmidt (1), @mkaz (1), @noisysocks (1), @pbiron (1), @wparslan (1), @zieladam (1), @hellofromtonya (1), @benjaminanakenam (1), @webcommsat (1), @zodiac1978 (1), @tellyworth (1), @takahashi_fumiki (1), @russhylov (1), @lynk (1), @youknowriad (1), @donmhico (1), @tobiasbg (1), @danielpost (1), @nacin (1), @alexislloyd (1), @vdwijngaert (1), @ComputerGuru (1), @benjamingosset (1), @Presskopp (1), @thimalw (1), @dufresnesteven (1), @kingkero (1), @clorith (1), and @spacedmonkey (1).

Congrats and welcome to our 8 new contributors of the week: @robertghetau, @musabshakeel, @mjaschen, @saju4wordpress, @clucasrowlands, @russhylov, @lynk, @danielpost ♥️

Core committers: @hellofromtonya (14), @audrasjb (13), @desrosj (12), @joedolson (10), @sergeybiryukov (9), @noisysocks (6), @johnbillion (3), @jffng (2), @spacedmonkey (2), @davidbaumwald (1), @peterwilsoncc (1), @adamsilverstein (1), @ryelle (1), and @timothyblynjacobs (1).

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

WordPress 5.9 Revised Release Schedule

A revised release schedule for WordPress 5.9 is available, with the final release planned for 25 January 2022.

Why the delay?

Near the end of the original alpha release cycle, issues arose that related to multiple major features planned for the 5.9 release, including:

  • Full Site Editing (FSE), which is a collection of features, such as global styles interface, 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., block themes, template editors, and site editing flows.
  • The Twenty Twenty-Two (TT2) theme, which depends on these FSE features.

The 6.0 release isn’t due until April 2022—too long for the community to wait for them. After processing this list of issues, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor team saw the features could ship in 5.9 with the revised schedule. 

This decision, to delay the 5.9 release, was not made lightly. The following section shares the decision-making process.

The decision-making process

Careful, thoughtful, open discussions happened in the release squad channel, that considered  options and impacts:

  • Move the specific pieces needing fixing to 6.0.
  • Move the fixes to a 5.9 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..
  • Move the fixes to 6.0.
  • Move these major features to 6.0.
  • Delay 5.9 to include fixes.

As the FSE features are very closely intertwined, removing some of its pieces would risk making the release unstable. To avoid delivering a sub-optimal experience, moving fixes to a 5.9 minor or 6.0 was ruled out.

It came down to a choice between:

  • Option 1: Remove these major features from 5.9 to target shipping in 6.0 in April 2022.
  • Option 2: Delay the release to ship the promised major features in 5.9 in January 2022.

After consulting with advisors from previous release squads and the Core Editor team, based on the current information available, the release squad determined shipping these major features sooner rather than later would have more benefits and less impact.

The release squad respects that the community has expectations and plans for these features. The extra time in the new schedule will help everyone involved deliver the 5.9 features the community has been waiting for.

Seasonal considerations

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. and RC release cycles have two jobs: to get the community involved in testing and delivering feedback, and to give contributors a block of time to fix identified issues before the final release.

The third 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. of the year was originally scheduled for the middle of December. Historically, fewer people are available the last two weeks of a year and the first week of a new year, because of various holidays, time off, and end-of-year and annual planning. This means there would be fewer people to test, give feedback, fix reported issues, and help package each release.

The revised schedule takes into account the realities of year-end and offers an optional Beta 4 if needed.

A schedule that delivers the full release 

5.9 is still in feature freeze. Work from here on is strictly to address the changes that get the release to a stable state.

The revised schedule also has a number of built-in safety measures:

  • More transparency. Constant communication between the release squad and Core Editor team throughout each week, so everyone involved knows the status of relevant items and can surface (and meet!) needs as early as possible.
  • 🔺blockers merged by Beta 1. An agreement that blockers (identified as🔺 in the list) must be ready by Beta 1 or risk getting moved to 6.0. (Update: these items were merged last week and are no longer blockers.)

How can you help?

Above all, please help test everything.

  • Get involved in the FSE Program testing calls including testing the site-editing experience. You can find a record of all the FSE Outreach exercises; feel free to go back and test any that interest you, but keep in mind that features have evolved.
  • Spin up a test site that uses Twenty Twenty-Two. If you find issues, please report them by opening a Trac ticket
  • Important: Try to break things to find things that may not work for your test sites. 
  • If you’re available, come to the Beta and 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). (RC) release parties, and bring friends! Test the packages when they drop. The parties take 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/..
  • Come to the Slack meetings for Core and the Core Editor, and keep reading the posts on the Make.WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ blogblog (versus network, site).
  • Share feedback! The teams need to know everything that breaks, and everything that works really well, too.
    • For issues with 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/, create an issue 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/.
    • For issues anywhere else, start a ticket on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress..

Props @marybaum, @annezazu, @costdev, @webcommsat, @cbringmann for collaborating and proofreading this post.

#5-9

Editor Chat Agenda: 24 November 2021

Facilitator and notetaker: @get_dave.

This is the agenda for the weekly editor chat scheduled for 2021-11-24 14:00 UTC.

This meeting is held in the #core-editor channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

  • 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/ 12.0.0.
  • WordPress 5.9
  • Updates based on updated scope for site editing projects:
    • Template editor.
    • Patterns.
    • Styling.
    • 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..
    • 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 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

Performance Chat Agenda: November 23, 2021

Here is the agenda for this week’s performance team meeting to occur on November 23 2021, at 16:00 UTC.

  • Focus group projects discussion
  • Performance features development coordination: we will discuss the proposal to centralize and coordinate the development of performance features in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. (see proposal document here).
  • Open floor

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

WordPress 5.9 Editor Update – 19 November

👋 Hi everyone! Hope you’re feeling good, taking care of yourself, getting ready for a relaxing weekend, brushing your teeth regularly, etc. Here are some assorted WP 5.9 editor updates:

We are proposing to delay 5.9 Beta 1 to 30 November. This would give us until Friday 26 November to land any 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/ PRs that we want in 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. 1.

The two priorities right now are:

We are still in feature freeze, so please remember to add the Backport to WP Beta/RC label on your PRs that need to land in WP 5.9.

I’d like to call particular attention to these issues that are in the list above:

Key:
🎨 Needs design
🔨 Needs dev
👀 Needs review

#core-editor #5-9

Editor chat summary: 17 November, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on  Wednesday, November 17 2021, 04: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 11.9.1 and Gutenberg 12.0 RC were both released on the 17 November.

WordPress 5.9

WordPress 5.9 Beta 1 delayed
WordPress 5.9 roadmap and priorities.

@mkaz and @mamaduka

Key project updates

Based on the scope for Site Editing projects.

Template Editor

@mkaz

Merged PR: Add feature flag to toggle the new site editor sidebar.

Mobile Team

@hypest

  • Shipped
    Link 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. Setting for Embeds, which concludes current Embeds work on native mobile.
  • Fixes
    Fix for pasting from MS Word.
  • In Progress
    Upgrade to ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. Native v0.66.
  • Finalizing GSS Font size, line height and selected text colors.
  • I would love to connect with folks about editor plans for the next year and see how to include the native mobile clients, any pointers appreciated!

There were no updates during the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. editor chat for Navigation Block & Navigation Editor, Global Styling or Patterns.

Task Coordination

@mamaduka

@mciampini

Lots of work to support folks working mainly on Styling controls (including Global Styles). Mainly refining the ToolsPanel component and color-related components and screens.

@annezazu

I am working on user docs. The FSE Outreach program’s latest call for testing, triaging GitHub issues, and testing things as much as I can manually.

Open Floor

@annezazu

I’d like to mention the latest call for testing https://make.wordpress.org/test/2021/11/08/fse-program-testing-call-11-site-editing-safari/ There are two weeks left to participate and it’ll be a huge help for 5.9/beyond to get feedback on the features this test is dedicated too.

@paaljoachim

I see there has been some discussions around the template editor appearance menu for WP 5.9.
@jameskoster
Kelly and I shared designs a few weeks ago. One idea was on creating new template list views. The initial groundwork can be seen in Add templates list page for site editor.

@siobhyb

Why is adding extra contexts not considered the best practice such as attempting to customize the Gallery’s inner blocks? For additional information check this Slack thread.

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

CSS Chat Agenda: November 18, 2021

The next weekly CSSCSS Cascading Style Sheets. meeting is today Thursday, November 18, 2021, 12:00 PM EDT 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/.. If there are any other topics you’d like to discuss, please leave a comment on this post.

Meeting Agenda

  • Welcome
  • Announcements & housekeeping
    • Revisit facilitator schedule
  • CSS Custom Properties (#49930)
  • CSS Audit Improvements & other projects
  • Open floor / CSS link share

See you there!

#agenda, #core-css

CSS Chat Summary: 11 November 2021

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

Announcements & housekeeping

Meeting time

  • Last week we initially discussed updating the meeting time to suit people’s schedules better. This week we discussed it further and agreed to try 17:00 UTC.
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. will remain on the first Thursday of the month but will now start at 18:00 UTC
  • The next meeting will be on Thursday 18 November at 17:00 UTC. Please add your name to the Meeting Facilitator schedule document if you would like to contribute by facilitating this or any future meetings
  • We’ve added a new Notetaker column to the facilitator schedule – please add your name if you would like to write up the meeting notes! @danfarrow offered to act as a fallback notetaker if nobody else steps forward

CSS Custom Properties (#49930)

  • Last week we discussed updating the targeted release to 6.0, which would give us an --experimental deadline of early next year, unless we manage to get testing done early in the release

CSS Audit project

  • @joyously had asked about the format of colour values in the CSS Audit report and if visibility could be improved. @danfarrow suggested that the values could be moved to appear beneath the colour “chips”
  • @danfarrow also suggested that improvements could be made to the report. Since the report deals with tabular data we could use HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. tables in conjunction with a table library like Filament Group’s Tablesaw to enable responsive, sortable tables
  • @notlaura raised the topic of CSS linting, linking an older comment from @tellthemachines pointing out the core CSS doesn’t adhere to our custom WP config. @ryelle clarified that 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/ is, but not core CSS, and shared ticket #29792 (she added that getting it implemented would involve fixing 6,000+ errors – yikes!)

Thanks everybody!

#core-css, #summary

Performance team meeting summary – November, 16 2021

This is the agenda for the meeting. You can read the logs here on Slack.

Focus group projects discussion

@audrasjb made an update about the progress for the Site Health group. Here’s the document with details about two projects for the focus group. The next step for this group is to use the next Site Health meeting time slot (November 22, 2021, at 16:00 UTC) to discuss these 2 projects.

@adamsilverstein shared that the Images focus group has a long list of ideas. The next task for this group would be to describe these ideas based on the template; listing their impact, complexity etc. and then based on that prioritizing the work of the group.

Should the performance team have its own Make blogblog (versus network, site)?

@spacedmonkey raised this question about having a Make blog for the Performance team.

@flixos90 mentioned that performance encompasses all areas of WordPress. And that having a dedicated performance blog is likely less impactful than posting in the area(s) where a certain topic mostly applies to – a dedicated performance blog may end up in some sort of silo, where only people who are into it anyway become aware of it.

Weekly meeting time

The team has voted to move the meeting time one hour later, at 4:00 PM UTC. The new meeting times are also updated here.

Object caching focus group

The object caching focus now has 7 contributor votes on the focus groups spreadsheet. With so many interested contributors, it is relevant to make it a focus group. @tillkruess and Dustin Rue will be the POCs for this focus group.

#meeting, #performance, #performance-chat, #summary