The WordPress coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. development team builds WordPress! Follow this site for general updates, status reports, and the occasional code debate. There’s lots of ways to contribute:
Found a bugbugA 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.?Create a ticket in our bug tracker.
@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 coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.’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 triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. session before next week’s meeting – thanks @ryelle!
Focused on substituting existing colors throughout CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. stylesheets, the CSS Custom Properties project aims to make working with Adminadmin(and super 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.
GutenbergGutenbergThe 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/pluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party releases
BlockBlockBlock 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. inserter performance improvements
Dimension controls for Featured ImageFeatured imageA featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. Block
A proposal of an API to make blocks aware of their global styles. This APIAPIAn 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. will allow the UIUIUser interface of a block to show their true styles by default.
Navigation Block & Navigation Editor
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).
Responding to Full Site Editing (FSE) feedback, testing FSE items, and helping amplify various efforts.
Working on a coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. editor improvement post about featured image block improvements.
Friendly reminder from Dave to add the most appropriate labels to PRs in GitHubGitHubGitHub 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/, whether you’re submitting PRs or helping with triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors.. All efforts there make work easier for the release leadRelease LeadThe community member ultimately responsible for the Release..
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 blockBlockBlock 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 Navigation editor screen has been behind an “experimental” feature flag within the GutenbergGutenbergThe 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/pluginPluginA 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 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: UIUIUser interface/UXUXUser experience feature parity with the existing Navigation screen (nav-menus.php) in CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress..
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 branchbranchA 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". 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 SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. 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.
Welcome back to a new issue of Week in CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.. Let’s take a look at what changed on TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. between August 16 and August 23, 2021.
27 commits
21 contributors
58 tickets created
5 tickets reopened
43 tickets closed
Pending the appointment of the WordPress 5.9 team, a number of tickets have been fixed, waiting for the next minor and major releasemajor releaseA release, identified by the first two numbers (3.6), which is the focus of a full release cycle and feature development. WordPress uses decimaling count for major release versions, so 2.8, 2.9, 3.0, and 3.1 are sequential and comparable in scope.(s).
TicketticketCreated 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.
Check the return type of parse_url() in WP::parse_request() – #53635
Check the return type of parse_url() in download_url() – #53635
Check the return type of parse_url() in ms_cookie_constants() – #53635
Check the return type of parse_url() on PluginPluginA 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/Theme Editor screens – #53635
Correct handling of null in wp_parse_str() – #53635
Only set auto_detect_line_endings in PHPPHPThe web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher < 8.1 – #53635
Pass correct default value to http_build_query() in WP_Sitemaps_Provider::get_sitemap_url() – #53635
Silence the deprecation warning for auto_detect_line_endings – #53635
Customize
Hide native control on background position field – #53803
Editor
Replace the remaining references to wp.editor with wp.oldEditor – #53762
External Libraries
Restore the phpcs:ignore statements in PHPMailer – #53953
REST APIREST APIThe 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/.
Remove trailing slashes when preloading requests and add unit tests for it – #51636
Toolbar
Limit the icon transition style to color only – #43423
First dev notedev noteEach 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. for WordPress 5.9 is out: Gallery Block Refactor Dev Note
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.
Navigation BlockBlockBlock 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. & Navigation Editor.
Template editor.
Patterns.
Styling.
Mobile Team.
Task Coordination.
Open Floor.
If you are not able to attend the meeting, you are encouraged to share anything relevant for the discussion:
If you have anything to share for the Task Coordination section, please leave it as a comment on this post.
If you have anything to propose for the agenda or other specific items related to those listed above, please leave a comment below.
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 triagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors./scrub tickets in the component.
Got something to propose for the agenda? Please leave a comment below.
@dryanpress outlined the goal of the project: To replace hard-coded colors in WordPress CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. stylesheets with CSS Custom Properties
Work is continuing on (ryelle/wordpress-develop)[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
