6.7 Dev Note Tracking Issue

[fabiankaegy]

Tracking all Dev Notes from Gutenberg plugin releases 18.6 - v19.3

Please read the information below carefully. If you have questions or suggestions, connect with @fabiankaegy via Slack, ping @fabiankaegy on GitHub, or comment here.

Important

🗓 Deadline Drafts for All Dev Notes - October 13th, 2024 (a few days before Beta 3, so there's enough time for reviews)
🗓 Deadline All Dev Notes Published - October 20nd, 2024 (a few days 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 the dev notes 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.

---

Note

The list is incomplete. We are in the process of reviewing plugin release changelogs and add them as we progress on the task.

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

---

TO DO

Progress of the Documentation work for WP 6.7 release (including the DevNotes tracked on this issue) can also be followed at WP 6.7 Documentation project dashboard

PRs with label has-dev-note or a related DevNote draft are marked with [x]

Standalone Posts:

• Editor: Add extensibility to PreviewOptions v2 #64644 - @lezama
• Split content view with open metaboxes #64351 - @stokesman
• Add plugin template registration API #61577 - @Aljullu [Draft]

Stabilize Role Attribute Property ✅ - [Draft]
@youknowriad and @getdave have agreed to work on this one and already shared a Draft.

• Blocks: Stabilise role attribute property #65484 - @getdave
• Block API: Introduce "local" attributes and use it for the image block #63076 - @youknowriad

Zoomed Out Mode
I'd love to have one dev note dedicated to all things Zoomed out mode that explains the feature and how to work with it. Including how stuff like the "Section detection algorithm" work.

@getdave has volunteered to help triage this :) A draft is available at #64197 (comment)

• Decouple "zoom/scaling the canvas" from zoom out mode (without mode rename) #65482
• Zoom out: remove experimental flag #65404
• Zoom out: Try vertical displacement when dragging a pattern between existing patterns/sections #63896
• Zoom Out: Only show the inserters when a block is selected or hovered #63668

Block Bindings
We should have a dedicated dev note for all things Block Bindings that talks about all the new stabilized API's etc. Assigned to @artemiomorales [Draft]

• Block Bindings: Open the stable editor APIs #65713
• Block Bindings: Use post meta label from register_meta in block bindings workflows #65099
• Block Bindings: Allow only admin users to create and modify bindings by default #64570
• Block Bindings: Create utils to update or remove bindings #64102
• Block bindings: UI for connecting bindings #62880
• Block bindings: Bring bindings UI in Site Editor #64072
• Block Bindings: Fix showing bindings field values in theme templates #65639

Interactivity API Updates
@DAreRodz or @michalczaplinski , can you help with this?

• Interactivity API: Add getServerState() and getServerContext() #65151
• Script Modules: Move data passing to 6.7 compat file #64006

Components Package Updates

@mirka @ciampo have volunteered to help with this :)

• Composite: stabilize APIs #63569 - @ciampo [Draft]
• FormTokenField: Deprecate bottom margin #63491 @mirka [Draft]
• CustomSelectControl: switch to ariakit-based implementation #63258 @ciampo
• CustomSelectControl V2 legacy adapter: stabilize experimental props #63248 @ciampo
• AlignmentMatrixControl: Promote to stable #60913 @ciampo
• BoxControl: Promote to stable #65469 @ciampo
• Modal: Decrease close button size #65131 @mirka [Draft]
• Deprecate DimensionControl #64951 @ciampo
• Normalize block inspector controls spacing #64526 @mirka [Draft]
• Deprecate bottom margin on BaseControl-based components #64408 @mirka [Draft]
• Button: Stabilize __experimentalIsFocusable prop #62282 - @mirka [Draft]
• SelectControl: Infer value type from options #64069 - @mirka [Draft]
• DateTime: Create TimeInput component and integrate into TimePicker #60613 @mirka [Draft]
• ToggleGroupControl: support disabled options #63450 @ciampo
• Navigator: stabilize and export APIs #64613 @ciampo

Miscellaneous Editor Updates (TBD)

• Adding Font size presets UI #63057 - @matiasbenedetto [Draft]
• Make useStyleOverride public #63656 - @ellatrix
• Try: Post content: Add clearfix #63690 - @carolinan
• ContentOnly: Add support for block styles on top-level contentOnly locked blocks #64872 - @ntsekouras
• Heading: Enable heading level curation #63535 - @ndiego
• Core Data: Support entities in the 'canUser' selector #63322 - @Mamaduka
• Global Styles: Create new public function to make it easier to expose style variations from other themes #63318 - @scruffian [Draft]
• block.json: Allow passing filename as variations field #62092 - @ockham - [Draft]
• Post Date & Comment Date: Add relative date format #62298 - @amitraj2203 - [Draft]
• Global Styles: Add a typesets section to Typography #62539 - @scruffian [Draft]
• Style engine: export util to compile CSS custom var from preset string #64490 - @ramonjd - [Draft]
• Media & Text: don't use background-image #64981 - @sgomes
• Add useEvent and revamped useResizeObserver to @wordpress/compose #64943 - @DaniGuardiola - [Draft]
• Locked Templates: blocks with contentOnly locking should not be transformable #64917 - @ramonjd [Draft]
• Global Styles: allow read access to users with edit_posts capabilities #65071 - @ramonjd - [Draft]
• Hooks: add support for async filters and actions #64204 - @jsnajdr
• Patterns: add opt out preference to the 'Choose a Pattern' modal when adding a page #65026 - @ramonjd [Draft]
• Stabilize the PreSavePost and SavePost filters #64198 - @jsnajdr

