Editor Chat Agenda: 31 March 2021

Facilitator and notetaker: @paaljoachim is stepping in for @ajitbohra

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

  • 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.3 release.
  • WordPress 5.7.1 maintenance release.
  • 5.8 Pre-planning
  • Monthly Plan for March 2021 and key project updates:
    • Global Styles.
    • 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. 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.
    • Navigation block.
    • Full Site Editing.
  • 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

CSS Chat Summary: 25 March 2021

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

Housekeeping

  • Reminder that from next week (01 April) onwards the meeting time will change to 9pm UTC
  • The bugscrub time will similarly be brought forward one hour to 8pm UTC

Share mock-ups with color custom property naming

  • We had no mock-ups to share this week so we decided to move this to next week’s meeting: Please bring a mock-up of either the adminadmin (and super admin) bar or a dashboard 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., styled using CSSCSS Cascading Style Sheets. custom colour properties, to the meeting on 01 April!

Project updates

CSS audit (#49582)

  • @notlaura’s PR for the typography audit is ready for review
  • The next steps will be moving the repo to the WordPress org on githubGitHub GitHub is a website that offers online implementation of git repositories that 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 by the repository owner. https://github.com/, then posting on Make to share the audit with the community

Colour scheming (#49999)

Open Floor + CSS Link Share

CSS deprecation

  • @tellthemachines brought up this issue and shared a link of the discussion on this topic from 2013
  • @ryelle supported the need for a CSS deprecation path, having recently found some CSS in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for a feature that was removed 9 years ago!
  • @notlaura agreed and suggested we put this on the agenda for the meeting-after-next (08 April)

Thanks everyone!

#core-css, #summary

Discussion: add a testing template to Trac

During the release cycle of WordPress 5.6, the focus lead, @monikarao, together with other people in the cohort, brainstormed ideas to encourage more testing.

One of the ideas is to add a template to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. so that when a new ticketticket Created for both bug reports and feature development on the bug tracker. is created the reporter is prompted to add information about the testing steps, not only the bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. or the enhancementenhancement Enhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. proposed.

Right now tickets are opened without instruction on how and what to test. During triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions, scrubbers sometimes add the request manually, but the process could be automated.

Add a template

When reporters create new tickets they will be prompted to add these information:

  • List the exact steps necessary to reproduce the problem.
  • Specify the environment details where you reproduced the issue, e.g. WordPress version, PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version, browser & version, operating system & version, plugins installed, and their versions.
  • Paste any relevant error messages.
  • Are there any workarounds for this issue?
  • How can this issue be tested to ensure it’s fixed? Apply 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.? Check the console? Check the front-end before and after? etc…
  • Are there any testing dependencies, such as a 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. or script?
  • What is the expected behavior after applying the patch?

How-to guide

Write a short page that explains every one of those prompts, with examples and explanations on why it is important to test. Add the link to new tickets.

Notify coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-test

If the tickets is high-priority, notify the #core-test channel in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.

What do you think?

I opened a ticket in Meta for this, and @dd32 encouraged me to discuss it here first, so here I am 🙂

Do you think having a template is useful? For every new ticket? What about stale tickets? Do you think notifying the core-test channel is necessary? What do you think should be the flow?

Thanks!

#test

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

  • 27 commits
  • 41 contributors
  • 60 tickets created
  • 13 tickets reopened
  • 51 tickets closed

Reminder: WordPress 5.7.1 is planned for April 14, 2021, so we are currently in the development cycle of the next point 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..

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.

Code changes

Administration

  • Use a darker gray color for various adminadmin (and super admin) UIUI User interface items – #52760

Build/Test Tools

  • Remove explicit puppeteer dependency – #52843
  • Update some devDependencies#52624
  • Run code coverage workflow when the file is updated – #52786
  • Run code coverage workflow using parallel jobs – #52923
  • Do not checkout the Importer 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. in the Code Coverage workflow – #52625
  • Fix code coverage reporting to generate report from src#52786, #51734
  • Run test workflows on old branches on a schedule – #52653
  • Disable fail-fast for the NPM testing workflow – #52625

Bundled Themes

  • Twenty Twelve: Change theme version back to 3.3#52704

Documentation

  • Spell “non-existent” in a consistent way – #52628
  • Fix description for $htmlhint argument in code editor settings – #52628

Editor

  • Add image default size to blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor settings – #52896
  • Add new theme categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. for block types – #52883

General

  • Check if the _export_data_grouped post 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. is an array when generating a personal data export file – #51423
  • Correct expected data type for WP_User_Search::$page property – #51423

Login and Registration

  • Restore the “Error:” prefix for the “Unknown username” message – #52914, #52915
  • Add the “Error:” prefix to some password reset messages – #52914
  • Prevent button misalignment on login screen – #52834
  • Prevent button misalignment on password reset screen – #52834

Media

  • Conditionally pass 2nd parameter to getimagesize()#52826

Posts, Post Types

  • Remove / from non-self-closing “clear” div tags – #52878

Privacy

  • Print screen reader text for the “Copy suggested policy text…” action button – #52891
  • Privacy: Wrap text in buttons on privacy policy guide – #52751

Query

  • Consistently include a space in parentheses in WP_Meta_Query::get_sql_for_clause()#49279

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/

  • Prevent database error when deleting meta data – #52787

Robots

  • Remove contradictory directive check in wp_robots()#52713

Script Loader

  • Escape HTML5 boolean attribute names – #52894

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.

  • Use a consistent check for the $rewrite['hierarchical'] parameter – #52882

Props

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

@SergeyBiryukov (7), @sabernhardt (5), @audrasjb (5), @jrf (3), @hellofromTonya (2), @mukesh27 (2), @ryelle (2), @johnbillion (2), @dd32 (2), @xknown (2), @whyisjake (2), @Mamaduka (1), @grapplerulrich (1), @Tkama (1), @davidbaumwald (1), @flixos90 (1), @jaymanpandya (1), @Cybr (1), @paaljoachim (1), @palmiak (1), @joyously (1), @BrechtVds (1), @goaroundagain (1), @TimothyBlynJacobs (1), @sumitsingh (1), @akabarikalpesh (1), @tmatsuur (1), @hareesh-pillai (1), @kaavyaiyer (1), @jillebehm (1), @pavelvisualcomposer (1), @terriann (1), @RogerTheriault (1), @rinatkhaziev (1), @peterwilsoncc (1), @Mista-Flo (1), @hellofromtonya (1), @azaozz (1), @desrosj (1), @isabel_brison (1), and @matveb (1).

Please welcome our 5 new 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 of the week ♥️
@BrechtVds, @sumitsingh, @kaavyaiyer, @jillebehm, and @pavelvisualcomposer.

Core committers: @sergeybiryukov (9), @desrosj (8), @peterwilsoncc (6), @davidbaumwald (4), @gziolo (2), and @ryelle (1).

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

Discussion summary: Dropping support for IE11

As a follow-up to the very active discussion around the proposal to drop support for IE11, there is a majority agreement to move forward with dropping support. The next steps are to figure out a timeline and what it means for projects/teams to drop the support.

Regarding timeline, there are two upcoming milestones where support could be dropped: 5.8 and 5.9. The argument for dropping in 5.8 is to realize the change and improvement quicker, while others are inclined to wait until 5.9 to provide a longer window between the official announcement and the effective date.

The decision when will be left to the release team for WordPress 5.8; this team is not formed yet as it depends on the April go/no-go Full Site Editing merge.

This post was written in collaboration with @mkaz, @annezazu, and @youknowriad.

#accessibility, #browser-support, #performance

CSS Chat Summary: 18 March 2021

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

Housekeeping

  • Following last week’s discussion we agreed that, from 01 April onwards, the meeting time will advance from 10pm to 9pm UTC to accommodate daylight saving time
  • The bugscrub time will similarly be brought forward one hour from 01 April onwards

Project updates

CSSCSS Cascading Style Sheets. audit (#49582)

  • @ryelle‘s audit tool is nearly ready to share with the wider community once the “container audit” feature is in place
  • The PostCSS PR is tested & ready to merge. UPDATE: Now merged, thanks @ryelle!
  • @notlaura asked if the tool is ready to have its repo moved into the WordPress org. @ryelle will ask in #meta

Colour scheming (#49999)

  • We will have another mock-up share at the next meeting (25 March). If you’re able to please bring a mock-up of a component of your choice using custom properties
  • @ryelle reported having updated her mockup to use a roughly --prefix--location--property--state naming pattern e.g. --wp-admin--button-primary--hover
  • In @ryelle’s example some custom properties are derived from other custom properties e.g. --wp-admin--button-secondary--text: var(--wp-admin--button-primary). Users could override these derived values as required

Open Floor + CSS Link Share

With that the meeting drew to a close. Thanks everyone!

#core-css, #summary

Dev Chat meeting Summary – March 24, 2021

This is the weekly meetings summary of the WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team. The facilitator for this week’s chats was @peterwilsoncc at 05:00 UTC and @audrasjb at 20:00 UTC. Here is the meeting agenda.

Link to 05:00 UTC devchat meeting on the core channel on Slack

Link to 20:00 UTC devchat meeting on the core channel on Slack

Announcements & News

There is also a couple items on the Make/Core blogblog (versus network, site) that require feedback:

Upcoming WordPress Releases

WordPress 5.7.1

In line with the trial for consistent minor release leads for each major branch, all the 5.7.x point releases will be led by @peterwilsoncc, with @audrasjb as deputy.

Here is the expected 5.7.1 release schedule:

  • 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).: Wednesday 7 April, 2021 around 23:00 UTC
  • Final release: Wednesday 14 April, 2021 around 23:00 UTC

For now, there are 26 tickets in the milestone.
11 of them are closed as fixed, or reopened for backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. operations.

@audrasjb plan to run a 5.7.1 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 on Thursday March 25, 2021 at 22:00 UTC. Everyone is welcome to attend.

Please note that this WordPress 5.7 board is the one to watch for 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/ updates that will need to land in this release.

WordPress 5.8

@chanthaboune shared some news about WordPress 5.8: @francina started to compile the planning round up and will publish it soon. @lukecarbis, @boniu91 and @hellofromtonya also compiled an early 5.8 bug scrub schedule, and published it right after the devchat.

Component maintainers updates

General (@sergeybiryukov): Work has continued on further fixing jQuery deprecations in WordPress core. See ticketticket Created for both bug reports and feature development on the bug tracker. #51812 for more details.

I18Ni18n Internationalization, or the act of writing and preparing code to be fully translatable into other languages. Also see localization. Often written with a lowercase i so it is not confused with a lowercase L or the numeral 1. Often an acquired skill. (@sergeybiryukov): The list of translations for selecting a timezone in General Settings was updated to add two new timezones and remove some older duplicates. See ticket #52861 for more details.

Build/Test Tools (@sergeybiryukov): no major news this week.

Date/Time (@sergeybiryukov): no major news this week.

Permalinks (@sergeybiryukov): no major news this week.

Themes (@williampatton): the component has had quite a lot of eyes recently but extra help would be appreciated.

Site Health (@clorith): the component has one ticket for 5.7.1, it’s got a proposed solution and feedback. Everyone is welcome to contribute.

Upgrade/Install (@audrasjb): no major news this week.

Menus / Widgets: @audrasjb started to silently scrub both of their awaiting review tickets, in order to prepare 5.8 effort.

Toolbar (@sabernhardt): there is a Toolbar component triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. scheduled on Thursday March 25, 2021 at 15:00 UTC. Also, the Core team nominated @sabernhardt as Toolbar component maintainer and he accepted.

Open floor

@isabel_brison requested some feedback on an overview ticket for adding end-to-end tests to WordPress Core.
The ticket contains suggestions for how to test most of the pages in the WordPress dashboard but requested some feedback on how to, or whether to, test certain pages.

@francina provided a document produced by her colleagues at Yoast recently. These are now available on the ticket.​

@clorith started a discussion on more frequently merging updates from the Gutenberg pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. in to Core. Highlighting that this would make testing future releases of WordPress features easier without keeping track of which features will remain in the plugin for the time being. There was general support for the idea.​ @chanthaboune is offered her help to move this forward.

@estelaris requested assistance for the Docs team in reviewing end user documentation. Particularly some of the more technical details. Anyone wishing to offer assistance can get in touch via the #docs channel in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ or by messaging @estelaris directly.​

@peterwilsoncc requested some highlighted the workflow report for the 5.7.1 release due in April. For contributors wishing to write code and see it released quickly, Peter recommend they review tickets on the “needs 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.” section of the report. Contributors wishing to test or review suggested code can review tickets on the “has patch/needs testing” section of the report.

@webcommsat requested people share two items with the marketing team via shared documents:

Thanks @peterwilsoncc for his help to compile the meetings notes.

#5-7-1, #5-8, #dev-chat, #summary

CSS Chat Agenda: March 25, 2021

Note: 1 hour before the meeting this week, @ryelle will lead a bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. scrub of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. tickets!

This is the agenda for the upcoming CSSCSS Cascading Style Sheets. meeting scheduled for Thursday, March 25, at 10:00 PM UTC. 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
  • Discuss: Share mock-ups with color custom property naming for another UIUI User interface component besides the button.
  • Project Updates
  • Open Floor + CSS Link Share

#agenda, #core-css

Early Bug Schedule for 5.8

As we begin to kick off work on 5.8, it’s time to schedule some early 5.8 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 sessions.

These scrubs will happen twice a week. For the most part, they’re scheduled for Tuesdays at 6:00 UTC for APAC timezones and 19:00 UTC for US / EU, though there are some adjustments to accommodate religious and national holidays.

Right now, we’re only including Early Scrubs. A release schedule for Alpha, 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 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). scrubs will follow soon.

Early Scrubs:

Focus: early tickets, tickets that require more time or early testing.

Check this schedule often, as it will change to reflect the latest information.

What about recurring component scrubs and triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. sessions?

The above 5.8 scheduled bug scrubs are separate and in addition.

For your reference, here are some of the recurring sessions:

  • Design Triage: Every Tuesday 16:00 UTC in the #design channel (for both coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 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/).
  • 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) Scrub: Every Friday 14:00 UTC in the #accessibility channel.
  • APAC-friendly Scrub: Every Tuesday at 05:00 UTC in the #core channel. This scrub will continue during the cycle, alternating focus between core and editor.
  • Testing Scrub: Every Friday 13:30 UTC in the #core channel, starting April 2.

Want to lead a bug scrub?

Did you know that anyone can lead a bug scrub at anytime? Yes, you can!

How? PingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me (@lukecarbis) on slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ and let me know the day and time you’re considering as well as the report or tickets you want to scrub.

Where can you find tickets to scrub?

  • Report 5 provides a list of all open 5.8 tickets:
    • Use this list to focus on highest priority tickets first.
    • Use this list to focus on tickets that haven’t received love in a while.
  • Report 6 provides a list of open 5.8 tickets ordered by workflow.

Need a refresher on bug scrubs? Checkout Leading Bug Scrubs in the core handbook.

Questions?

Have a question, concern, or suggestion? Want to lead a bug scrub? Please leave a comment or reach out directly to me (@lukecarbis) on slack.

#5-8, #bug-scrub

Core Editor Meeting Notes 24 March, 2021

This post summarizes the latest weekly Editor meeting (agendaslack transcript). This meeting was held in the #core-editor SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ channel on Wednesday, 17 March, 2021, 10:00 AM EDT and was facilitated by @andraganescu.

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

At the time of the meeting the release process was having some issues, looked at by @gziolo and @bernhard-reiter

WordPress 5.7.1 maintenance release

WP 5.7.1 RCrelease candidate One of the final stages in the version release cycle, this version signals the potential to be a final release to the public. Also see alpha (beta). 1 will be on Wednesday 7 April, 2021 around 23:00 UTC and according to @noisysocks  the WordPress 5.7 board is the one to watch for editor updates that will need to land in this release.

Monthly Priorities

The monthly post outlining Gutenberg’s priorities for March 2021 is available.

Global Styles

@nosolosw shared this week’s global styles update:

  • Merged a few important things 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.: add a layout config in theme.json, allow themes to use any style via theme.json whether or not the block supports it, translationtranslation The process (or result) of changing text, words, and display formatting to support another language. Also see localization, internationalization. for custom templates.
  • Continue iterating on the blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. supports mechanism: allow skipping the serialization of border.
  • Some bugfixes: PR:30088.

Ongoing/Next tasks necessary for MVPMinimum Viable Product "A minimum viable product (MVP) is a product with just enough features to satisfy early customers, and to provide feedback for future product development." - WikiPedia:

And more:

Full Site Editing (FSE)

@youknowriad and @vindl shared this week’s update:

  • working on making sure the frontend and backend are equivalent for all blocks and themes (as much as we can). The idea being that a user can open the site editor in an unstyled theme, start blank, add blocks bit by bit and having everything look as expected (front and back)

Infrastructure and UI milestone update:

  • Fix for template saving issue after switching FSE themes should be merged soon in PR:29842
  • Experiments to open browsing 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. to the appropriate template sub-menu landed today (PR:26964PR:30098)
  • Persistent List View now has visual support for multiple selected blocks (PR:29878); its performance has also been improved (PR:29902)
  • Block toolbar is no longer overlapping the navigation panel (PR:29918)
  • Browsing sidebar will now close after template selection (PR:29956)
  • PR for template part block variations in the Inserter was merged (PR:30032), which should unblock the continuation of our work on semantic template parts

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 navigation editor)

