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.
It’s time to look ahead at the main areas of work for WordPress 6.1. The tune of the release will be to refine the experiences introduced in 5.9 and 6.0, weave the various flows into more coherent and fulfilling experiences for users, maintainers, and extenders, and close some gaps in functionality as we start to look towards Phase 3 of 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/ roadmap.
Introduce the ability to browse, visualize, and edit the structure of the site. Provide more clarity between global elements (templates, template parts, styles) with the aim of unifying the template editor and the post editor experiences.
We should be better prepared to fully unlock the potential of patterns as outlined in “Building with Patterns”, which was put together a bit late in the 6.0 cycle. Allow patterns to be a central piece of the creative experience, including tailoring them for custom post types, 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. types, improving the locked down experience, manage saved patterns, etc.
Continue to make progress on the global styles interface while improving the support for restrictions, privileges, and curated presets. Allow managing webfonts, implement responsive typography, and expand the toolset available to blocks with an eye towards consistency, reliability, and delight.
Themes & Gradual Adoption