Editor chat summary: 31 March, 2021

This post summarizes the weekly editor chat meeting (agenda here) held on Wednesday, March 31, 2021, 04:00 PM GMT+1 in Slack. Moderated by @paaljoachim.

WordPress 5.7.1

WordPress 5.7.1 maintenance release.
The following release schedule is being proposed:
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.

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

What’s new in Gutenberg 10.3.

5.8 Pre-planning

5.8 schedule

Monthly Priorities

March monthly priorities. Along with Key Project updates.

Global Style

Update from @nosolosw

Navigation Editor

Update from @grzegorz

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.

Update from @mkaz

Mobile

Update from @hypest

Full Site Editing

Update from @annezazu

Task Coordination

@annezazu

  • Mainly focused on FSE Outreach program (daily fse testing, reporting issues, writing up summaries, writing tests, amplifying!) and a few CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement post ideas in the pipeline.

@aristath

  • Focus FSE and getting things ready for our MVP for inclusion in core.
  • Past week focused on implementations for hybrid themes, and also adding skip-links to FSE themes.
  • Focus on reviewing PRs.

@ntsekouras

@mamaduka

@poena

  • Reviews.
  • Testing Full Site Editing.
  • Reporting issues and creating pull requests toward the FSE MVP.

Open Floor

Discussing the Full Site Editing MVP.
To summarize the discussion that happened during the meeting and after, here are the top takeways:

  • There is confusion of what MVP for Full Site Editing consists of.
  • As has been previously shared, the MVP should make it possible to build a version of the Twenty Twenty-One theme, using only blocks, without any coding knowledge.
  • Widgets & Navigation work are not included in FSE but they are seen as complementary projects to help with adoption.
  • At the moment we have two targets: the full site editing MVP & what would be introduced in 5.8.

A link to the full discussion on Slack.

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

Dev Chat meeting Summary – March 31, 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 @markparnell at 05:00 UTC and @francina 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

Upcoming 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

There are 33 tickets in the milestone:

  • 10 are already closed as fixed
  • 3 are fixed and reopened for proper 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.

@audrasjb announced a new 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 right after the devchat, and will run another one on Tuesday April 6, 2021 at 20:00 UTC.