@andraganescu and @grzim shared this week’s update:

  • the widgets editor progressed a lot by having two PRs landing, one that updated the REST API to work better with widgets and one that added the block inspector as a sliding panel to 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.. Work continues, and the aim is to have blocks in customizer functional in the 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 the end of the month. Be sure to check things in #feature-widgets-block-editor 

Navigation editor update:

  • Minor improvements in styling PR:30168PR:29832, PR:30129, PR:29975
  • Theme location settings moved to sidebar and have more features PR:29458
  • Fix of navigation editor toolbar which was disappearing in small screensPR:29967
  • Use the interface package for the navigation screen PR:30013
  • …and there are also a few other PRs that are nearly completed.

Navigation block

@joen shared this week’s update:

  • Layers of CSSCSS Cascading Style Sheets. has been refactored, dead code removed, inheritance fixed so styles work, and in general from here on out it will just be a great deal easier to manage. At the moment we’re also working on a hamburger menu for better responsive behavior, and it’s looking great already.

Mobile/native

@hypest shared this week’s update:

  • Landed various E2E tests related fixes, a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) improvements in UnitControl/StepperCell/RangeCell, removed the cancel button from many settings options on Android, split/merge regressionregression A software bug that breaks or degrades something that previously worked. Regressions are often treated as critical bugs or blockers. Recent regressions may be given higher priorities. A "3.6 regression" would be a bug in 3.6 that worked as intended in 3.5. on Android fixed
  • In Progress and Next up: same as previous week’s update

