DevChat meeting Summary – May 5, 2021

Agenda for the two meetings. Thanks to @peterwilsoncc and @jeffpaul for leading the 05:00 and 20:00 UTC devchats respectively.

Link to 05:00 UTC devchat meeting archive in Slack // Link to 20:00 UTC devchat meeting archive in Slack

Announcements and news

These posts need your feedback:

  • @ryokuhi published a proposal on Make/Accessibility about a new Trac workflow keyword that the 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) team would like to consider.  If you feel particularly opinionated or passionate about this, please comment on the post.
  • @jeffpaul and @desrosj published a request to Component Maintainers, Feature plugin authors, and the Gutenberg team to share plans / help needed for 5.8 (primary focus will be FSE).  Please comment on the post to help ensure we’re tracking the right work for the release.
    • @youknowriad noted that required Gutenberg changes in Core are made as filters/extensions points and brought to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. as part 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/ merge that happens regularly
    • @mkaz shared the WordPress 5.8 Must Haves project board on GitHub as outline of Gutenberg work for 5.8

5.8 Review

  • Schedule confirmed including bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub schedule
  • @youknowriad shared that trunk is already on Gutenberg 10.4, @gziolo is working on updating it to 10.5 and the big changes (Global styles infrastructure in themes.json and FSE blocks) are coming in 10.6
  • Feature freeze on Tuesday May 25th (19 days from now) defined as “During the following two weeks, there will be no commits for new enhancements or feature requests. 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. will focus on defect work (aka outstanding bugs)
  • 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 on Tuesday June 8 (33 days)
  • RC 1 on Tuesday June 29 (54 days)
  • Release on Tuesday July 20 (75 days)
  • Current list of tickets that are on the 5.8 milestone, list of good-first-bugs tickets

Component maintainers and committers update

  • @sergeybiryukov shared Plugins update that Parameter names in 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 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. functions now use consistent terminology when referring to actions, filters, and callback functions via #50531
  • @sergeybiryukov shared Themes update that #49487 removes the “Featured” tab on Add Themes screen to match an earlier change in the Theme Directory
  • @webcommsat shared About/Help update that ticketticket Created for both bug reports and feature development on the bug tracker. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. continues with @marybaum
  • @audrasjb shared Menus update that #21603 is being reviewed
  • @audrasjb shared Upgrade/Install update that the last meeting recap includes a project for the next few releases

Open Floor

Props to @audrasjb, @webcommsat and @marybaum for reviewing this post.

#5-8, #accessibility, #dev-chat, #docs, #fse, #full-site-editing, #github, #learnwp, #summary, #updater

Media Meeting Recap – May 6, 2021

The following is a summary of the weekly Media component meeting that occurred on Thursday, May 6, 2021 at 14:00 UTC. Weekly media meetings are held every Thursday at 14:00 UTC. A full transcript can be found here in the #core-media room in the Make WordPress Slack.

Attendees: @antpb, @mista-flo, @chaion07, @adamsilverstein, @paaljoachim, @hellofromtonya, @sergeybiryukov, @desrosj

Media 5.8 tickets

This meeting’s discussion focused around WebP and 5.8 Media features.

#35725: Add WebP support – WebP support has been merged! Please test on all configurations possible to ensure there are no edge case issues. Big props to @adamsilverstein and all who helped make this happen! Adam mentioned that a post is in progress that will provide an overview to the new WebP supports.

#52876 Add capability to set default format for image sub-sizes. – This ticketticket Created for both bug reports and feature development on the bug tracker. is in progress and adds a new 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. where people can set a default image type such as WebP. @adamsilverstein has asked for some testing assistance to ensure everything works as intended. Testing instructions can be found here.

#50105: Remove infinite scrolling behavior from the Media grid – It was agreed during the meeting that for the button that moves focus to the first newly loaded media item, “Jump to first loaded item” is a great way to make this not focus on images or any other specific media type and still be clear. @hellofromtonya mentioned in the meeting on the pending count issue, “I think it would be a better experience for users if we could solve it before 5.8 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.. That said, it would be good to get the patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing. committed and then work on that specific issue as a follow-up.” It was agreed by multiple participants in the meeting that landing this sooner and iterating is ideal.

