WordPress.org

Welcome!

The WordPress coreCore Core 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 bugbug 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.? Create a ticket in the bug tracker.

Want to contribute? Get started quickly with tickets marked as good first bugs for new contributors or join a bug scrub. There’s more on the reports page, like patches needing testing, and on feature projects page.

Other questions? Here is a detailed handbook for contributors, complete with tutorials.

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 GutenbergGutenberg 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/ roadmap.

Keeping this concise so people can expand through the main Phase 2 project overview.

Template Editor →

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.

There’s a subset of work here around improving the navigation block →

Building With Patterns →

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, blockBlock 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. types, improving the locked down experience, manage saved patterns, etc.

Global Styles →

Blocks & Design Tools →

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

There are also several issues around the ability to adopt features like template parts gradually on existing themes, as well as the possibility of getting broader access to theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. editing. It’s also important to continue to look towards theme switching flows and how to best make use of the new possibilities of styles and templates.

#6-1, #gutenberg, #release-roadmap

pmmueller 12:22 pm on June 11, 2022

Simple question: What should we call things?

You now refer to the Site Editor aka the Editor as the Template Editor, and I like it.

But.

1.
There is a blockBlock 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. editor for the content area on posts and pages that many people refer to as GutenbergGutenberg 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/ editor because we didn’t have a proper name for it, and that is called WordPress editor over on WP dot com and that Carolina Nymark over on (fullsitediting.com) simply calls Editor .

2.
There is a Template Editor that you can start from the block editor for the content area on post and pages that is called WordPress editor over on WP dot com to create templates that sometimes is refered as Editor, and that Template Editor is of course a block editor.

3.
There is a Site Editor in a menu called Editor to edit and create templates which also is a block editor but not for content, and now that editor is called Template Editor, too?

The only thing I haven’t seen recently is Theme Editor. That’s now called Theme File Editor and has moved to a different menu.

Maybe proper names for things would help clear the confusion?
justlevine 3:03 pm on June 15, 2022

Is there intentionally nothing on the roadmap that isn’t directly related to GutenbergGutenberg 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/?

Surely by now you’ve all seen the dev community’s retrospectives / reviews of 6.0 (and if we’re being honest, 5.9 and 5.8) about how the rest of WP languishes while the only major improvements come to a module that still isn’t in a place that many of us can adopt.
- Antonio D. 8:00 am on August 26, 2022
  
  I agree
Juliette Reinders Folmer 3:35 am on June 23, 2022

Interesting…. no mention of PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher 8.2 or even continued efforts for PHP 8.x readiness…
- Josepha 4:09 pm on June 23, 2022
  
  That’s on the short list I’ve gathered from folks in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. so far. We’ll publish a companion post to this one and link them both on the project page for the release.
  - webcommsat AbhaNonStopNewsUK 8:45 am on August 31, 2022
    
    @chanthaboune was there a companion post to this one please? Could not see it on the development cycle page for this release, so it may not be out yet. Looking for dev chat and for the release documentation team. Thanks.
    - Josepha 10:55 pm on September 2, 2022
      
      I was sure that got published, but I can’t put my hands on it. I’ve shared the list that I originally collected below. @priethor, can you share the official link when you have a chance?
      
      Default theme
      
      Rollback and Plugin Dependencies
      
      https://core.trac.wordpress.org/ticket/55942
      
      Upgrade/Install updates
      
      https://core.trac.wordpress.org/ticket/14179
      
      Various performance initiatives such as improving loading of block.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. files
      
      Site Health > messaging to alert site admins of out-of-date PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher versions in an effort to help users migrate off of these old versions i.e. upgrade).
      
      PHP 8.2 compatibility (and ongoing work for PHP 8.x compatibility)
      
      Fonts things (default themes esp).
      
      devcontainer/Codespace support set up
pmmueller 9:17 am on July 29, 2022

Please don’t forget to put the links on the project page for 6.1 😉