Task Coordination

@annezazu

  • FSE Program wrangling (responding to feedback, triaging, figuring out what’s next to test, etc), testing FSE everyday (lots of reported bugs), and some light triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.!

@ntsekouras

  • Keep on explorations with block patterns integrations mostly on Patterns transforms(PR:29890) – could use some feedback/testing there 🙂
  • Expose Template part block variations to Inserter
  • Code reviews and triaging

@andraganescu

  • I have merged a few small PRs, triage and code review mainly for the new block editors (widgets and navigation).

@mamaduka

  • Image block now will use image default size from settings. PR:29966
  • Added since parameter to the deprecated function. PR:30017
  • Added/Updated since versions for deprecated features. PR:30072
  • Created PR for Gallery Block pattern to prevent adding all images when adding media. PR:30122

@paaljoachim

  • Triaging.
  • Focusing on getting more exposure on basic Full Site Editing user issues. Such as the preview drop down, easier save, editing template/post content etc 
  • Just made an issue for using a big modal to have a common approach for editing templates/reusable blocks/patterns.

@rafaelgalani

  •  I worked on some small PRs to fix some bugs 

Open Floor

@paaljoachim reminded that the new Gallery Block which uses Inner Image blocks has a call for testing. It is a new and awesome way to use the Gallery block, and it has a lot of potential. Go and test it..:)

#chats, #core-editor, #meeting-notes