#37255: Update attachment functions to accept a post object in addition to ID@hellofromtonya mentioned keeping this ticket focused on resolving the issues that were identified and moving any broader scope to a separate issue to avoid this being punted to a future release again.

Props @antpb for proofreading and final review.

#core, #media, #summary

Test scrub for WordPress 5.8

As a part of the 5.8 release, we’ll be hosting test scrub for WordPress 5.8 on 2021-05-07 13:15 in the core-test channel.

We’ll do manual testing of the below tickets:
https://core.trac.wordpress.org/ticket/43697
https://core.trac.wordpress.org/ticket/50866

We’ll appreciate your participation and feedback!

What you need

How to apply a 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.

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., for example 35449

npm run grunt patch:35449

How to fetch and then checkout a PR, for example, PR 828

git fetch upstream pull/828/head:pr-828
git checkout pr-828

or for PR:

npm run grunt patch:https://github.com/WordPress/wordpress-develop/pull/828

Check the handbook for more ways to test patches.

Looking forward to seeing you!

#core-test, #testing

CSS Chat Agenda: May 6, 2021

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday, May 6, at 5:00 PM EDT. This meeting will be held in the #core-css 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 there’s any topic you’d like to discuss, or if you have suggestions for discussion questions, please leave a comment below!

  • Housekeeping
    • Check in on bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub frequency
  • Project Updates
    • CSS Audit (#49582)
    • Color Scheming (#49999)
    • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSS deprecation path (#53070)
  • Open Floor + CSS Link Share

#agenda, #core-css

Editor chat summary: 5th May 2021

This post summarises the weekly editor chat meeting (agenda here) held on 2021-05-05 14:00 UTC in Slack. Moderated by @get_dave.

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 release

  • At the time of the meeting the latest release was 10.5.4.
  • @get_dave noted 10.6 RC is due today (May 5th) with the stable release on May 12th.
  • Riad asked for volunteers to release the RC for 10.6 – this was completed post-meeting by @vdwijngaert.

WordPress 5.8

  • Feature freeze for Gutenberg for WordPress 5.8 is May 19th (10.7 RC).
  • The release schedule for WP 5.8 is available.
  • Riad noted that to follow the progress, we have these two things:
    • A project to see all the different mandatory tasks for this release.
    • A merge issue to track the progress of the integration of the Gutenberg updates into 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. before feature freeze date.
  • Riad asked for folks to review and help with the experimental APIs in this Issue.
  • @gziolo is already working on bringing Gutenberg 10.5 into WordPress trunk.
  • @youknowriad is the Editor Tech lead for 5.8.

Full Site Editing Next Steps

  • Reminder about Hector Prieto’s Full Site Editing Go/No Go: Next steps post which summarizes scope for Gutenberg in WordPress 5.8.
  • To summarise, the scope is roughly:
    • 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. theme building
    • Theme blocks (eg: Query, Navigation, Site Logo…etc) 
    • Template editing within the post editor
    • Widgets Editor & Block Widgets 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. 
    • Persistent List view in the post editor
    • Duotone design tool 
    • Gallery block refactor
  • Riad said we’re already in a good state as everything is developed but we may still have to do some calls about whether to keep everything or reconsider some parts of it.

What’s new in Gutenberg

@ajitbohra posted What’s New In Gutenberg for the end of April.

Highlight’s included:

  • New block patterns and pattern transformations
  • “Template Editing Mode” – enables editing templates without leaving the Post Editor.
  • File Block now supports embedding PDFs in most major browser
  • Block widgets in the Customizer now have media upload and richtext formats.
  • Fix autoscrolling when selecting partially “off screen” blocks.

Key Project updates

Updates were requested for the key projects.

Global Styles

@nosolosw provided an update async via a Github Issue. I have omitted it here for brevity.

@youknowriad also provided us with a summary update:

  • the new 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. format merged
  • we’re making theme.json stable (no more experimental-theme.json ) in 10.6.

Block based 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. Editor and Customizer.

@andraganescu provided the update.

  • The widgets editor has gone through an amazing round of polish.
  • Grouped up only late last week, this week all the major testing blockers have had their fixes merged in time for the new Gutenberg release.
  • The aim is to have a call for testing as soon as possible to collect feedback on the state and progress of the project.

Navigation Block

@joen provided an async update:

@mkaz also provided:

  • Responsive hamburger menu aiming for GB 10.7 PR-30047 eyes welcome
  • Dynamic Home URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org is the last must-have for 5.8 in progress and looking good  PR-30926
  • Refining placeholder and design

Navigation Editor screen

@get_dave provided an update:

  • The Nav editor continues to see steady progress.
  • We now have all entity (post, page, 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.)…etc) block variations serialising to/parsing from their respective nav_menu_items. So when you add a Post link it stays synced to that Post.
  • We also have lots of work going on regarding notifying users about unsaved changes.
  • Both nav block and editor features have also seen background improvements to stability and test coverage.

Full Site Editing

The meeting agreed this was mostly covered by the above items.

@paaljoachim did ask if someone could provide an async update on the Page templates.

Feel free to leave an update in the comments if you have one.

Mobile Team

Task Coordination

@annezazu:

@aristath:

  • Last week was Greek/Orthodox Easter so it was a half working week here:
  • Continued working on PR to autogenerate anchors for headings – #30825. Could use a review after today’s updates.
  • Font-sizes can now use non-px values – #31314
  • WIP – Worked on splitting the theme.css file to conditionally load parts for rendered blocks only – #31239 (same as what we previously did for the style.css file).
  • This week & next week I plan to continue working on 5.8 tickets, converting the quote block to nested blocks, and improving the sustainability of block themes. Hopefully I won’t need to continue working on the autogenerate-anchors PR ’cause it will be merged.

@mamaduka:

  • Primarily focused on the new Navigation Editor.
  • I pushed another update for the “Most used terms” feature and based on the latest feedback. I think it’s in a good place to merge into the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • There’s also a new PR Site/Template editor welcome guide if anyone wants to test and provide feedback.

@paaljoachim:

@get_dave:

@ntsekouras:

@vdwijngaert:

  • Working on an accessible (and reusable) way of describing a path (eg: go to Settings > Reading) to follow, came up in 31122
  • Resuming work on the first step of duplicating post/page title to the top toolbar (issue: 27093, PR: 31288 )
  • Tweaking the ImageResizeControl behavior, now it returns NaN when empty or 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. 31355
  • Gave a go at fixing block conversion for <!–more–> tag in the middle of a paragraph 31374, could use a review.

@desrosj

@jorgefilipecosta:

  • Helping the merge of the theme.json shape changes (with reviews suggestions etc).
  • I also made some PR reviews not related to global styles.
  • I added some PR’s removing unused code 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.’s and stabilising other API’s.
  • Changed the way the global styles cpt is associated to a theme to use a 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. like the other FSE post types do.
  • Finishing a refactoring to the link color to use an elements + the same mechanism as duotone/layout instead of css variables.
  • I will work on moving theme.json to core and the code changes required to be core first code.
  • I plan on fixing some old issues/tasks where I have been pinged and have some insights.
  • And if time allows I plan on starting the work on dashboard that shows the performance metrics on each commit merged to trunk.

Open Floor

Note for task coordination purposes: Automattic will be on remote virutal meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. next week.

@annezazu noted for task coordination purposes that much of Automattic that focuses on the editor space is going to be on a remote, virtual  meetup next week (12th & 13th). It might mean less of us coming to the core editor chat or slightly less responsiveness during those days but it’ll probably depend on the person.

Please reconnect your 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/ and 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/ accounts.

  • @desrosj flagged issue with some GitHub and WordPress.org connections where tokens expired for some users.
  • If you have previously connected your GitHub account to your WordPress.org account, please head over and verify the connection is still active!
  • If you have never connected your accounts, please do! This is a huge help for the release squads when they compile the list of props for a given release.
  • We always want everyone to receive proper recognition for their contributions, and this is a huge help with matching contributions to Gutenberg on GitHub to a .org profile. 
  • More info on connecting your Github profile to your WordPress.org account.

Opt out Plugin to be used to disable the block based Widgets editor.

@paaljoachim wanted to highlight this issue: Add a plugin to disable the block based Widgets editor.

As a plugin has been added if/when a user wants to go back to using the Classic Widget screen. I am hesitant. As it should be easier to jump between old <-> new.

@andraganescu responded:

“Easier” is complex. Adding buttons to switch in and out may sound easier, but using the same system that has been used for years via plugins can be easier as well. Opening that issue, I did think about the option to add an “opt out” button. But that would mean adding an opt in button as well. And that would mean adding a user setting. And, if not a user setting then a way to store the opt in state. This, as the welcome screen in the Guteneberg editor has shown us, is not a reliable way.

@andraganescu indicated there would be a “Welcome screen” on first use of the new Widget editor with clear information about how to install the Plugin to easily opt out.

@andraganescu also confirmed there will be multiple touch points:

  • Post install page.
  • Welcome screen.
  • Make post with more information.

Wrap up

Due to the meeting taking longer than usual @get_dave wrapped up by encouraging any further open floor questions to be left async as a comments (below).

Thanks to everyone who attended.

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

CSS Chat Summary: 29 April 2021

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

Housekeeping

  • A volunteer is needed to lead the next coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. CSSCSS Cascading Style Sheets. bugscrub which is happening on 06 May @ 8pm UTC

Project updates

CSS Audit (#49582)

Color Scheming (#49999)

CSS deprecation path (#53070)

  • @danfarrow noticed there had been some discussion on the ticketticket Created for both bug reports and feature development on the bug tracker. which seems to have stalled

Open floor / CSS link share

Thanks everyone!

#core-css, #summary

Upgrade/Install component meeting notes from May 4th, 2021

On Tuesday May 4, the component held a meeting in the #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 main topic in agenda was the Update the Updaters project kickoff.

These are the decisions taken about it:

  • The group will tackle the outcomes in order, to complete one sub-project before moving to another.
  • The weekly upgrade/install component meeting is back and the updater project will be part of them. Tuesdays at 5 pm UTC is confirmed.
  • @francina will post the agenda and host the meeting. If she isn’t available @audrasjb will step in.
  • @pbiron is going to go through the tickets in the “Outcome 1” list to prioritize them before the next meeting.
  • @audrasjb will refresh his patches as part of the “Outcome 1” drive.
  • The attendees agree that @schlessera‘s proposal to make everything as compatible as possible with WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ should be part of the scope.
  • No additional tools will be used to keep track of the project at this time since it’s a small group of people working on it. If there will be more contributors (🤞), the decision will be revisited.

The attendees also checked an open ticketticket Created for both bug reports and feature development on the bug tracker. on TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. (#53049) and agreed that it’s a good idea to include a changelog in the autoupdate emails that users that have opted-in to this service receive.

See you next week!

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

Upgrade/Install component meeting agenda for May 4th, 2021

Next meeting is scheduled on Tuesday May 4, 2021 at 19:00 UTC+2 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 with the following agenda:

  • Update the Updaters project kickoff (thanks @francina for putting this post together)
    • Outcome 1 – Make sure the zip uploads and unpacking are safe
    • Outcome 2 – Create a mechanism to upgrade and rollback
    • Outcome 3 – Have managed updates (database migrations)
    • 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
  • Open floor / tickets awaiting review

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

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

A Week in Core – May 3, 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 April 26 and May 3, 2021.

  • 17 commits
  • 28 contributors
  • 57 tickets created
  • 4 tickets reopened
  • 44 tickets closed

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

  • Correctly test grunt clean when built to run from src#52625
  • Improve get_bookmark() test coverage – #52988

Bundled Themes

  • Twenty Twenty-One: Fix “Opening PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 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.) must be on a line by itself” WPCSWordPress Coding Standards A collection of PHP_CodeSniffer rules (sniffs) to validate code developed for WordPress. It ensures code quality and adherence to coding conventions, especially the official standards for WordPress Core. issue – #52938
  • Twenty Twenty-One: Display page title as the H1 heading when a static page is selected as the “Posts page” – #52938

Coding Standards

  • Fix a whitespace at end of line issue in wp-admin/includes/class-wp-comments-list-table.php#52627
  • Use strict comparison in wp-admin/includes/class-wp-posts-list-table.php#52627
  • Update $out in WP_Widget_Pages with a more meaningful name – #53059
  • Fix a precision alignment issue in wp-admin/includes/template.php#52627

Documentation

  • Document the usage of $current_user global in get_user_by()#53088

Editor

  • Fix typo in image default size setting – #52920
  • 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: Update the bundled block patterns – #52846

External Libraries

  • Upgrade PHPMailer to version 6.4.1 – #53114

Posts, Post Types

  • Pass the post object to the_password_form 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.#29008

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

  • Check the results of get_metadata() in WP_REST_Meta_Fields methods – #53099

Toolbar

  • Remove title attribute on pending updates link – #26562, #53031

Upgrade/Install

  • Display 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 update counts on WordPress Updates screen – #53031

Users

  • Share current user instance across functions – #28020

Props

Thanks to the 28 people who contributed to WordPress Core on Trac last week:

@mukesh27 (4), @sabernhardt (3), @audrasjb (3), @peterwilsoncc (2), @hellofromtonya (2), @rmccue (1), @lukecarbis (1), @donmhico (1), @chriscct7 (1), @chaion07 (1), @silb3r (1), @paaggeli (1), @david.binda (1), @gziolo (1), @kjellr (1), @beafialho (1), @melchoyce (1), @onemaggie (1), @mamaduka (1), @ayeshrajans (1), @Mte90 (1), @afercia (1), @Boniu91 (1), @francina (1), @rianrietveld (1), @justinahinon (1), @davidbaumwald (1), and @TimothyBlynJacobs (1).

Congrats to our new contributor of the week: @paaggeli ♥️

Core committers: @sergeybiryukov (10), @peterwilsoncc (2), @joedolson (1), @gziolo (1), @davidbaumwald (1), @desrosj (1), and @youknowriad (1).

#5-8, #week-in-core

Editor chat summary: Wednesday, 28 April 2021

This post summarizes the weekly editor chat meeting on Wednesday, 28 April 2021, 14:00 UTC held in Slack.

GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ 10.5 RC release.

The first topic was the Gutenberg 10.5 release. The RC was already shipped a week before the chat https://github.com/WordPress/gutenberg/releases/tag/v10.5.0-rc.1. @jorgefilipecosta said that we had some PR’s that were cherry-picked since the RC.

The final release was scheduled for the day of the chat. @jorgefilipecosta gave public congratulations to @ajitbohra for the first RC release!

Posts requiring feedback and insights.

@jorgefilipecosta said that we have two important posts published recently that deserve wide attention:

In case anyone has some insights or thoughts to share please leave a comment on the posts! Your insights are appreciated!


Monthly Plan and key project updates.

Global Styles

Shipped this week

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.

block.json / 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. supports

  • duotone #26752
  • padding: fix to allow units other than px #31057
  • font-size: can be used in nodes other than the wrapper #30879
  • border-color: fix for dynamic blocks #31020
  • blocks
    • padding for site title #31125
    • padding and letter casing for site tagline #31042
    • link color for post date #30791
    • table uses now background/text colors from the theme #30791

Internationalization

  • custom templates can be translated via theme.json #29828

KSES

  • fix to sanitizing user styles #30888

Site editor:

  • fixes for preset classes in the site editor #31218 #31217 #31204
  • fix for color selector in the UIUI User interface color panel #31015

Ongoing

theme.json

  • Changes to format #29891 are ready #30541 we’re now testing and polishing. It also includes versioning (aka migrate the older formats to the new one).
  • Improve 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 take data from the theme directly #31267

block.json / block supports

  • typography (line-height, font-weight, etc) can be used in nodes other than the wrapper #30880
  • border and color (background, text) to the pull quote block #30951

New style properties

  • Add support for letter-spacing #31118

Misc

  • Add a new endpoint that exposes block editor settings through 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/. (by mobile to access global styles data) #29969
  • standardize capabilities of wp_template, wp_template_part and wp_global_styles #30893

Priorities

The priority continues to be shipping #29891 as soon as possible to unblock related work.

#28913 is a good issue to look at if you can lend a hand (help with reviews, migrate more blocks, more properties, etc).

Block based 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. and Navigation Editor.

@andraganescu provided the following update:

The legacy widget got an UXUX User experience upgrade and now the default view is the preview while the embedded widget editor 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. had a performance overhaul. The focus on back combat continued with more testing with legacy widgets from various plugins. As expected a lot of new issues were opened.

On navigation editor the steady pace of improvements continued last week. Many thanks for the many welcome contributions!

Navigation block.

@joen provided the following update:

For the navigation block, we recently merged a padding change and I’m doing some followups (submenu gapplaceholder itemsnav screen). Also looking at small separate improvements, and hope to get back to patterns now that the padding change is merged  — thank you for reviews.

Full Site Editing/Page templates

@youknowriad provided the following update regarding page templates:

I’ve spent some time iterating on that on the last days. We now merged the UIs for templates under a single “template” panel in the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme., we iterated a bit on the design of the “frame” to distinguish properly between template and post modes and simplified the save flow a bit. There are a number of iterations we could make, I don’t expect all of them to happen before 5.8, at some point, we’d make a final decision about whether it’s good enough to include.

@ntsekouras made a heads up regarding the query block:

Query block has now a wrapper element which for now is div (and will be the default when more tags will be supported) here: https://github.com/WordPress/gutenberg/pull/30804I’ve added a deprecation so everything will work as before but it will be good to update any block themes you have that use Query.

Task Coordination

@aristath

This past week:

  • Continued working on PR to autogenerate anchors for headings – #30825
  • Continued on @nosolosw‘s existing PR to allow inner blocks in quotes – #25892
  • Sustainability: PR to split theme.css styles and only load the ones for rendered blocks – #31239
  • Smaller PRs, mostly to improve code quality & linting errors
  • Lots and lots of PR reviews

Next week: Continue working on all the things mentioned above

@mamaduka

Helping out with the new Navigation Editor screen:

  • Sync menu name updates.
  • Introduce useMenuEntityProp hook.
  • Better handling of unsaved changes. PRs one and two.

Continued my work on the “Most Used Terms” feature and got great feedback about improvements. Thanks, everyone.Planning to continue working on Navigation Editor tasks.

@paaljoachim

@ntsekouras

@annezazu

Continued FSE Program work with the fifth call for testingpublishing a schedule of upcoming plans, reviewing/adding to a brief FSE doc, and launched a second round of questions. I’m planning to likely do a hallway hangout tomorrow on FSE issues/prs/designs in #fse-outreach-experiment for anyone interested!

@poena

Plans to continue on the site block changes but also I want to test the theme.json format and update the tutorial for creating block themes. Awaiting review of the letter-spacing.

@vdwijngaert

Will be working on a PR for moving the post/page title to the top bar. Current PR: #31240, but going to close that in favor of a new one based on a 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".

@jffng

@jorgefilipecosta

The main goal for next week is to review https://github.com/WordPress/gutenberg/pull/30541 and help it be merged. Plans on reviewing other Global Styles PR that are opened (e.g: https://github.com/WordPress/gutenberg/pull/30880). Wants to fix https://github.com/WordPress/gutenberg/issues/27478, which is probably very simple but may have a considerable impact and should be done ASAP.

Open floor

Post title moving in site editor

@bobbingwide said that there’s a problem moving the post title in the Site Editor. Adding that it’s tricky editing the topmost block if one does not have the toolbar set to top. @joen said @ellatrix is working on a fix https://github.com/WordPress/gutenberg/pull/31134.

G2 Components

@aristath asked the status of “G2 components” and if there is any plan on removing them. @youknowriad said that G2 is not removed but while reviewing some of the integration PRs, he noticed that G2 reimplements a lot of things we already have in Gutenberg in its own way. So the plan is still to integrate it but aligning with Gutenberg practices.

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