@peterwilsoncc and @jeffpaul led the weekly meetings of the WordPress Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team, respectively at 05:00 UTC and 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
Blog (versus network, site) post hightlights
In the last “Week in Core” issue, @audrasjb featured 98 contributors, 13 new contributors to WordPress source code and 12 core committers.
@priethor shared details on Gutenberg 10.7 including new features like the persistent List View in the Post Editor, responsive navigation menus, many design tools for blocks, and enhancements to the top toolbar, as well as iterative performance improvements and a lot of bug 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.
@danfarrow shared CSS Cascading Style Sheets. team updates on color scheming, CSS audit, and CSS deprecation path from their last two meetings. For more information, see CSS chat summaries for May 20th and May 27th.
Blog posts that need feedback
@annezazu extended the FSE Program Testing Call #7 from June 9th to June 16th, so please check the post to learn about the feature overview, how to set up your testing environment, and the desired testing flow to help out on this.
@webcommsat has a related ask ahead of Friday’s deadline for suggestions of external channels for the promotion/info share on FSE to various audiences. Everyone is welcome to review and add suggestions in the comments.
@meaghanthompson shared a call for testing the WordPress iOS 17.5 beta, so please check the post to learn about what’s new in the release, what’s most in need of testing, how to set up the test app, and how to report issues you find.
WordPress 5.8 update
@jeffpaul shared a 5.8 schedule reminder: we are now in the Feature Freeze period where focus shifts away from enhancements and feature requests to defects and tasks.
@chaion07 and @francina led different bug scrubs this past week. There’s a final bug scrub on Monday, June 7th at 20:00 UTC to work to clear the milestone before the Beta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 1 release the next day. Here is the full bug scrubs schedule.
The next milestone will be Beta 1 on Tuesday June 8, 2021 after which point the focus will shift to testing and fixing bugs discovered during the 3 weeks beta period.
There are two “big” remaining tasks and a call for help from @youknowriad:
- The Query block 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. where the Gutenberg 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/ team had some feedback about it being too powerful (need to find better heuristics to disable editing there). Feel free to contribute to the discussion. There is also a subset of this issue.
- A proposal to change in how edited block templates are linked to themes (using theme mod instead of taxonomies). The Gutenberg team would appreciate some thoughts here from Core folks familiar with these APIs (theme mods, performance, database).
Also, these are the dev notes that need to be written for the editor.
@youknowriad shared that he consider that the Core team is ready for Beta 1, ideally, we’d have some improvements for the Query block by then but not sure if it’s necessary for beta 1.
WP 5.8 Docs focus update
@milana_cap shared that out of 165 tickets, 35 (Gutenberg excluded) are marked for some sort of documentation:
- 28 for dev notes 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, and 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.
- 5 for updating DevHub
- 12 for updating HelpHub
Gutenberg will have:
- 10 dev notes (as per the list shared by @youknowriad)
- 12 updates for dev docs
- many updates for end user docs
Everything except block editor end user updates can be found in this spreadsheet. Block editor end user updates can be found in this Drive folder.
Docs needs the most help with end user documentation. For block editor in particular. Some changes from 5.6 and 5.7 are still not published and we had a significant drop in number of contributors due to pandemic situation. Anyone interested in getting involved please ping 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.” @milana_cap (zzap on Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.).
Components check-in and status updates
Build/Test Tools, Date/Time, I18N 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., Permalinks (@sergeybiryukov): No major news this week.
Upgrade/Install (@audrasjb): @francina hosted the weekly meeting and posted the meeting notes.
Menus, Widgets (@audrasjb): no major news this week.
@poena has a request on the agenda post for anyone with knowledge on admin (and super admin) pointers:
Theme Check is a plugin 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 used to analyze themes submitted to the theme directory. I’m looking for someone who knows about admin pointers and if this issue from 2016 is still valid. Does the core team want themes with
wp_enqueue_script( ‘wp-pointer’ ); or
wp_enqueue_style( ‘wp-pointer’ ); to be blocked from the theme directory? The theme would not be able to be uploaded.
If you’re experienced with admin pointers, please respond to the comment on the agenda post or respond in the linked GitHub 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 be the repository owner. https://github.com/ issue above.
@webcommsat pointed out that WordCamp Europe is Monday to Wednesday next week!