Note: At the time this meeting recap is published, there are now 31 tickets in the milestone. 12 are fixed, 4 are reopened. The ticketticket Created for both bug reports and feature development on the bug tracker. with the higher priority was fixed (#52822).

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

@francina shared some blogposts worth reading, where a new, experimental, release cycle is proposed, and the early bug scrubs schedule is now available.

Core related blogblog (versus network, site) posts

Some thoughts were shared about the last item (Add a testing template to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.). People are invited to comment in the blog post.

@francina suggested to follow make.wordpress.org/updates as this blog has updates from Make teams + project leadership.

Component maintainers updates

Build/Test Tools (@sergeybiryukov): Work has continued on backporting recent build and test tool improvements to the older branches still receiving security updates. See ticket #52653 for more details.

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

General (@sergeybiryukov): No major news this week.

Internationalization (@sergeybiryukov): No major news this week.

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

Menus (@audrasjb): JB did some Triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. last week.

Widgets (@audrasjb): no major news this week.

Upgrade/Install (@audrasjb / @afragen): The team is still looking for feedback concerning the feature plugin. @francina asked if it would be useful to organize a test scrub. I would be a nice idea, and @afragen answered there’s a simple way to force the rollback for testing. The Upgrade/Install team will discuss this during the next #core-auto-updates weekly meeting on Tuesday April 6, 2021 at 18:00 UTC.

Toolbar (@sabernhardt): no triage planned this week, but @sabernhardt will probably will have another session in a few weeks.

Open floor

@chanthaboune noted that there are listening hours next week with her and Matt.

@annezazu dropped in a call out to help with the latest call for testing for the Full Site Editing Outreach Experiment: FSE Program Testing 4 – Building a restaurant themed header.

@chanthaboune shared that the recent Slack outage caused some additional things to break, so if folks see things that usually work but aren’t now, please feel free to let her know.

#5-7-1, #5-8, #dev-chat, #summaries, #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, #summaries, #summary

Dev chat summary: March 17, 2021

@francina led the chat on this agenda.

Announcements

The big news: WordPress 5.7 “Esperanza” landed March 9, and the group took a well-deserved bow.

Moving on, Francesca highlighted these posts:

@jeffpaul noted Trial run: Consistent minor release squad leaders for each major branch. Francesca added that the post is both a highlight and a call for volunteers.

@annezazu put out a last call for FSE Program Testing Call #3: Create a fun & custom 404 page. If you’d like to catch up on the previous two FSE tests, Anne and Francesca said you can find previous calls under this tag. If you’d like to do your own testing, the FSE Handbook has a page with instructions. Capping off the FSE discussion was Marketing Team repTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. @webcommsat, who said you can also share this LinkedIn promotion.

@francina then turned to posts that need feedback. This Proposal: A WordPress Project Contributor Handbook drew spirited emoji support from the group. Francesca also reminded the group to sign up for the Updates blog to keep up with a variety of team updates, as well as posts from @chanthaboune about cross-team efforts and the latest news from leadership.

Components check-in and status updates

@sergeybiryukov started with jQuery news: the version in 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. has updated to 3.6.0, which is mostly bugbug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority. fixes and improvements. Two callouts:

Aside from the change to no longer ensure XHTML-compliant tags for you, we do not expect other compatibility issues when upgrading from a jQuery 3.0+ version.

See ticketticket Created for both bug reports and feature development on the bug tracker. #52707 for more details.

 jQuery hoverIntent library has updated from version 1.8.3 to 1.10.1. The changes all appear to be minor.

See ticket #52686 for more details.

@adamsilverstein checked in with Media news: he’s working on landing support for WebP images in 5.8 and would like testing and feedback on ticket #35725.

Up next, @audrasjb said he has nothing new for Menus and 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., but he’s quietly scrubbing bugs and watching tickets. On Upgrade/Install, he highlighted this feature plugin proposal post.

@sabernhardt wrapped up the Component updates with his announcement of a Toolbar triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors./bug scrub for the following day, March 18, at 16:00 UTC.

Open floor

IE11 support

@adamsilverstein asked: Given that the Project has decided to drop support for IE 11, have we discussed a specific release to make that change in?

The discussion that followed outlined a general process—notify, then act—but pointed out the group still needs to make a specific plan for IE11. Adam noted that IE11 is the only major browser that doesn’t support WebP images.

@desrosj said there might already be a notification in place. @adamsilverstein found a ticket, #48743, to that effect. Further discussion also made it clear that the team needs to do more to announce the change, including stronger language in relevant tickets (@desrosj and @audrasjb), a News blogblog (versus network, site) post (h/t: @jorbin) and relevant Handbook updates (h/t @jeffpaul)

“Try FSE?”

@sergeybiryukov observed:

It seems that most of WP users (outside of the contributing teams) are still largely unaware that full-site editing is coming later this year.

Perhaps that’s intentional, but once we have something stable to test, have we considered adding a dashboard widget to one of the upcoming minor releases, to invite more users to test FSE before final release, like we did 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/ in #41316 for WP 4.9.8?

See the full discussion that followed, with a variety of people sharing a variety of views on the subject.

#core, #dev-chat, #meetings, #summaries, #summary

CSS Chat Summary: 11 March 2021

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

Housekeeping

  • @ryelle noted that daylight savings comes into effect in the US on March 13th and asked if we should change the meeting time
  • @danfarrow agreed that it would be good to move the meeting time but maybe not until UK daylight savings has come into effect at the end of the month, as otherwise the meeting would be at 11pm in the UK
  • We agreed that the next meeting should stay as 22:00 UTC and we can discuss the change then – if you have a preference please let us know!

Discussion: Ideas for custom property naming

  • @danfarrow shared his custom property naming for buttons mock-up which, with a little cheating, reduces the custom properties to --button-color,
    button-contrast-color and --button-active-color
  • @ryelle liked the use of the word contrast to clarify the intent of the custom property
  • @ryelle’s --color-$n approach received support from @audrasjb & @danfarrow, however it still has the issue of a lack of context. When defining the numbered colour values it’s not clear what the contrast relationships should be between them
  • We concluded by following up @notlaura’s idea from last week of having people mock-up another UIUI User interface component of their choice with custom properties. It would be great if people could bring their mock-ups to the March 25th meeting!

Project updates

  • There were no project updates this week

Open floor / CSSCSS Cascading Style Sheets. link share

  • @sabernhardt shared a link to ticketticket Created for both bug reports and feature development on the bug tracker. #52760: Color not 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) for AA which @ryelle offered to look at
  • @sabernhardt also asked for anyone with good flexbox knowledge to join the discussion on #28983: Adminadmin (and super admin) bar length or Admin bar on two line

With that our time was up. Thanks everyone!

#core-css, #summary

Dev Chat Summary for March 10, 2021

@francina hosted this agenda.

Announcements

WordPress 5.7 “Esperanza” was released yesterday.

The 5.7 Field Guide is available.

@audrasjb confirmed all documentation is published and noted that HelpHub end-user documentation pages reflect changes introduced in the 5.7 release.

Blogblog (versus network, site) Post Highlights

These posts detail the latest news on 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/:

Blog posts that need feedback

Components check-in and status updates

@francina confirmed that UTC time remains in use for dev-chats due to the overwhelming preference expressed in comments.

@annezazu announced that the third call for testing for the Full Site Editing Outreach Program us underway. Published summary on feedback from the second call expected next week.

@sergeybiryukov announced the NPM test workflow now includes testing for Linux and MacOS to confirm that the scripts used to build WordPress also complete successfully in those environments. Also, the jQuery version in 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. is now version 3.6.0.

Open Floor

@whyisjake expressed interest in joining a 5.7 minor release.

Discussion commenced on the establishment of a formal triage team. @francina, @desrosj, @hellofromtonya, @sergeybiryukov and @jeffpaul shared updates on those currently involved in the process and the steps to include more people.

@audrasjb started a spirited conversation that included @johnbillion, @marybaum, @clorith, @joyously, @jeffpaul, @sergeybiryukov and @ipstenu on the need for clarity on the authorship of the dark mode feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins. and its mention in Make blog posts. @audrasjb welcomed feedback on several questions he asked addressing this.

Props to @audrasjb for review.

#summaries, #summary

CSS Chat Summary: 04 March 2021

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

Housekeeping

  • A leader is needed for next week’s (Thursday 11 March @ 21:00 UTC) coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. 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 – if you fancy doing it please let us know 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/.

Discussion: Compare ideas for naming custom properties for colors in a button

  • In order to start the discussion on naming conventions for custom properties in wp-adminadmin (and super admin) we are asking for people to mock-up examples of how they would name the custom properties for a button
  • @ryelle shared her demo
    • Button appearance is defined in terms of 7 body-level colour variables --color-1, --color-2 etc
    • Colour variations are achieved by overriding the values of the 7 colours
  • @notlaura shared her demo
    • Button appearance is defined by a set of custom properties using a --prefix--element--property[--modifier] naming pattern e.g. --wp-admin-color--button--bg
    • Variations are achieved by overriding the button properties for specific classes e.g. .button--alert
  • Discussing the merits of the differing approaches @williampatton pointed out that the --element--property--modifier pattern can lead to overly verbose CSSCSS Cascading Style Sheets.. @ryelle agreed but felt that the --color-1 etc. approach is also not the right answer either
  • @notlaura suggested that, as buttons are particularly complicated compared to other elements, it might help to also mock-up another element in order to compare solutions

Beyond color

Fallbacks

Next steps

  • @notlaura concluded the discussion with the observation that we need a naming convention which is close to an element selector, but which doesn’t result in a huge number of variables, many having the same value
  • @ryelle‘s use of more general custom properties e.g. --wp-admin--page--background, --wp-admin--text--color could be a better approach – she will explore this further
  • The discussion on this topic will continue!

Project updates

Color Scheming (#49999)

  • @ryelle shared this Trac ticket which could introduce custom property support & tooling
  • @peterwilsoncc asked about the possibility of setting up an npm package with admin colour sass variables, so that 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 authors could use to stay in sync. @ryelle responded that the core colours will become custom properties so the sass files will eventually be deprecated.

With that our time was up & the meeting finished. Thanks everyone!

#core-css, #summary

CSS Chat Summary: 25 February 2021

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

Housekeeping

  • @ryelle suggested she could run a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-specific 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 next week, ahead of the upcoming release – thanks @ryelle!

Project updates

CSSCSS Cascading Style Sheets. Audit (#49582)

There was a discussion about whether the time is right to share this project with the wider community:

  • @notlaura suggested adding container audits would bring the project to that point, although the tool does fulfill the objectives of the original audit ticketticket Created for both bug reports and feature development on the bug tracker.
  • @ryelle suggested also an introductory post on make/core and moving the repo into the WordPress 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/ org, preferably after the 5.7 release

There was discussion of how “dead” CSS could be deprecated & eventually removed

  • @ryelle observed that helper tools (e.g. for the adminadmin (and super admin) colours reduction project) help mitigate the risks of removing CSS
  • @williampatton suggested measuring the potential impact of particular CSS deprecations on 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 developers by performing regex searches on plugins in the directory
  • @notlaura shared a Google doc from earlier in the CSS audit process with some preliminary results using purgeCSS to find redundant CSS in core
  • @ryelle pointed out that about.css has a whole section of deprecated code that could be used to test out a CSS deprectation flow

Color Scheming (#49999)

  • @notlaura reminded us that next week we’re hoping to see some CodePens / sandboxes of approaches to naming custom properties for colours in the buttons – details here in Slack
  • @ryelle shared ticket #52623 which proposes adding a CSS custom property to represent the height of the WordPress admin bar
  • Introducing this custom property into core, along with its tooling & documentation requirements, would be a great opportunity to get the ball rolling

Visual 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. testing (#49606)

  • We had intended to remove this from the agenda but as it was mentioned @williampatton asked for some clarification on the current state of the ticket
  • Briefly, the visual regression tool in @tellthemachines’ PR is intended to be run on a person’s local machine, rather than running on CI & adding screenshots to the repo

With that @notlaura realised that we had run out of time & the meeting closed.

Thanks everyone!

#core-css, #summary

Dev Chat Summary: February 24, 2021

This post summarizes the weekly dev chat meeting from February 24, 2021 (Slack Archive). There was no APAC timed dev chat this week.

Announcements

WordPress 5.6.2 was released on Monday, February 22, 2021.

WordPress 5.7 RC1 is also available for testing!

5.7 Field GuideField guide The field guide is a type of blogpost published on Make/Core during the release candidate phase of the WordPress release cycle. The field guide generally lists all the dev notes published during the beta cycle. This guide is linked in the about page of the corresponding version of WordPress, in the release post and in the HelpHub version page. & developer notes

The WordPress 5.7 Field Guide has been published! All developer notes for the 5.7 release are included. Head on over and dive in!

All dev notesdev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. related to the 5.7 release can also be found by browsing the 5.7 and dev notes tags. Props to @audrasjb for making sure every ticketticket Created for both bug reports and feature development on the bug tracker. needing a dev notedev note Each important change in WordPress Core is documented in a developers note, (usually called dev note). Good dev notes generally include: a description of the change; the decision that led to this change a description of how developers are supposed to work with that change. Dev notes are published on Make/Core blog during the beta phase of WordPress release cycle. Publishing dev notes is particularly important when plugin/theme authors and WordPress developers need to be aware of those changes.In general, all dev notes are compiled into a Field Guide at the beginning of the release candidate phase. had a guardian.

Blogblog (versus network, site) post highlights

Component maintainer updates

  • Build/Test Tools: @sergeybiryukov shared #33043, #52643.
  • Upgrade/Install: @audrasjb reiterated the call for feedback on the Rollback Plugin Update Feature Plugin post.
  • Date/Time: No major news to share this week.
  • General: No major news to share this week.
  • 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.: No major news to share this week.
  • Permalinks: No major news to share this week.
  • Menu/Widgets: No major news to share this week.

Open floor

  • @davidbaumwald proposed adding an officially recognized needs-testing-info keyword to TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. that can be used to request better documented steps for testing a proposed 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.. The Meta-#5634 ticket has been opened to field feedback.

Next week

The next dev chat meetings will take place on Wednesday, March 3rd, 2021 at 5:00 UTC and Wednesday, March 3rd, 2021 at 20:00 UTC in the #core 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.

Props @hellofromtonya, @cbringmann, and @audrasjb for proof reading.

#dev-chat, #summaries, #summary

CSS Chat Summary: 18 February 2021

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

Housekeeping

  • @ryelle volunteered to run next week’s 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 (Thursday 25 February @ 21:00 UTC) – thanks @ryelle!

Discussion: Deprecation flow for base styles

  • Last week’s bug scrub brought up this Gutenberg issue about an SCSS variable that was removed from the wordpress/base-styles npm package
  • The issue asks if a deprecation policy & notice period exists, or should exist, for SCSS variables, since they may be used by developers in contexts other than coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • After some discussion @ryelle suggested the #core-editor meeting might be better equipped to delve into this issue
  • @notlaura offered to bring this up at the next #core-editor meeting (Wednesday 24 February @ 14:00 UTC)

Updates

Color Scheming (#49999)

CSSCSS Cascading Style Sheets. Audit (#49582)

Visual 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. testing (#49606)

Open Floor + CSS Link Share

With that the meeting drew to a close.

Thanks everyone!

#core-css, #summary