The WordPress core development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
@ryelle noted that all custom properties should eventually be moved into custom-properties.css
@wazeter asked about fallback values which @ryelle responded to: hex fallback rules, which precede rules assigning rgba values for browsers that don’t understand rgba, can now be removed since core’s browser support has been updated – UPDATE: I’ve added a note about this in the shared doc
@notlaura added a final note thanking all contributions, especially newcomers
CSS Link Share / Open Floor
@notlaura raised the topic of meeting structure, in particular keeping the structured work sessions for times when attendance is low
@wazeter supported the meeting format, noting that he sometimes was unsure what to do in the structured work session
@notlaura suggested creating some general guidelines on how to run Core CSS meetings – UPDATE: Now underway here!
@ryelle volunteered to run the CSS triage session before next week’s meeting – thanks @ryelle!
Focused on substituting existing colors throughout Core stylesheets, the CSS Custom Properties project aims to make working with Admin Themes & Admin Color Schemes easier and more reliable both in Core and Plugins.
The #core-css team is looking for contributors interested in adopting a stylesheet (a process outlined here). No prior contributing experience is required — we’re happy to assist anyone who would like to participate! This meeting we will continue with work and collaboration, time permitting.
The team have been focused on reforming the project around the goal of removing the “experimental” status of the feature within the Gutenberg Plugin (only).
Friendly reminder from Dave to add the most appropriate labels to PRs in GitHub, whether you’re submitting PRs or helping with triage. All efforts there make work easier for the release lead.
It would be very helpful for us who run the Core Editor Meetings to have tracking issues that are updated once a week, so we can share the project updates during the meeting. As it will also give a nice overview and it would make it easier for anyone to follow along to see the progress over time.
The block-based Navigation editor screen has been behind an “experimental” feature flag within the Gutenbergplugin for some time. The purpose of the call was to outline the work required in order to remove the “experimental” status from the screen in order that the editor is active by default in the Gutenberg plugin.
The team working on the feature feel this is valuable in order to increase the visibility of the feature and therefore improve the quantity of feedback we receive.
Meeting Recording
If you’d like to watch the full recording of the session you can do so below:
Key points agreed
It was agreed that the prerequisite for removing “experimental” was: UI/UX feature parity with the existing Navigation screen (nav-menus.php) in Core.
We also acknowledged that:
We wouldn’t commit to feature parity of developer focused APIs at this stage.
Removing “experimental” in the Gutenberg plugin, would not automatically make the feature ready for merging into Core (that won’t happen until WordPress 5.9 at the earliest).
What was discussed?
The format of the hangout was an open discussion comparing and contrasting the classic menu screen with the experimental block-based navigation screen.
To this end attendees were asked to test drive both screens and note down their findings prior to the call.
The meeting facilitators also prepared a list of items as discussion points which were worked through during the call.
Each item was demonstrated, discussed and then assigned a loose priority of High/Medium/Low based on how critical the group felt the issue was to achieving feature parity.
Outcomes
The key outcomes of the call were:
A clearer understanding of the current project roadmap and the next steps required.
Contributors working on the Nav Editor will now look to reorganise and reprioritse the tracking issue around the problems identified during the call.
All items will be added to the tracking issue (with the possible exception of bugs).
The High priority section of the tracking issue will be reformed and refocused around the goal of “removing the experimental status from the Navigation Editor”. Only tasks directly related to this goal will be considered for inclusion in the “High” priority section.
Tasks identified during the call that were marked as Medium or High till be added to the aforementioned High priority section of the tracking issue.
Contributors will focus on tackling High priority tasks in order to realise the goal of removing the “experimental” status.
All contributors are encouraged to become involved in prioritisation. Everyone is welcome and we’d very much value your feedback. If you feel a priority is wrong or missing then please let your fellow contributors know.
Thanks to everyone who attended the hangout and we look forward to moving the Navigation Editor forward together.
The following schedule is being proposed for 5.8.1:
RC: Wednesday, September 1, 2021
Final release: Wednesday, September 8, 2021.
As of the publish date of this post, 24 tickets have already been fixed and backported to the 5.8 branch to be included in 5.8.1. 38 additional open tickets are currently in the 5.8.1 milestone for consideration. Please head over and check out that list to contribute to the release.
Release coordination
During the 5.8 release, a new, #5-8-release-leads channel was created in Slack for the release squad to have all 5.8 related conversations. Because the 5.8.x releases are part of 5.8 by extension, all coordination and conversation related to the 5.8.x releases will also be held here before the channel is archived when WordPress 5.9 is released.
Do you have something to propose for the agenda, or a specific item relevant to the usual agenda items above?
Please leave a comment, and say whether or not you’ll be in the chat, so the group can either give you the floor or bring up your topic for you accordingly.
This meeting happens in the #core channel. To join the meeting, you’ll need an account on the Making WordPress Slack.
I’d like to make another plea for adding the most appropriate labels to PRs in Github. It’s a small thing but it really helps the release lead when they are pruning the changelog.
Anything folks can do to help add labels when triaging PRs or remembering to use labels when they can would be much appreciated. Thank you!
The aim of the chat is to check the status of the rollback for failed plugin/theme updates after last Friday’s testing session and triage/scrub tickets in the component.
Got something to propose for the agenda? Please leave a comment below.
Work is continuing on (ryelle/wordpress-develop)[http://wayback.fauppsala.se:80/wayback/20210829144930/https://github.com/ryelle/wordpress-develop/pull/2]
Last week’s chat summary here covers our discussion around box-shadow, why we can’t use HSL and that we’ll be continuing discussion on this PR
This project is targeted for experimental release in WordPress 5.9 and then a stable release in 6.0. To make WordPress 5.9, the project probably needs to be merge-ready by end of August
Update for the Navigation editor screen is available.
We also have a summary of the recent hallway hangout and decisions that were made about next steps for the Nav Editor.
I’d like to make another plea for adding the most appropriate labels to PRs in Github. It’s a small thing but it really helps the release lead when they are pruning the changelog.
Anything folks can do to help add labels when triaging PRs or remembering to use labels when they can would be much appreciated. Thank you!