7.1 Dev Note Tracking Issue

[t-hamano]

Tracking all Dev Notes from Gutenberg plugin releases v22.7 - v23.6

Please read the information below carefully. If you have questions or suggestions, connect via Slack in the #7-1-release-leads or comment here.

Important

🗓 Deadline Drafts for All Dev Notes - 29 July 2026 79186(around Beta 3, so there's enough time for reviews)
🗓 Deadline All Dev Notes Published - 3 August 2026 (before RC1)

Not all developer-related information must be in a separate DevNote on the Make Core blog for the field guide. We can group related information. We can already decide whether some features warrant a stand-alone blog post or a group post.

Stand-alone post

To streamline the process and eliminate bottlenecks, all writers of stand-alone dev notes will write them on the Make Core Blog.

Instructions

• Create your note in a new post,
• Save as Draft
• Enable public preview
• Share the link to the public preview in a comment below as ready for review
• "For dev notes, each one must have at least two reviewers" (Handbook)

Part of a group post

If the information related to your PR will be part of a group post, please write the dev note in a comment on the PR, so it can be reviewed and, if necessary, commented on by the release docs team or a reviewer.

Before you start writing 📣 please read the handbook pages:

• ⭐️ Writing developer notes
• ⭐️ Style & Substance section of the Post & Comment Guidelines for Make Blog
• ⭐️ Documentation Style Guide - Good for reference, when in doubt, especially when English is not your native language.

---

There are two labels relevant to DevNotes :

• needs dev note
• has dev note

If you worked on a feature/module/component that definitely needs a dev note, please assign the label needs dev note. If you already added the Dev Note to the make blog on draft or as a comment on the PR, please label it has dev note.

---

Important

Please add your dev note to this list if it's missing.

Style with states, Responsive editing

⚒️ Draft: https://make.wordpress.org/core/?p=124535&preview=1&_ppp=c12ce0c63d

@tellthemachines @talldan @MaggieCabrera @t-hamano

This feature is a bit large, so I feel a standalone dev note would be more appropriate than including it with the Editor Misc. At the very least, we need to inform the consumers that viewport or state styles can now be defined in theme.json.

• Responsive style states for blocks - iteration for WP 7.1 #77817
• Try responsive global block styles with states #77513
• Style states: Use symbols for property keys to avoid clashes #79210
• Allow setting viewport tablet and mobile values in theme.json #79104
• Navigation link: add support to style current menu item via theme.json #75736
• Add support for layout responsive styles #78543
• Add supports for pseudo states on single block instances #76491
• Integrate Resizable Editor with Device Preview and add Responsive editing #75121

New Block Support: Background Gradient

⚒️ Draft: https://make.wordpress.org/core/?p=124676&preview=1&_ppp=0fd12e7801

@aaronrobertshaw @ramonjd

• Block Supports: Add background gradient support that can combine with background images #75859

New Block Support: Minimum Width

⚒️ Draft: https://make.wordpress.org/core/?p=124685

@aaronrobertshaw @tellthemachines

• Block Supports: Add min width support to dimensions #76949

New Block Support: innerContent

@youknowriad

• Blocks: Add innerContent support for static inner blocks, adopt it in the HTML block #79115
• Block variations: Support innerContent for the Custom HTML block #79659

New Block Support: editableRoot

@ellatrix

• Add an editableRoot block support for native cross-block selection #79105

Text Shadow Support in Global Styles

⚒️ Draft: https://make.wordpress.org/core/?p=124682

@t-hamano @ramond @aaronrobertshaw

• Global Styles: Add textShadow style support #73320

Editor Misc

Regarding the following items, it might be possible to consolidate them into a few groups rather than having separate dev notes for each.

Pattern Editing:

⚒️ Draft: #75717 (comment)

@CookieDarb @ramonjd

• Block Editor: Allow overriding disableContentOnlyForTemplateParts setting #79191
• Related PR: https://make.wordpress.org/core/2026/03/15/pattern-editing-in-wordpress-7-0

Block Transforms

⚒️ Draft: #78713 (comment)

@tellthemachines @talldan

• Try allowing transforms to a variation of another block #78713

Migrate parsing library

@Mamaduka @sgomes

• Blocks: Migrate Markdown converter from showdown to marked #77953

Navigation block markup change

@sarthaknagoshe2002 @talldan @scruffian @tellthemachines

• Prevent font-size propagation in Navigation items causing em compounding #77419

Blocks: Stabilize APIs

@talldan @Mamaduka

• Blocks package: Stabilize cloneSanitizedBlock and sanitizeBlockAttributes #79928

Core Data

@Mamaduka @jsnajdr

• Core Data: Fix incorrect pagination for non-paginated entities #76406

No-op Packages

@mirka @Mamaduka

• Make @wordpress/reusable-blocks a no-op compatibility package #79186
• Make @wordpress/nux a no-op compatibility package #77773 — Dev Note added ✅
• Deprecate @wordpress/reusable-blocks public APIs #79805

Enforced iframed editor

⚒️ Draft: https://make.wordpress.org/core/?p=124614&preview=1&_ppp=9298693fee

@t-hamano @ellatrix @Mamaduka

We are planning to take one of the following two approaches, and in either case, a dev note will be necessary.

• Post editor: always iframe #74042

Media Editor

@ramonjd, @andrewserong

• It may be beneficial to explain how to build a custom media editor using the public APIs MediaEditorProvider, MediaPreview, MediaForm: https://github.com/WordPress/gutenberg/blob/trunk/packages/media-editor/README.md#usage
• Soft deprecate inline cropper: Media Editor: remove inline cropper (follow-up to #78653) #78654

Client-side Media Processing

⚒️ Draft: https://make.wordpress.org/core/wp-admin/post.php?post=124446&action=edit

@adamsilverstein @andrewserong @swissspidy

• Docs: Add client-side media processing documentation #75895: This PR already includes a draft post for Make/Core.
• Media: Add hooks and extension points for client-side media processing #74913
• Client Side Media iteration for WordPress 7.1: stabilization, docs, and Core backports #76756

DataViews, DataForm, View Config API

@oandregal @ntsekouras

It might be helpful to have specific code examples regarding the get_entity_view_config_{$kind}_{$name} filter.

• DataViews, DataForm, et al. in WordPress 7.1 #76045

SVG Icon API, Icons

⚒️ Draft: https://make.wordpress.org/core/?p=124593&preview=1&_ppp=6b0d70faaa

@t-hamano @mcsf @tyxla @jasmussen @mirka

• SVG Icon API: Iteration for WordPress 7.1 #75715
• Icons: Add APIs for collection and icon registration #77260
• Icons: Add PHP method(s) for rendering inline SVG icons from the registry #78332
• Icons: self declare color #79320 (@mirka) — Dev Note added ✅

Components

⚒️ Draft: https://make.wordpress.org/core/?p=124581&preview=1&_ppp=c8060ea4b2

• Hard deprecate 40px default size: Components: Deprecate 36px default size #65751 (@mirka) — Dev Note added ✅
• Components: Remove deprecated __experimentalApplyValueToSides export #78528 (@mirka) — Dev Note added ✅
• Navigation: Hard deprecate component #78529 (@mirka) — Dev Note added ✅
• Components: migrate View away from Emotion #79443 (@ciampo) — Dev Note added ✅

Design System

@WordPress/gutenberg-components

Consider if there is anything related to the 7.1 release that should be communicated to consumers

• Theme: Remove experimental package messaging #80049 (@ciampo ) — Dev Note added ✅

---

✅ Persistent Admin Bar

Published: https://make.wordpress.org/core/2026/07/13/consistent-navigation-in-wordpress-7-1-with-persistent-toolbar/

@fushar

• WordPress 7.1: An omnipresent, consistent admin bar #79036

[t-hamano]

@annezazu @joedolson @BenjaminZekavica @kjnanda, I have added the items that I decided need to be published as dev notes at this time to the list.

Each item in these lists is assigned to the person who primarily contributed to its feature (e.g., the PR submitter or PR reviewer).

@WordPress/gutenberg-core Please let me know if there is anything else we should add.

[luisherranz]

Thanks @t-hamano.

I removed #75563 from the list as it was included in Gutenberg 22.6 and therefore present in WordPress 7.0.

For the record, there is nothing new in WordPress 7.1 regarding the Interactivity API.

[ramonjd]

It may be beneficial to explain how to build a custom media editor using the public APIs

Thanks @t-hamano. I'm not sure we're quite there yet, but yes, it'd be good to explain how these piece will fit together. There are plans to promote the cropper to a package one day, or at least create a thin public interface. cc @andrewserong for confidence check.

[tyxla]

Thank you, @t-hamano!

I'm removing Deprecate Classic Block from the list because we're reverting that for 7.1 - see this comment and this post for more information.

[andrewserong]

I'm not sure we're quite there yet, but yes, it'd be good to explain how these piece will fit together. There are plans to promote the cropper to a package one day, or at least create a thin public interface. cc @andrewserong for confidence check.

I'd agree with this. One way to frame it would be to say that the media editor lands in 7.1 in the form of the modal and that the cropping tools will be expanding in subsequent releases for plugins to build on top of. For now (and while we gather feedback on the new editor) the cropper remains a private implementation detail, but in future releases a dev note showing how plugins could use it would be good.

[t-hamano]

Since collaborative editing is being punted entirely from 7.1, I would like to exclude it from the list.

[adamsilverstein]

Docs: Add client-side media processing documentation #75895: This PR already includes a draft post for Make/Core.

I have now posted this as a draft on make and removed from the PR: https://make.wordpress.org/core/wp-admin/post.php?post=124446&action=edit

[fushar]

Posted a draft for persistent admin bar, not sure where to put this in the list above 😄 https://make.wordpress.org/core/?p=124509&preview=true

[t-hamano]

@fushar Thanks for reaching out! I believe the persistence of the admin bar is also related to Gutenberg, so let's track it in this issue.