Title: Planning for 7.0
Author: Matias Ventura
Published: December 11, 2025
Last modified: December 20, 2025

---

 [  ](https://profiles.wordpress.org/matveb/) [Matias Ventura](https://profiles.wordpress.org/matveb/)
4:44 pm _on_ December 11, 2025     
Tags: [7.0 ( 76 )](https://make.wordpress.org/core/tag/7-0/),
[phase 3 ( 18 )](https://make.wordpress.org/core/tag/phase-3/)   

# Planning for 7.0

With 6.9 [out in the world](https://wordpress.org/download/releases/6-9/), 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](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 by the repository owner. [https://github.com/](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/](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..

**Table of Contents**

 * [Collaboration ](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#collaboration)
 * [Admin](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#admin)
 * [APIs](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#apis)
 * [Navigation Block](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#navigation-block)
 * [Customization](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#customization)
 * [Blocks](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#blocks)
 * [Media](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/#media)

## 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](https://github.com/WordPress/gutenberg/issues/52593)
 * 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](https://profiles.wordpress.org/acicovic/), [@aduth](https://profiles.wordpress.org/aduth/),
   [@alecgeatches](https://profiles.wordpress.org/alecgeatches/), [@czarate](https://profiles.wordpress.org/czarate/),
   [@ingeniumed](https://profiles.wordpress.org/ingeniumed/), [@jsnajdr](https://profiles.wordpress.org/jsnajdr/),@
   maxschmelingkc, [@paulkevan](https://profiles.wordpress.org/paulkevan/), [@shekharnwagh](https://profiles.wordpress.org/shekharnwagh/),
   [@youknowriad](https://profiles.wordpress.org/youknowriad/)

**Notes i2**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73260)
 * 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](https://profiles.wordpress.org/adamsilverstein/),
   [@jeffpaul](https://profiles.wordpress.org/jeffpaul/), [@mamaduka](https://profiles.wordpress.org/mamaduka/)

---

## Adminadmin (and super admin)

**Improving screens across wp-admin**

 * Link: TBD
 * Key considerations:
    - [Explore CSS improvements](https://core.trac.wordpress.org/ticket/64308) 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](https://profiles.wordpress.org/fabiankaegy/),
   [@karmatosed](https://profiles.wordpress.org/karmatosed/), [@mcsf](https://profiles.wordpress.org/mcsf/)

**DataViews and DataForms iterations**

 * Link: [7.0 iteration issue](https://github.com/WordPress/gutenberg/issues/73076)
 * 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](https://profiles.wordpress.org/oandregal/)

**Design System**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/71196)
 * 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](https://profiles.wordpress.org/0mirka00/), [@aduth](https://profiles.wordpress.org/aduth/),
   [@jsnajdr](https://profiles.wordpress.org/jsnajdr/), [@mciampini](https://profiles.wordpress.org/mciampini/),
   [@wildworks](https://profiles.wordpress.org/wildworks/)

**Font library admin section**

 * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/57904)
 * Key considerations:
    - **✅ **Support for block themes.
    - Support for hybrid/classic themes.
 * Contributors: [@youknowriad](https://profiles.wordpress.org/youknowriad/)

**RevisionsRevisions 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](https://github.com/WordPress/gutenberg/issues/52138)
 * 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](https://profiles.wordpress.org/adamsilverstein/)

**Customizable Keyboard Shortcuts**

 * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/3218)
 * 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](https://github.com/WordPress/gutenberg/issues/70710)
 * 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](https://github.com/WordPress/ai/issues/40).
    - Command palette and UI:
       * Differentiation between commands.
       * Ability to support two stages of a command.
 * Contributors: [@jorgefilipecosta](https://profiles.wordpress.org/jorgefilipecosta/)
   [@gziolo](https://profiles.wordpress.org/gziolo/) [@senadir](https://profiles.wordpress.org/senadir/)
   [@youknowriad](https://profiles.wordpress.org/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](https://reactjs.org/)
19**

 * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/71336)
 * 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](https://profiles.wordpress.org/aduth/) [@jsnajdr](https://profiles.wordpress.org/jsnajdr/)
   [@mamaduka](https://profiles.wordpress.org/mamaduka/) [@ralucastn](https://profiles.wordpress.org/ralucastn/)
   [@tyxla](https://profiles.wordpress.org/tyxla/)

**Block API: Add validation levels**

 * Links: [Github issue](https://github.com/WordPress/gutenberg/issues/21703) with
   [initial PR** **](https://github.com/WordPress/gutenberg/pull/73116)
 * 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](https://profiles.wordpress.org/matveb/) [@mcsf](https://profiles.wordpress.org/mcsf/)
   [@youknowriad](https://profiles.wordpress.org/youknowriad/)

**Enforced iframed editor**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73138).
    - 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](https://profiles.wordpress.org/ellatrix/), [@wildworks](https://profiles.wordpress.org/wildworks/)

**WP client AI API**

 * Link: [GitHub project](https://github.com/WordPress/wp-ai-client)
 * 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](https://profiles.wordpress.org/flixos90/) [@jason_the_adams](https://profiles.wordpress.org/jason_the_adams/)

**Creating blocks and patterns on the server**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/71792)
 * 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](https://profiles.wordpress.org/priethor/), TBD

**wordpress/build and routing (site editor)**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/70862); [Scripts issue](https://github.com/WordPress/gutenberg/issues/72032)
 * 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/](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](https://profiles.wordpress.org/youknowriad/) 

**Shortblocks**

 * Links: [Bits as dynamic tokens](https://make.wordpress.org/core/2024/06/08/proposal-bits-as-dynamic-tokens/);
   [Bits: Introduce the ability to store and render bits](https://github.com/WordPress/wordpress-develop/pull/6390),
   [Rich text: try BITS with block binding API](https://github.com/WordPress/gutenberg/pull/60735),
   [Introduce parser for dynamic token system](https://github.com/WordPress/gutenberg/pull/42015).
 * 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](https://profiles.wordpress.org/dmsnell/), [@ellatrix](https://profiles.wordpress.org/ellatrix/),
   [@jonsurrell](https://profiles.wordpress.org/jonsurrell/)

**Block bindings iterations**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73467)
 * Key considerations:
    - [Open up “Pattern Overrides” and therefore intern block bindings to custom dynamic blocks](https://href.li/?https://github.com/WordPress/gutenberg/issues/64870).
    - [Filter available source items for a given attribute by format](https://href.li/?https://github.com/WordPress/gutenberg/issues/72446).
    - Align with Fields API as a requirement. 
 * Contributors: [@bernhard-reiter](https://profiles.wordpress.org/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](https://github.com/WordPress/gutenberg/issues/65699)
 * Key considerations:
    - [Better insertion](https://github.com/WordPress/gutenberg/issues/73647).
    - [Pattern editing and ContentOnly interactivity](https://github.com/WordPress/gutenberg/issues/71517).
    - Better presentation of “bound” page items.
 * Contributors: [@get_dave](https://profiles.wordpress.org/get_dave/), [@jeryj](https://profiles.wordpress.org/jeryj/)

**Ability to customise “mobile” overlay **

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73084)
 * Key considerations:
    - Implemented as a template part.
    - Ability to customize when the overlay appears (breakpoint settings) just for
      navigation overlay.
 * Contributors: [@get_dave](https://profiles.wordpress.org/get_dave/), [@jeryj](https://profiles.wordpress.org/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](https://github.com/WordPress/gutenberg/pull/73631).
    - 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](https://github.com/WordPress/gutenberg/pull/73628).
 * Contributors: [@ellatrix](https://profiles.wordpress.org/ellatrix/)

**Pattern Editing (aka ContentOnly)**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/71517)
 * Key considerations:
    - Ensure proper discoverability to enter/exit.
    - Ensure it works well with synced patterns. 
 * Contributors: [@aaronrobertshaw](https://profiles.wordpress.org/aaronrobertshaw/),
   [@andrewserong](https://profiles.wordpress.org/andrewserong/), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/),
   [@ramonopoly](https://profiles.wordpress.org/ramonopoly/) [@talldanwp](https://profiles.wordpress.org/talldanwp/).

**Improve template management**

 * Link: [GitHub PR](https://github.com/WordPress/gutenberg/pull/67125)
 * Key considerations:
    - Direction and UXUX User experience is still TBD and needs more exploration.
    - [Retain access to template parts across theme switches](https://github.com/WordPress/gutenberg/issues/72452).
 * Contributors: [@ellatrix](https://profiles.wordpress.org/ellatrix/) [@scruffian](https://profiles.wordpress.org/scruffian/).

**Responsive editing mode**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/19909)
 * Key considerations:
    - Toggle to engage responsive editing mode.
    - Block visibility i2: [add ability to hide blocks based on screen size](https://github.com/WordPress/gutenberg/issues/72502).
    - Allow style changes to be saved and retrieved for different breakpoints.
    - Allow customization of hardcoded breakpoints.
 * Contributors: [@matveb](https://profiles.wordpress.org/matveb/) [@ramonopoly](https://profiles.wordpress.org/ramonopoly/)

**Block supports and design tools:  **

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73772)
 * Key considerations:
    - Add text line indent support. [GitHub PR](https://github.com/WordPress/gutenberg/pull/73114).
    - Add [gradient support to text color options](https://github.com/WordPress/gutenberg/issues/30982).
    - [Add height block support to dimension ](https://github.com/WordPress/gutenberg/pull/71914).
    - Styles support for text shadow. [GitHub PR](https://github.com/WordPress/gutenberg/pull/73320).
    - Support for text alignment [with justify support](https://github.com/WordPress/gutenberg/issues/50319).
    - [Allow Video backgrounds to be ‘Fixed’](https://github.com/WordPress/gutenberg/issues/52585).
    - [Balanced line wrap](https://github.com/WordPress/gutenberg/issues/52387).
    - Text columns. [GitHub issue](https://github.com/WordPress/gutenberg/issues/27118);
      [GitHub issue](https://github.com/WordPress/gutenberg/issues/25459).
    - Support aspect ratio [on wide and full images](https://github.com/WordPress/gutenberg/issues/53652).
 * Contributors: TBD, [@aaronrobertshaw](https://profiles.wordpress.org/aaronrobertshaw/)
   [@matveb](https://profiles.wordpress.org/matveb/) [@youknowriad](https://profiles.wordpress.org/youknowriad/)
   [@wildworks](https://profiles.wordpress.org/wildworks/)

---

## Blocks

Keeping the momentum [on adding new blocks](https://github.com/WordPress/gutenberg/issues/71026)
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](https://github.com/WordPress/gutenberg/issues/73845)
 * 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](https://github.com/WordPress/gutenberg/issues/28860); [GitHub PR](https://github.com/WordPress/gutenberg/pull/73023)
 * Contributors: [@matveb](https://profiles.wordpress.org/matveb/) 

**Modernize Code editor + Code block**

 * Link: [GitHub link](https://github.com/WordPress/gutenberg/issues/10423)
 * Contributors: [@jonsurrell](https://profiles.wordpress.org/jonsurrell/), [@westonruter](https://profiles.wordpress.org/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](https://github.com/WordPress/gutenberg/pull/70603#top)
      in this work too.
 * Contributors: [@tyxla](https://profiles.wordpress.org/tyxla/)

**Leverage iAPI for instant search block & submit comments without full page refresh**

 * Links: [Instant Search](https://href.li/?https://github.com/WordPress/gutenberg/pull/67181),
   [submit comments without requiring a full-page refresh](https://href.li/?https://github.com/WordPress/gutenberg/pull/53737).
 * Contributors: TBD

**Writing flow + drag and drop improvements**

 * Link: [GitHub issue](https://href.li/?https://github.com/WordPress/gutenberg/issues/63255)
 * 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](https://github.com/WordPress/gutenberg/issues/73581)
      and inline images.
 * Contributors: [@ellatrix](https://profiles.wordpress.org/ellatrix/)

**✅ Tabs block **

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73230)
 * Contributors: [@mikachan](https://profiles.wordpress.org/mikachan/)

**Release the Table of Contents block **

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/42229)
 * Contributors: TBD 

**Playlist block**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/805)
 * Contributors: [@scruffian](https://profiles.wordpress.org/scruffian/)

**Slider block**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/43369), [GitHub issue](https://github.com/WordPress/gutenberg/issues/25501),
   [GitHub issue](https://github.com/WordPress/gutenberg/issues/25502)
 * Contributors: [@lstraczynski](https://profiles.wordpress.org/lstraczynski/), 
   [@karolmanijak](https://profiles.wordpress.org/karolmanijak/)

**Dialog block**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/pull/71618)
 * Contributors: TBD

**✅ Breadcrumb block**

 * Link: [GitHub Issue](https://github.com/WordPress/gutenberg/issues/72498)
 * Team: [@ntsekouras](https://profiles.wordpress.org/ntsekouras/)

**Add more dynamic URLs via block bindings to Buttons block and Image block**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/18345#issuecomment-3400461363),
   [API shape](https://github.com/WordPress/gutenberg/issues/72426)
 * Team: TBD

**Icon block**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/16484)
 * Key considerations:
    - Ship with a default set made out of some wordpress/icons.
    - Allow extenders to register their own sets.
 * Contributors: [@mcsf](https://profiles.wordpress.org/mcsf/) [@welcher](https://profiles.wordpress.org/welcher/)

**Gallery block: add lightbox support with the ability to switch between images**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/56310), [GitHub PR](https://github.com/WordPress/gutenberg/pull/62906#issuecomment-3535417814)
 * Contributor: [@wildworks](https://profiles.wordpress.org/wildworks/)

**Introduce heading levels as Heading block variations**

 * Link: [Github issue](https://github.com/WordPress/gutenberg/issues/42181); [https://github.com/WordPress/gutenberg/issues/42181](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](https://profiles.wordpress.org/matveb/)

**Aim to stabilize grid block**

 * Link: [GitHub issue](https://github.com/WordPress/gutenberg/issues/73773)
 * Contributor: [@isabel_brison](https://profiles.wordpress.org/isabel_brison/)

---

## Media

**Client side media work**

 * Link: [GitHub issue ](https://github.com/WordPress/gutenberg/issues/61447)
 * Contributors: [@adamsilverstein](https://profiles.wordpress.org/adamsilverstein/),
   [@ramonopoly](https://profiles.wordpress.org/ramonopoly/)

**Media editor**

 * Link: [Iteration issue](https://github.com/WordPress/gutenberg/issues/73771)
 * Contributors: [@aaronrobertshaw](https://profiles.wordpress.org/aaronrobertshaw/),
   [@andrewserong](https://profiles.wordpress.org/andrewserong/), [@isabel_brison](https://profiles.wordpress.org/isabel_brison/),
   [@ramonopoly](https://profiles.wordpress.org/ramonopoly/), [@talldanwp](https://profiles.wordpress.org/talldanwp/)

---

Designers looking across all these projects: [@fcoveram](https://profiles.wordpress.org/fcoveram/),
[@joen](https://profiles.wordpress.org/joen/), [@jameskoster](https://profiles.wordpress.org/jameskoster/),
[@mattmiklic](https://profiles.wordpress.org/mattmiklic/).

[#7-0](https://make.wordpress.org/core/tag/7-0/), [#phase-3](https://make.wordpress.org/core/tag/phase-3/)

### Share this:

 * [  Threads ](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/?share=threads)
 * [  Mastodon ](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/?share=mastodon)
 * [  Bluesky ](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/?share=bluesky)
 * [  X ](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/?share=x)
 * [  Facebook ](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/?share=facebook)
 * [  LinkedIn ](https://make.wordpress.org/core/2025/12/11/planning-for-7-0/?share=linkedin)

 1.  ![](https://secure.gravatar.com/avatar/4358d28c1e85f9015cb3363e024e2b238bccb44d05c4b84e9a38aafef0d83ac9?
     s=32&d=mm&r=g)
 2.   [Riad Benguella](https://profiles.wordpress.org/youknowriad/)  5:00 pm _on_ December
     11, 2025
 3.  I realize this is not a commitment but it’s an impressive list nonetheless. I 
     hope we can ship the maximum from this.
 4.  ![](https://secure.gravatar.com/avatar/fc43a66be3c49f7c4b27529ae501ccf53de0525cba9204cfff9e644fb70c2d67?
     s=32&d=mm&r=g)
 5.   [Aminul Islam](https://profiles.wordpress.org/theaminuldev/)  5:17 pm _on_ December
     11, 2025
 6.  My question is: will responsiveness become a priority in the next ten years?
 7.   * ![](https://secure.gravatar.com/avatar/4f50dc56c80eceb636a7ef7d036a019a7d4189e8b3f87d9c899e848248ef36d8?
        s=32&d=mm&r=g)
      *  [annezazu](https://profiles.wordpress.org/annezazu/)  7:26 pm _on_ December
        11, 2025
      * Responsive editing mode is listed here. Please check it out! It continues a
        range of work around responsiveness that’s been done in prior releases.
         - ![](https://secure.gravatar.com/avatar/00ce0f258fcc5e5d29897a5e81316009713e9104cfaf49f481c5bce3f81c7cb1?
           s=32&d=mm&r=g)
         -  [John Russell](https://profiles.wordpress.org/laubsterboy/)  5:57 pm _on_
           February 25, 2026
         - We fully embraced container queries with our custom theme and custom blocks(
           and coreCore Core is the set of software required to run WordPress. The 
           Core Development Team builds WordPress. blocks where needed/possible) and
           have almost entirely eliminated the need for device size based settings/
           styles in the 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.
 8.  ![](https://secure.gravatar.com/avatar/08f5251e656bb9e514f0991825afcfed1053665cc3b79036b6c229552fd6ccd0?
     s=32&d=mm&r=g)
 9.   [Paul Bearne](https://profiles.wordpress.org/pbearne/)  5:38 pm _on_ December
     11, 2025
 10. I didn’t see the tests update to support PHPUnit 10/11 in the list [https://core.trac.wordpress.org/ticket/62004](https://core.trac.wordpress.org/ticket/62004)
 11. I want to get this task done so I can get back to writing the missing tests!!
 12. ![](https://secure.gravatar.com/avatar/0c00bc6bb79905cd73ec1cb0f22bf813f7f34f46ee670d018b30b5569b2924dd?
     s=32&d=mm&r=g)
 13.  [Tammie Lister](https://profiles.wordpress.org/karmatosed/)  5:59 pm _on_ December
     11, 2025
 14. Really excited to see this list, looking forward to diving in where is needed 
     and us all improving the experience.
 15. ![](https://secure.gravatar.com/avatar/f8f418aab55b09d54413662469ca9fb3199199a553f8c283d92e7a1a8b3416f6?
     s=32&d=mm&r=g)
 16.  [Juan Aldasoro](https://profiles.wordpress.org/juanfra/)  9:57 am _on_ December
     12, 2025
 17. This looks great! Excited to see where 7.0 takes us ✨
 18. ![](https://secure.gravatar.com/avatar/82e095c8bc229017b128e53940ea534aa31f6624431bedee24c7e8756e42dd1c?
     s=32&d=mm&r=g)
 19.  [Adam Silverstein](https://profiles.wordpress.org/adamsilverstein/)  3:25 pm 
     _on_ December 12, 2025
 20. This list is huge, so exciting to see all the features and work underway.
 21. Please add my name to the Notes i2 list as I plan to continue working on Notes.
     Also, please add me to RevisionsRevisions 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.–
     although not my highest priority this cycle, I am deeply invested in revisions
     and plan to support from the coreCore Core is the set of software required to 
     run WordPress. The Core Development Team builds WordPress. side at a minimum.
 22.  * ![](https://secure.gravatar.com/avatar/56bab68692c2a170323d65a02b2faec6c12e2b5eda10f0ee5b53610416f389d4?
        s=32&d=mm&r=g)
      *  [Matias Ventura](https://profiles.wordpress.org/matveb/)  5:10 pm _on_ December
        12, 2025
      * Done, thank you! 🙂
      * ![](https://secure.gravatar.com/avatar/603a3c8128c0966d4671b093c07634cf9f0f505644b82bfa5dcf57c27e5ded66?
        s=32&d=mm&r=g)
      *  [Ella Van Durpe](https://profiles.wordpress.org/ellatrix/)  12:22 pm _on_ 
        January 22, 2026
      * Worth noting that I’ve been working on in-editor revisionsRevisions 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. ([tracking issue](https://github.com/WordPress/gutenberg/issues/74742)).
 23. ![](https://secure.gravatar.com/avatar/e783c9bb428fdb2a40d72e88425248f41035a1f05b7133a1ae9f4f88257c168e?
     s=32&d=mm&r=g)
 24.  [Seth Rubenstein](https://profiles.wordpress.org/smrubenstein/)  5:12 pm _on_
     December 14, 2025
 25. Wow what a huge list, very exciting. Just as an update from me, I plan on getting
     Dialog to experimental state in January and if someone doesn’t beat me to it I
     can come back in and finish off the polish list on Tabs.
 26. ![](https://secure.gravatar.com/avatar/0c00bc6bb79905cd73ec1cb0f22bf813f7f34f46ee670d018b30b5569b2924dd?
     s=32&d=mm&r=g)
 27.  [Tammie Lister](https://profiles.wordpress.org/karmatosed/)  2:52 pm _on_ December
     15, 2025
 28. > Improving screens across wp-adminadmin (and super admin)
 29. Please also add my name to this as I am already starting to find ways to collaborate.
     Along with this I would also be very happy to contribute to ‘Design System’. I
     want to be helpful in other ways that are useful but this is where I am starting.
 30. ![](https://secure.gravatar.com/avatar/63b496ec3806485229b4f934b26643dad6e734ca6e6ef7b38c846205b01cd37f?
     s=32&d=mm&r=g)
 31.  [Weston Ruter](https://profiles.wordpress.org/westonruter/)  5:11 am _on_ December
     22, 2025
 32. Let’s add “View Transitions” to this list, per [Matt in #core](https://wordpress.slack.com/archives/C02RQBWTW/p1766110325508679).
     I’ll be contributing to that. This will go nicely with the adminadmin (and super
     admin) refresh. The admin view transitions should be an easy lift. I’m not entirely
     sure view transitions on the frontend will be so straightforward. We may need 
     to scope specifically to Twenty Twenty-Five (or to 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. themes) but then provide
     an 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. for themes to configure for their needs. The [feature plugin](https://wordpress.org/plugins/view-transitions/)
     introduces a `view-transitions` theme support for this purpose.
 33.  * ![](https://secure.gravatar.com/avatar/63b496ec3806485229b4f934b26643dad6e734ca6e6ef7b38c846205b01cd37f?
        s=32&d=mm&r=g)
      *  [Weston Ruter](https://profiles.wordpress.org/westonruter/)  2:38 am _on_ 
        January 2, 2026
      * I’ve filed two tickets: [#64470](https://core.trac.wordpress.org/ticket/64470)(
        for the adminadmin (and super admin)) and [#64471](https://core.trac.wordpress.org/ticket/64471)(
        for the frontend).
 34. ![](https://secure.gravatar.com/avatar/603a3c8128c0966d4671b093c07634cf9f0f505644b82bfa5dcf57c27e5ded66?
     s=32&d=mm&r=g)
 35.  [Ella Van Durpe](https://profiles.wordpress.org/ellatrix/)  12:11 pm _on_ January
     22, 2026
 36. > Improve template management
 37. This is punted to a future release until we agree on a design and UXUX User experience.
 38. ![](https://secure.gravatar.com/avatar/d1206b2538cfce31db7cfe5cf02cc5913c44d6428cf218ea0e357faa23accb0c?
     s=32&d=mm&r=g)
 39.  [André Maneiro](https://profiles.wordpress.org/oandregal/)  4:08 pm _on_ January
     22, 2026
 40. I wanted to re-share an update from the [DataViews/DataForm iteration issue](https://github.com/WordPress/gutenberg/issues/73076#issuecomment-3785224518):
 41.  * Some tasks had been punted for the next iteration, including [visualizing hierarchical post types](https://github.com/WordPress/gutenberg/issues/74072).
      * The current focus is on the aspects of the Field 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. we need to
        support well emerging use cases, such as [Pattern editing](https://github.com/WordPress/gutenberg/issues/73261)
        and [PHP-only blocks](https://github.com/WordPress/gutenberg/issues/71792).
        We’re prioritizing work on: [74409](https://github.com/WordPress/gutenberg/pull/74409),
        [74858](https://github.com/WordPress/gutenberg/issues/74858), [74856](https://github.com/WordPress/gutenberg/issues/74856),
        [73180](https://github.com/WordPress/gutenberg/issues/73180), [72614](https://github.com/WordPress/gutenberg/issues/72614),
        [74105](https://github.com/WordPress/gutenberg/pull/74105).
      * We still want to extend the existing Site Editor screens, but it has been scoped
        down to registering fields as per [#74865](https://github.com/WordPress/gutenberg/issues/74865).
        We’ll focus on the above foundational work, first.
 42. ![](https://secure.gravatar.com/avatar/4f50dc56c80eceb636a7ef7d036a019a7d4189e8b3f87d9c899e848248ef36d8?
     s=32&d=mm&r=g)
 43.  [annezazu](https://profiles.wordpress.org/annezazu/)  2:41 am _on_ February 19,
     2026
 44. As we are veering towards betaBeta 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, I wanted to share a bigger update of where the above stands as
     I can gather from talking to people, testing, and gathering updates. I’m sharing
     this here for completeness and will link to it in the 7-0 release leads channel
     for others to benefit from. This is purposefully very, very, very concise.
 45. 🟢 **Green (Good Progress/Ready)**
 46.  * [Real time collaboration](https://github.com/WordPress/gutenberg/issues/74549).
        There are some remaining questions around opt in/opt out strategies and limitations
        that are being sorted and are known.
      * [Visual Revisions](https://github.com/WordPress/gutenberg/issues/74742).
      * [PHP-only block registration w/ auto-generated inspector controls](https://github.com/WordPress/gutenberg/issues/71792).
      * [Navigation: Ability to customise “mobile” overlay](https://github.com/WordPress/gutenberg/issues/73084#issuecomment-3920201929).
      * [Simpler navigation editing](https://github.com/WordPress/gutenberg/issues/65699#issuecomment-3920199661).
      * [Ability to hide blocks responsively](https://github.com/WordPress/gutenberg/issues/73776#issuecomment-3911455239).
      * [Add QuickEdit to Data Views](https://github.com/WordPress/gutenberg/pull/75565).
      * [Cover: add support for background videos as embeds](https://github.com/WordPress/gutenberg/pull/73023).
        Note that this has [some residual questions around opt out options](https://github.com/WordPress/gutenberg/issues/75069).
      * [Breadcrumb block](https://github.com/WordPress/gutenberg/issues/21943).
      * [Icon block](https://github.com/WordPress/gutenberg/issues/16484).
      * [Enable grid block to be responsive when columns are set](https://github.com/WordPress/gutenberg/pull/73662),
        along with a [range of other improvements.](https://github.com/WordPress/gutenberg/issues/73773)
      * [Gallery block: add lightbox support](https://github.com/WordPress/gutenberg/pull/62906).
      * [Introduce heading levels as Heading block variations](https://github.com/WordPress/gutenberg/issues/42181)(
        sub item of 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. supports).
      * [Block bindings: Open up “Pattern Overrides”](https://github.com/WordPress/gutenberg/issues/64870).
      * [Add text line indent support](https://github.com/WordPress/gutenberg/pull/73114)(
        sub item of block supports).
      * [Add height block support to dimension](https://github.com/WordPress/gutenberg/pull/71914)(
        sub item of block supports).
      * [Support aspect ratio on wide and full images](https://github.com/WordPress/gutenberg/issues/53652)(
        sub item of block supports).
      * [Client side Abilities API](https://github.com/WordPress/gutenberg/pull/72703)(
        sub item of Abilities & Workflows).
      * [Improving screens across wp-admin](https://core.trac.wordpress.org/ticket/64308).
        The ticketticket Created for both bug reports and feature development on the
        bug tracker. is still open but there [have been PRs done against this](https://core.trac.wordpress.org/ticket/64308#comment:26).
      * [Dedicated font library section](https://github.com/WordPress/gutenberg/pull/73630)
        with compatibility for all themes. There were concerns with related build process
        changes within this work when it comes to wordpress/build and routing (punted
        for everything else outside of the site editor) but it’s not dependent to land
        the feature.
      * [Pattern Editing](https://github.com/WordPress/gutenberg/issues/73775) (aka
        ContentOnly). The bulk of the features landed with an [iteration issue](https://github.com/WordPress/gutenberg/issues/75717)
        opened already for 7.1.
      * [WP client AI API](https://make.wordpress.org/core/2026/02/03/proposal-for-merging-wp-ai-client-into-wordpress-7-0/#comment-48384).
        Made it after discussion on the review call for 7.0.
 47. 🟡 **Yellow (At Risk/Nearly there)**
 48. This section was updated and edited over the last 24 hours since the comment was
     originally posted to share where things ended up in the green or red sections.
 49. **🔴 Red (Blocked/Major Issues)**
 50.  * [Client side media](https://github.com/WordPress/gutenberg/issues/74333) improvements.
      * [Tabs block](https://github.com/WordPress/gutenberg/issues/73230#issuecomment-3909661654).
        The block was moved back to experimental ahead of the GB release and was decided
        to not move ahead in 7.0. There are some aspects of the active tab state that
        are being done in a non-standard way and a more general solution is desired.
      * [wordpress/build and routing](https://github.com/WordPress/gutenberg/issues/70862)(
        site editor). See dedicated font library section.
      * [Playlist block](https://github.com/WordPress/gutenberg/issues/805). Work didn’t
        finish in time.
      * [Dialog block](https://github.com/WordPress/gutenberg/pull/71618). Work didn’t
        finish.
      * [Notes: Emoji support](https://github.com/WordPress/gutenberg/pull/75549). 
        Decision around storage too last minute.
      * [Notes: Compact mode](https://github.com/WordPress/gutenberg/pull/74985). Decision
        around design too last minute.
      * [WordPress Core Abilities](https://core.trac.wordpress.org/ticket/64455) (sub
        item of Abilities & Workflows)
      * [Markdown generator for content](https://core.trac.wordpress.org/ticket/64363).
        Work was rapidly evolving but it’s unclear what can land for CoreCore Core 
        is the set of software required to run WordPress. The Core Development Team
        builds WordPress. and needs more time. Work will focus on adding to wordpress.
        orgWordPress.org The community site where WordPress code is created and shared
        by the users. This is where you can download the source code for WordPress 
        core, plugins and themes as well as the central location for community conversations
        and organization. [https://wordpress.org/](https://wordpress.org/) for now.
 51. ❌ **Cancelled**
 52.  * Hierarchical post visualization (sub-item of DataViews)
      * Design System
      * Customizable Keyboard Shortcuts
      * 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](https://reactjs.org/)
        19
      * Block 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.: Add validation levels
      * Enforced iframed editor
      * Shortblocks
      * The remaining block bindings iterations for 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. fixes
        and enhancements.
      * Explore more intuitive page navigation in the site editor
      * Improve template management
      * Group block attributes
      * Modernize Code editor + Code block
      * Lazy load the Classic block
      * Leverage iAPI for instant search block & submit comments
      * Writing flow + drag and drop improvements
      * Release the Table of Contents block
      * Slider block.
      * Add more dynamic URLs via block bindings
      * Media editor
 53. cc @matveb @4thhubbard for your awareness as both project leadership and release
     squad members.
 54.  * ![](https://secure.gravatar.com/avatar/ed91c778d5bfd26ddee8ad17b9bc49b62333363c9277f3f939715e85ba67393e?
        s=32&d=mm&r=g)
      *  [Ankit K Gupta](https://profiles.wordpress.org/ankit-k-gupta/)  12:51 pm _on_
        February 19, 2026
      * Hi [@annezazu](https://profiles.wordpress.org/annezazu/),
         Notes: Emoji support&
        Compact mode are blocked. Do you have any news about “[Support partial text selection notes”](https://github.com/WordPress/gutenberg/pull/74852)?
         - ![](https://secure.gravatar.com/avatar/4f50dc56c80eceb636a7ef7d036a019a7d4189e8b3f87d9c899e848248ef36d8?
           s=32&d=mm&r=g)
         -  [annezazu](https://profiles.wordpress.org/annezazu/)  1:47 pm _on_ February
           19, 2026
         - As you can see, it has not been merged. To help out, [I added an update for Notes and what shipped here](https://github.com/WordPress/gutenberg/issues/73260#issuecomment-3927376848).
           There are no new major features.
      * ![](https://secure.gravatar.com/avatar/4f50dc56c80eceb636a7ef7d036a019a7d4189e8b3f87d9c899e848248ef36d8?
        s=32&d=mm&r=g)
      *  [annezazu](https://profiles.wordpress.org/annezazu/)  5:58 pm _on_ February
        19, 2026
      * Heads up that I just finished updating the above comment with the latest that
        I can find for the release. In particular, I focused on the yellow section 
        for anything that is sitting in between as those are the most relevant and 
        important areas to track.
      * ![](https://secure.gravatar.com/avatar/a27a6d11672af559c57e5d2bf533d369c22d7d42bc594246f11051c1c1309b8f?
        s=32&d=mm&r=g)
      *  [Andrea Roenning](https://profiles.wordpress.org/awetz583/)  7:54 pm _on_ 
        March 6, 2026
      * Looks like [Image: add focal point controls](https://github.com/WordPress/gutenberg/pull/73115)
        is also coming in 7.0 – yay!

Comments are closed.

# Post navigation

[← Summary, Dev Chat, December 10, 2025](https://make.wordpress.org/core/2025/12/10/summary-dev-chat-december-10-2025/)

[WordPress 6.9 Hotfixes →](https://make.wordpress.org/core/2025/12/12/wordpress-6-9-hotfixes/)