loading . . . Planning for 7.0 With 6.9 out in the world, our collective attention has already turned to 7.0. Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org., together with Matt and Mary, had a call to discuss ideas and projects. There was shared excitement about this release, even if it’s _just_ another number. This post acts as a gathering point for contributors to share what they are starting to work on and to find known areas they can contribute to. There will be another more tactical follow up with release schedule and responsibilities, this one is about the initial scope.
**How to interact with this post**
Please do not use this as a spot to request folks to work on features. GitHubGitHub 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/ and TracTrac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress. are the best places to share feedback, talk about impact, and advocate for issues.
Please use this post to share what you are working on, including areas you’d like to help with that may be listed here, as well as areas that you are working on that are not. Items with TBD indicate areas where contributors are needed so please comment below if you’re keen to work on those pieces.
If you were planning to work in an area listed below and don’t see your name, please be sure to comment as well and it’ll be updated. It’s intentional that this post is meant to be a place to shore up who is working on what out in the open at this early stage.
Also note this is neither comprehensive nor yet a commitment that all of these things will be part of 7.0, since many are in early stages and may not make this release. Items marked with ✅ mean the work is already merged in 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/ or trunktrunk A directory in Subversion containing the latest development code in preparation for the next major release cycle. If you are running "trunk", then you are on the latest revision..
## Collaboration
The project is getting deeper into Phase 3: Collaboration. Notes was a highlight feature in WP6.9 and there’s several improvements already planned to make it even more powerful and resilient.
**Real time collaboration**
* Link: GitHub issue
* Key considerations:
* There’s been a lot of progress in defining the UIUI User interface and the diffing mechanics for reconciling changes. It’s in very good shape and needs to be reviewed and tested diligently, especially around compatibility with third-party blocks and plugins.
* This feature has a stronger dependency on server support and infrastructure than usual WordPress features, so there needs to be a definition of what’s the baseline experience shipping in WordPress (for example, peer-to-peer with 1 or 2 connections) and how it can be augmented, either by WP.org, hosting providers, or plugins.
* Contributors: @acicovic, @aduth, @alecgeatches, @czarate, @ingeniumed, @jsnajdr, @maxschmelingkc, @paulkevan, @shekharnwagh, @youknowriad
**Notes i2**
* Link: GitHub issue
* Key considerations:
* Support partial selection inside 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. rich text fields.
* A “suggestions” mode and interface that allows Notes to refer to specific content within a block and apply the suggestions.
* Support for multi-block notes.
* Add rich text support in the comments.
* Develop a dashboard widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. for recent notes.
* More notification options (responses, follow a note, mentions).
* Contributors: @adamsilverstein, @jeffpaul, @mamaduka
* * *
## Adminadmin (and super admin)
**Improving screens across wp-admin**
* Link: TBD
* Key considerations:
* Explore CSS improvements that can modernize the look and feel. For example, consider making the “modern” admin color scheme the default.
* Admin bar and editor “site hub” improvements. Make the W menu item filterable. Possibly start work as an experiment in Gutenberg.
* Consider a “This time last year” widget for bloggers.
* Bring grid layout customization to dashboard experience or other screens. (Possible widgets at the top of comments, etc).
* Contributors: TBD, @fabiankaegy, @karmatosed, @mcsf
**DataViews and DataForms iterations**
* Link: 7.0 iteration issue
* Key considerations:
* DataForms/QuickEdit/Document inspector design iterations.
* Hierarchical post visualization.
* Make DataViews screens extensibleExtensible This is the ability to add additional functionality to the code. Plugins extend the WordPress core software. in the site editor (templates, pages, etc).
* Contributors: @oandregal
**Design System**
* Link: GitHub issue
* Key considerations:
* Components are already being worked on in wordpress/ui.
* **✅** Theming system with design tokens using wordpress/theme.
* Start replacing key parts of the editor UI with improved components (tabs, flyout menus).
* Contributors: @0mirka00, @aduth, @jsnajdr, @mciampini, @wildworks
**Font library admin section**
* Link: Github issue
* Key considerations:
* **✅** Support for block themes.
* Support for hybrid/classic themes.
* Contributors: @youknowriad
**Revisions Revisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. **
* Link: GitHub issue
* Key tasks:
* Rethink the revisions interface to be more modern, intuitive, and work with blocks.
* Show visual diffs.
* Bonus: potentially tie in with collaborative editing, suggestions, and undo management.
* Contributors: @adamsilverstein
**Customizable Keyboard Shortcuts**
* Link: Github issue
* Key considerations:
* Build with design system components.
* Contributors: TBD
* * *
## APIs
**Abilities & Workflows APIAPI An 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.**
* Link: Github issue
* Key considerations:
* Hybrid abilities.
* **✅** The client side package.
* Driven by Fields API definitions.
* Querying and filtering functionality for the abilities.
* Implement some of the abilities outlined in WordPress Core Abilities.
* Command palette and UI:
* Differentiation between commands.
* Ability to support two stages of a command.
* Contributors: @jorgefilipecosta @gziolo @senadir @youknowriad
**Upgrade to ReactReact React is a JavaScript library that makes it easy to reason about, construct, and maintain stateless and stateful user interfaces. https://reactjs.org/. 19**
* Link: Github issue
* Key considerations:
* There’s a path for the block editor in the mobile apps that should remove this dependency blockerblocker A bug which is so severe that it blocks a release..
* Ecosystem impact.
* Contributors: @aduth @jsnajdr @mamaduka @ralucastn @tyxla
**Block API: Add validation levels**
* Links: Github issue with initial PR****
* Key considerations:
* The scope of this issue is to drastically reduce the amount of times a user sees a “this block is broken” message.
* Impact on block API.
* Contributors: @matveb @mcsf @youknowriad
**Enforced iframed editor**
* Link: GitHub issue.
* Backwards compatibility, extended testing.
* **✅** MigrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. guide.
* Contributors: @ellatrix, @wildworks
**WP client AI API**
* Link: GitHub project
* Key considerations:
* An AI client and API for WordPress to communicate with any generative AI models of various capabilitiescapability A **capability** is permission to perform one or more types of task. Checking if a user has a capability is performed by the `current_user_can` function. Each user of a WordPress site might have some permissions but not others, depending on their role. For example, users who have the Author role usually have permission to edit their own posts (the “edit_posts” capability), but not permission to edit other users’ posts (the “edit_others_posts” capability). using a uniform API.
* Integration with Abilities API.
* Strictly no providers included in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
* Decide nomenclature.
* Ideally, the minimum PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 7.4 or higher version has to be bumped from PHP 7.2.
* Contributors: @flixos90 @jason_the_adams
**Creating blocks and patterns on the server**
* Link: GitHub issue
* Key considerations:
* Most of the tools for a pretty straightforward PHP-only representation of blocks and patterns, including bindings, are ready.
* Declarative block attributes and form components.
* Pattern creation and syntax that allows easy construction of blocks and bindings.
* Contributors: @priethor, TBD
**wordpress/build and routing (site editor)**
* Link: GitHub issue; Scripts issue
* Key considerations.
* Add extensibility to site editor routing.
* Dependency on standalone font library.
* Refactor the site editor to allow pluginPlugin 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 authors to add their pages there.
* **✅** Opinionated build tool for plugins.
* Update Gutenberg – Core backportbackport A port is when code from one branch (or trunk) is merged into another branch or trunk. Some changes in WordPress point releases are the result of backporting code from trunk to the release branch. flow.
* Contributors: @youknowriad
**Shortblocks**
* Links: Bits as dynamic tokens; Bits: Introduce the ability to store and render bits, Rich text: try BITS with block binding API, Introduce parser for dynamic token system.
* Key considerations:
* Decide name for the feature (shortblocks, inline blocks, bits).
* Determine best syntax.
* Connect with bindings UI.
* Support for rich text autocomplete.
* Contributors: @dmsnell, @ellatrix, @jonsurrell
**Block bindings iterations**
* Link: GitHub issue
* Key considerations:
* Open up “Pattern Overrides” and therefore intern block bindings to custom dynamic blocks.
* Filter available source items for a given attribute by format.
* Align with Fields API as a requirement.
* Contributors: @bernhard-reiter
* * *
## Navigation Block
A series of improvements were identified to simplify the navigation workflow and make the experience of managing menus more intuitive and straightforward.
**Simpler navigation editing**
* Link: GitHub issue
* Key considerations:
* Better insertion.
* Pattern editing and ContentOnly interactivity.
* Better presentation of “bound” page items.
* Contributors: @get_dave, @jeryj
**Ability to customise “mobile” overlay**
* Link: GitHub issue
* Key considerations:
* Implemented as a template part.
* Ability to customize when the overlay appears (breakpoint settings) just for navigation overlay.
* Contributors: @get_dave, @jeryj
* * *
## Customization
Over the past couple years we’ve been iterating on a series of related systems with the hope of arriving at a more streamlined editing experience of composite blocks and design patterns. We have some solid directions sketched out that are looking promising.
**Explore more intuitive page navigation in the site editor**
* Link: TBD
* Key considerations:
* Modify the title bar to display a pages dropdown instead of empty command palette. List the pages used in the primary menu with a link to “browse all pages”. Exploration.
* Add next/previous page links in zoomed-out view, similar to a carousel. See a preview in a zoomed out state with arrows next to preview or title bar. Exploration.
* Contributors: @ellatrix
**Pattern Editing (aka ContentOnly)**
* Link: GitHub issue
* Key considerations:
* Ensure proper discoverability to enter/exit.
* Ensure it works well with synced patterns.
* Contributors: @aaronrobertshaw, @andrewserong, @isabel_brison, @ramonopoly @talldanwp.
**Improve template management**
* Link: GitHub PR
* Key considerations:
* Direction and UXUX User experience is still TBD and needs more exploration.
* Retain access to template parts across theme switches.
* Contributors: @ellatrix @scruffian.
**Responsive editing mode**
* Link: GitHub issue
* Key considerations:
* Toggle to engage responsive editing mode.
* Block visibility i2: add ability to hide blocks based on screen size.
* Allow style changes to be saved and retrieved for different breakpoints.
* Allow customization of hardcoded breakpoints.
* Contributors: @matveb @ramonopoly
**Block supports and design tools:**
* Link: GitHub issue
* Key considerations:
* Add text line indent support. GitHub PR.
* Add gradient support to text color options.
* Add height block support to dimension .
* Styles support for text shadow. GitHub PR.
* Support for text alignment with justify support.
* Allow Video backgrounds to be ‘Fixed’.
* Balanced line wrap.
* Text columns. GitHub issue; GitHub issue.
* Support aspect ratio on wide and full images.
* Contributors: TBD, @aaronrobertshaw @matveb @youknowriad @wildworks
* * *
## Blocks
Keeping the momentum on adding new blocks and new block tools to expand the palette and expressiveness offered to theme builders and users. There’s also some refinements to some fundamental aspects of blocks to make them more resilient and more consistent.
**Group block attributes**
* Link: GitHub Issue
* Key considerations:
* Adding groups to InspectorControls (like BlockControls).
* Add support for list representation to block API based on nav block work.
* Implement content representation for media and rich text attributes. (Connected with contentOnly, bindings, and partially synced patterns work.)
* Contributors: TBD
**✅ Cover block: video embeds**
* Link: GitHub Issue; GitHub PR
* Contributors: @matveb
**Modernize Code editor + Code block**
* Link: GitHub link
* Contributors: @jonsurrell, @westonruter
**Lazy load the Classic block**
* Link: TBD
* Key considerations:
* The main aim is performance—avoid loading TinyMCE by default if not needed.
* If possible, address moving the freeform block to a separate package in this work too.
* Contributors: @tyxla
**Leverage iAPI for instant search block & submit comments without full page refresh**
* Links: Instant Search, submit comments without requiring a full-page refresh.
* Contributors: TBD
**Writing flow + drag and drop improvements**
* Link: GitHub issue
* Key considerations:
* Get to a place where the drag handle from the toolbar can be entirely removed due to improved drag and drop functionality.
* Making multi selection work on touch devices.
* Improvements to inline insertion and inline images.
* Contributors: @ellatrix
**✅ Tabs block**
* Link: GitHub issue
* Contributors: @mikachan
**Release the Table of Contents block**
* Link: GitHub issue
* Contributors: TBD
**Playlist block**
* Link: GitHub issue
* Contributors: @scruffian
**Slider block**
* Link: GitHub issue, GitHub issue, GitHub issue
* Contributors: @lstraczynski, @karolmanijak
**Dialog block**
* Link: GitHub issue
* Contributors: TBD
**✅ Breadcrumb block**
* Link: GitHub Issue
* Team: @ntsekouras
**Add more dynamic URLs via block bindings to Buttons block and Image block**
* Link: GitHub issue, API shape
* Team: TBD
**Icon block**
* Link: GitHub issue
* Key considerations:
* Ship with a default set made out of some wordpress/icons.
* Allow extenders to register their own sets.
* Contributors: @mcsf @welcher
**Gallery block: add lightbox support with the ability to switch between images**
* Link: GitHub issue, GitHub PR
* Contributor: @wildworks
**Introduce heading levels as Heading block variations**
* Link: Github issue; https://github.com/WordPress/gutenberg/issues/42181
* Key considerations:
* Show up in search and slash inserter.
* Easy toggling in sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. inspector and transforms.
* Contributor: @matveb
**Aim to stabilize grid block**
* Link: GitHub issue
* Contributor: @isabel_brison
* * *
## Media
**Client side media work**
* Link: GitHub issue
* Contributors: @adamsilverstein, @ramonopoly
**Media editor**
* Link: Iteration issue
* Contributors: @aaronrobertshaw, @andrewserong, @isabel_brison, @ramonopoly, @talldanwp
* * *
Designers looking across all these projects: @fcoveram, @joen, @jameskoster, @mattmiklic.
#7-0, #phase-3
### Share this:
* Click to share on Threads (Opens in new window) Threads
* Click to share on Mastodon (Opens in new window) Mastodon
* Click to share on Bluesky (Opens in new window) Bluesky
* Click to share on X (Opens in new window) X
* Click to share on Facebook (Opens in new window) Facebook
* Click to share on LinkedIn (Opens in new window) LinkedIn
*
* Login to Reply
https://make.wordpress.org/core/2025/12/11/planning-for-7-0/
