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 the bug tracker.
Twenty Twenty-Five embodies ultimate flexibility and adaptability, showcasing the many ways WordPress enables people to tell their stories with many patterns and styles to choose from. The glimpses of natural beauty and ancestry woven into the theme evoke ideas of impermanence, the passage of time, and continuous evolution.
The demo content imagery, all from the Public Domain, carries a poetic, universal, and ubiquitous tone that complements the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. concept. There was an opportunity to visually lean into a positive tone to bring softness, lightness, and inspiration through its aesthetic.
Patterns
Structurally, Twenty Twenty-Five offers a robust set of patterns, promoting interoperability and enabling users to compose intentional pages quickly. A broad range of patterns was designed for categories such as services, about, landing pages, products, calls to actions, events, and others.
Styles
Given the theme’s global use, high-quality and comprehensive fonts that support multiple languages have been considered from the first conceptual steps of the design. Furthermore, we’re refining a set of diverse color palettes to be bundled within the theme as style variations.
Templates
Twenty Twenty-Five also features a versatile set of blogblog(versus network, site)templates: text-centric blogs with sidebars, photo blogs that highlight featured images, and more complex blogs with diverse content. Twenty Twenty-Five will be fully compatible with the Site Editor and will use many of the new design tools like the Grid 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. and Pattern/Section Styles.
Personal Blog (Default)
In keeping with the idea of simplicity, the personal blog tendency is to lean on a default template that just works, whether you want to write a post with a title and 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. or not, and showing all the post’s content out-of-the-box, instead of just excerpts.
Photo Blog (Alternative)
The alternative “photo blog” templates tailored primarily for photography or portfolios lean on an image-heavy approach, with interesting layouts that can be used for a variety of purposes.
Complex Blog (Alternative)
Lastly, the set of complex blog alternative templates would be more suitable for websites with greater complexity in content. Some of these templates, with more variety in type scales and more opinionated designs can also appeal to different audiences.
Development
As part of the 6.7 release, Carolina Nymark (@poena) and Juanfra Aldasoro (@juanfra) are leading development while Beatriz Fialho (@beafialho) is leading design. If you’re interested in contributing, make sure you’re following this blog; we look forward to your involvement and support throughout the process.
The Figma file is the design source of truth. Comments in the main file are open, and anyone should feel free to duplicate the Figma to their drafts and remix. Both of these actions are free, whereas every edit access is paid and therefore reserved.
Theme development will happen on the Twenty Twenty-Five GitHub repository. You can contribute by submitting and reviewing pull requests or opening new issues and, as usual, once the theme is stable, it will be merged into Core and the GitHubGitHubGitHub 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/ repository will be archived.
Starting on Wednesday August 21st at 3:00 PM UTC , there will be weekly Slack meetings in #core-themes to coordinate development of the theme. Agenda notes will be posted before meetings and summaries posted after the meeting.
Learn more
For information about previous default themes, read the following posts:
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/ 19.0 was released earlier today 🎉 You can read the release post here.
The WordPress 6.7 release squad was announced just before this meeting! You can find the list of squad members here.
Forthcoming Releases
Next 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.: 6.7
We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBetaA 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 is scheduled for Tuesday, October 1.
Next minor releaseMinor ReleaseA 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.: 6.6.2
The next maintenance release will be 6.6.2. @hellofromtonya shared in the meeting that the release date may be delayed by a few weeks to early September to address all of the CSSCSSCascading Style Sheets. specificity issues being tracked in this Gutenberg issue. Once a date is confirmed, Tonya will post an update on the make/coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. site.
Next Gutenberg release: 19.1
The next Gutenberg release will be 19.1, scheduled for August 28.
Discussion
Update on changing the Dev Chat time for 6.7 – Now that the release squad for 6.7 has been announced, @joemcgill is going to give them an opportunity for feedback on the original post, and then confirm an updated Dev Chat time starting next week. Currently, Wednesday, Aug. 21 at 1:00 UTC is looking likely.
@karmatosed reminded that we should make sure to post agendas maybe day before and ask those not attending due to time zone to get their updates added. It will need to be a habit for some.
@clorith suggested some ideas for automating the agendas to make it easier to publish at a consistent time each week.
Open Floor
@dmsnell is asking for additional feedback on #61864. To summarize:
[this] fixes old commits and errors caused by our subversion-to-git process, as noted in the TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.ticketticketCreated for both bug reports and feature development on the bug tracker.. For example, a number of contributors are stuck with corrupted names because the conversion script double-UTF-8 encodes text from the WordPress.org profiles.
it’s a one-off thing I proposed, but in the future allows each contributor to have control over their own representation. we don’t have to maintain it because we simply haven’t been maintaining this stuff at all. it doesn’t particularly go out of date, but a committercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. may change their name and not update the file. it’s their option to do so or not
if there’s no problem there’s no need to be added to the list. for example, I have no commits from the time a GUID was added as the email domain, and I haven’t changed my name. so I’m not in the list. only people who have commits from multiple identities and people whose names have been corrupted by the conversion are in the list right now.
The original HEIC image can be downloaded via a link on the attachment page.
Conversion is only done if the server has a version of Imagick that supports HEIC. You can see whether a server supports HEIC in Tools → Site Health → Info → Media Handling → ImageMagick supported file formats.
If conversion is not possible, a warning is displayed to the user encouraging them to manually convert the image to JPEG. This was the default behaviour prior to WordPress 6.7.
Automatic conversion of HEIC images to JPEG can be disabled using the image_editor_output_formatfilterFilterFilters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output..
In [58899]a .mailmap file was added to WordPress which instruct git and git-aware tooling to alias specific emails and names to a new identity. With this change it’s possible to combine multiple git identities into a single one as well as fix any identities which may be broken in history.
For example, there was a time commits were brought over from Subversion and the emails associated in the git commit followed the form <username@602fd350-edb4-49c9-b593-d223f7449a82>. For each of these users, there might be other commits referencing <username@git.wordpress.org>. Tools counting commits, history logs, annotations (blames), and others will make it seem as though the commits came from different people.
Further, committers change their names from time to time. Since git history is immutable there’s no easy way to update old names without rewriting the entire project. The .mailmap file provides the necessary mechanism to do this without interrupting that history.
Finally, committercommitterA developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. names may be corrupted if they contain non-US-ASCII characters. This corruption can be resolved by adding an entry in the .mailmap file correcting the name. This was the motivating case for introducing this file.
Most git tools provide a way to see the underlying raw data, so to see the actual recorded names it’s usually possible to pass --no-use-mailmap.
Would you like to review your own contributions?
If you run git shortlog -ens from the wordpress-develop repo then it will show a listing of commits per committer. If you see any problem with your name, duplicate name/email pairs, or would prefer to update your name, you can add new entries in the .mailmap to make the appropriate adjustments.
# Review variations of my name before adding the .mailmap entry
git shortlog -ens | grep -iE 'dmsnell|dennis'
98 Dennis Snell <dmsnell@git.wordpress.org>
1 dmsnell <dmsnell@602fd350-edb4-49c9-b593-d223f7449a82>
echo "Dennis Snell <dmsnell@git.wordpres.org> dmsnell <dmsnell@602fd350-edb4-49c9-b593-d223f7449a82>" >> .mailmap
git shortlog -ens | grep -iE 'dmsnell|dennis'
99 Dennis Snell <dmsnell@git.wordpress.org>
Core TriagetriageThe act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. Leads: Ahmed Kabir Chaion, Stoyan Georgiev
This squad experiments with merging the Marcomms lead with the release coordinator, as suggested in the previous proposal and agreed upon with this release’s coordinator, David. We’re open to feedback and can revert this change during the process if needed.
While announcing the whole release squad is ideal, at the end of the day, it involves a lot of async coordination that delays the announcement. Feedback received indicates this is particularly constraining for the Default Theme Role, for which the leads had to start the work before this announcement to avoid getting caught by the release deadlines. For future releases, I suggest:
Providing release squad updates every week.
Making a call for volunteers for the default theme earlier, independent of the squad of the release that will contain it.
Big thanks to everybody who volunteered for the release squad!
“What’s new in 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/…” posts (labeled with the #gutenberg-new tag) are posted following every Gutenberg release on a biweekly basis, showcasing new features included in each release. As a reminder, here’s an overview of different ways to keep up with Gutenberg and the Editor.
In the Gutenberg 19.0 release, two important features have been added under experimental flags to allow folks to opt in to test and give feedback as they want. These features can be enabled by going to Gutenberg > Experiments. The first feature lets you connect blocks to custom fields, which many have been eager to see. The second feature lets you quick edit within the new Site Editor > Page’s interface, built using Data Views. Feedback is welcome and needed for both.
Outside of these experimental features, this release also includes severable notable enhancements, including a more intuitive user interface to configure views (pages, templates, patterns, etc) and the option to choose whether filters are shown or hidden within them. Finally, the option to manually enter a zoomed out view was added alongside the device preview options and multiple writing flow enhancements were completed.
UIUIUser interface to connect blocks and custom fields
Gutenberg 19.0 comes with the first UI prototype to connect blocks and custom fields. It has been merged under an experimental flag in the 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..
To check it out enable the “UI to create 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. bindings” experiment under “Gutenberg -> Experiments”.
Quick edit is now available on the new Pages list
The first version of Quick Edit for Data Views has landed in Gutenberg 19.0 as an experiment. It allows users to edit some fields without leaving the overall Pages interface — it supports bulk editing as well.
Show or hide filters in Data Views
Gutenberg 19.0 includes functionality to hide/show the filters in the user interface. This simplifies the Data Views UI, as complex filters (including default ones for some views) will no longer occupy UI space. At the same time, feature parity and ease of use are maintained, as filters can still be added by clicking the filtering button when needed.
@westonruter shared a pulse check on Monday noting that the milestones are on average 55% complete. During the meeting he mentioned that the Modern Image Formats issues still needs to most eyes.
@flixos90: “It seems there have been quite a few bugs piling up from the picture element support, but I haven’t been able to look closely yet. Is there an overarching theme that these fall into? E.g. ecosystem compatibility, or edge-cases, or compatibility with other image features of the 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.?”
@adamsilverstein: “…the picture element support missed a few things we could have caught before launching. we also did already fix a few compatibility issues that would have been hard to catch”
This led to a longer conversation about the goal of experimenting with picture support from a performance point of view.
@flixos90: “My concern with this is mostly about how much of a priority it should be compared to everything else we have on our plate as a team. Of course there’s value in exploring picture element in CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress., but for instance if it doesn’t help much with AVIF, I question that we prioritize it this much. It’s by no means a simple feature to implement and land, and the bugs require a lot of attention that is taken away from the other things we’re working on (e.g. better responsive image sizes handling) which IMO have a greater performance benefit”
Active Priority Projects
Optimization Detective: Server-applied optimizations informed by client-side detection (overview issue)
@westonruter confirmed that this is mostly complete. He’ll create follow-up issues and close this one.
Improving the calculation of image sizes attributes (overview issue)
@mukesh27 did not have any updates this week, will share more next week.
@mukesh27 opened #61847 to propose adding auto-sizes to WP Core
“I’m thinking about making a new core ticketticketCreated for both bug reports and feature development on the bug tracker. to introduce a Sustainabiliuty classification to the Site Health checks, as some of the performance ones, when there’s no real performance problem as is, but the recommendations would be good for sustainability., Just wanted to voice it with y’all first before I started throginw out ideas to change your classifications”
@flixos90: “Definitely some overlap between the two, but I like the idea. Sustainability is a different motivator than performance and some checks may apply more to one than the other. Either way, it’s a good way to promote certain checks and of course sustainability”
Next step is that @clorith plans to open a ticket with recommendations for which checks to possibly reclassify to get input.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.
Announcements
There are no announcements from the last week.
Forthcoming releases
Next 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.: 6.7
We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBetaA 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 is scheduled for Tuesday, October 1 (7 weeks away!)
Next maintenance release: 6.6.2
The next maintenance release will be 6.6.2. RC1 is scheduled for August 19, and the full release is planned for August 26. Here is the Trac milestone for the release.
Next 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/ release: 19.0
Design Share #61 (Jul 15-Aug 9) — recent recap post of design efforts and a great way to see what’s top of mine for design contributors as well as how to get involved.
Comments pagination 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.: efforts were kicked off to Deprecate Comments Pagination block
Components: design efforts have started to update TimePicker component design. Great spot for accessibilityAccessibilityAccessibility (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) to get involved.
Media: very early PR for [WIP] Add experiment for client-side media processing which “lays the foundation for client-side media processing in Gutenberg—meaning we can do things like thumbnail generation, cropping, compression, and format conversion (transcoding) all in the browser.”
Performance: PR Inserter: Try improving pattern loading to both improve performance and the experience of patterns in the Inserter to lessen any jumpiness in the UIUIUser interface for users.
Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.
Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting for discussion or if you will be async.
Next 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.: 6.7
We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBetaA 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 is scheduled for Tuesday, October 1.
Next minor releaseMinor ReleaseA 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.: 6.6.2
The next maintenance release will be 6.6.2 and will likely be released at the end of the month, likely August 26 with RC1 the week before.
Next 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/ release: 19.0
Gutenberg 19.0 is scheduled for August 14. RC1 was released on August 7.
#53817 was raised in the agenda comments. We discussed that this issue should be opened in the Gutenberg repo instead of TracTracAn open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress., which @hellofromtonya offered to handle.
Next, we discussed #51525. @mathieulamiotwpmedia described where the ticketticketCreated for both bug reports and feature development on the bug tracker. was up to:
We are interested in this possible enhancementenhancementEnhancements are simple improvements to WordPress, such as the addition of a hook, a new feature, or an improvement to an existing feature. for a while and we built a library that we currently use based on the ticket’s discussions. Having this directly in CoreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. would open up a few possibilities to make apply_filters typing more resilient, but it was never really clear in the ticket discussion if such approach could make it to the Core at some point.
So, we suggest a patchpatchA 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. based on the library we built, and it would be great to get feedbacks from Core maintainers. First, to know whether or not it’s worth pursuing the effort on this, from a WP Core perspective. And if yes, what could be next steps
The ticket itself is loaded with information and context, and the patch itself might not be easy to assess right here right now ; but I thought we could bring this up here to maybe follow-up on it asynchronously. That’s it, I guess!
We discussed whether this should be included in Core, how it could be used, or if it is intended as a shared 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. that plugins and themes would use.
The live meeting will focus on the discussion for upcoming releases, and have an open floor section.
Additional items will be referred to in the various curated agenda sections, as below. If you have ticketticketCreated for both bug reports and feature development on the bug tracker. requests for help, please do continue to post details in the comments section at the end of this agenda.
Announcements
There are no announcements from the last week.
Forthcoming releases
Next 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.: 6.7
We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBetaA 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 is scheduled for Tuesday, October 1.
Next maintenance release: 6.6.2
The next maintenance release will be 6.6.2. No release date is currently set.
Next 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/ release: 19.0
You can keep up to date with the major Editor features that are currently in progress by viewing these Iteration issues.
Open floor
Any topic can be raised for discussion in the comments, as well as requests for assistance on tickets. Tickets in the milestone for the next major or maintenance release will be prioritized.
Please include details of tickets / PRs and the links in the comments, and if you intend to be available during the meeting for discussion or if you will be async.
You must be logged in to post a comment.