Query Loop Updates
@ryanwelcher would you be able to help write a dev note for these changes?

• Set query loop to have the inherit value by default #63362
• Update Inherited Query Loop value from Template Settings changes #63358
• Move Posts Per Page, Offset, and Pages controls from the block toolbar into Inspector Controls #58207
• Query loop / Post template: Enable post format filter #64167
• Query Loop: Default to querying posts when on singular content #65067
• Query Loop Block: remove Posts List variation #63404 - @ellatrix

Consolidating and expanding block supports
@mumtahinafaguni Would you be able to draft a dev note that includes all these updates in one post? 🤔

• Buttons: Add border, color, and padding block supports #63538
• Categories List: Add border block support #63950
• Column: Enable border radius support #63924
• Comment Author Name: Add Border Support #64550
• Comment Content: Add Border Support #64230
• Comment Date: Add Border Support #64210
• Comment Template: Add Border Block Support #64238
• Comment Edit Link: Add Border Block Support #64239
• Comment Reply Link: Add border support #64271
• File: Add border block support #64509
• Gallery: Add border block support #63428
• Group: Add block support for shadow #63295
• Heading: Add border support #63539
• Image: Adopt margin block support #63546
• Latest comments: Add color block support #63419
• List: Add border support #63540
• List Item: Add border support #63541
• Media Text: Add border support #63542
• Paragraph: Add border support #63543
• Post Author Biography: Add Border Support #64615
• Post Author Name: Add Border Support #64530
• Post Author: Add Border Support #64599
• Post Comments Form: Add Border Block Support #64233
• Post content block: add background image and padding support  #62499
• Post Date: Add border block support #64023
• Post Excerpt: Add border block support #64022
• Post Terms: Add border block support #64246
• Post Title: Add border block support  #64024
• Preformatted: Add border block support  #64302
• Query Title: Add Border Support #64581
• Quote: Add spacing supports #63545
• Quote blocks: add background image and minimum height support #62497
• Search: Add margin support #63547
• Site Tagline: Add border block support  #63778
• Site Title: Add border block support  #63631
• Social Links: Add border block support  #63629
• Tag Cloud: Add border block support  #63579
• Term Description: Add border block support #63630
• Verse block: add background image and minimum height support #62498
• Add writing mode support to other blocks #62727

[talldan]

Add JSON Schema for .wp-env.json files

This one isn't a WordPress (core) API, so I personally don't think a dev note is the right choice (it isn't something that will be released via WordPress 6.7, it was already released as a change via the npm package update).

From the handbook it seems like dev notes are only for WordPress core releases - https://make.wordpress.org/core/handbook/tutorials/writing-developer-notes/.

[fabiankaegy]

Add JSON Schema for .wp-env.json files

This one isn't a WordPress (core) API, so I personally don't think a dev note is the right choice (it isn't something that will be released via WordPress 6.7, it was already released as a change via the npm package update).

From the handbook it seems like dev notes are only for WordPress core releases - https://make.wordpress.org/core/handbook/tutorials/writing-developer-notes/.

@talldan Fair point :)

In the past we published standalone posts for the schema. I do think it is something we should somehow inform users about. But it doesn't have to do with a specific release 👍

[talldan]

I think standalone posts are good. My understanding is the dev notes are all organized and linked from the general release literature that extenders will read through, so it's good to ensure it contains highly relevant items. There have been complaints in the past about important changes being buried in the details.

The TS changes might also qualify for something that doesn't need to be a dev note (if the public APIs haven't changed).

[youknowriad]

@fabiankaegy For the DataViews extensibility APIs, they are still plugin-only for now. So no need for dev notes for 5.7. We should try to gather more feedback and usage there.

[fabiankaegy]

@fabiankaegy For the DataViews extensibility APIs, they are still plugin-only for now. So no need for dev notes for 5.7. We should try to gather more feedback and usage there.

Thanks for confirming that Riad :) Will remove the section 👍

[matiasbenedetto]

• Adding Font size presets UI #63057 - @matiasbenedetto

I think this doesn't need a dev note. It is the implementation of a UI in the editor for an already existing feature in theme.json.

[fabiankaegy]

• Adding Font size presets UI #63057 - @matiasbenedetto

I think this doesn't need a dev note. It is the implementation of a UI in the editor for an already existing feature in theme.json.

@matiasbenedetto Happy to remove it. My rationale for adding it here was that I do think it is useful for developers to know about the existence of the new feature. Because it does allow the user to do more things with their theme that they weren't before.

It is an end user feature but I think developers should be aware of it.

[matiasbenedetto]

It is an end user feature but I think developers should be aware of it.

Gotcha 👍 , here it goes:

---

Font Size Presets UI

A new UI feature has been introduced in the Global Styles section of the editor, allowing users to add, edit, and remove font size presets.

A font size preset is a predefined font size that can be reused throughout the site via the font size picker. This enhancement provides a more user-friendly way to manage font size options, which were previously only accessible via the manual edition of theme.json file. Users can now modify preset names, base sizes, enable or disable the default fluid behavior, and customize the minimum and maximum values for fluid font size presets directly from the UI.

To access this interface, navigate to the Styles sidebar, then go to Typography → Font Sizes.