6.3 Dev Note Tracking Issue

[Leonardus-Nugraha]

Tracking all Dev Notes from Gutenberg plugin releases 15.2 - 16.1

Please read the information below carefully. If you have questions, connect with @Leonardus-Nugraha or @stevenlinx via Slack or comment here.

Not all developer-related information needs to be in a separate DevNote on the Make Core blog for the field guide. We can group related information. We can already make decisions on some features if it warrants a stand-alone blog post or if the information will be part of 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. If you need access to write on the Blog, connect with @hellofromtonya or @abhansnuk via Slack or comment here.

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](https://make.wordpress.org/core/handbook/tutorials/writing-developer-notes/))

## 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](https://make.wordpress.org/core/handbook/tutorials/writing-developer-notes/) - ⭐️ [Style & Substance section](https://make.wordpress.org/core/handbook/best-practices/post-comment-guidelines/#style-and-substance) of the Post & Comment Guidelines for Make Blog - ⭐️ [Documentation Style Guide](https://make.wordpress.org/docs/style-guide/) - Good for reference, when in doubt, especially when English is not your native language.

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:
needs dev note and 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

---

Standalone dev notes:

Command Palette API

• Marks the commands APIs as public #50691 @youknowriad
• Marks the selectors and actions of the commands store as a public API #51169 @youknowriad

Block Selectors API

• Block.json: Refactor and stabilize selectors API #46496 @aaronrobertshaw

Layout-related updates

• Try reducing specificity of layout margin rules #47858 @tellthemachines
• Add compound class to layout wrapper for global spacing styles #47952 @tellthemachines
• Add block spacing and layout to Post Template  #49050 @tellthemachines
• Get orientation for Spacer block from parent layout #49322 @tellthemachines
• Try stabilising layout and its associated APIs #51434 @tellthemachines
• Layout: Move layout definitions out of theme.json #50621 @andrewserong

Social Icons

• Social Links block: Add color classes so icon colors correctly reflect changes in Global Styles  #51020 @ndiego

Miscellaneous dev notes:

• Introduce new PluginTemplateSettingPanel slot #50257 @ntsekouras
• Allow dragging-and-dropping images from the inserter to image blocks #49673 @kevin940726
• Publish types for plugins package #49649 @noahtallen
• Post editor: iframe if all blocks are v3 #48286 @ellatrix
• Block editor: iframe: add enqueue_block_assets #49655 @ellatrix
• Post editor: revert iframed editor for WP core only #48076 @ellatrix
• Remove unwrap from transforms and add ungroup to more blocks #50385 @ntsekouras
• Add block variations transformation in block switcher #50139 @ntsekouras
• Add new API to allow inserter items to be prioritised #50510 @scruffian

To Do

Editor

• List View: Add a rootClientId prop #49475 @scruffian
• Reusable blocks: Rename to 'Patterns' and add option to also add a non-synced Pattern #51144 @glendaviesnz

Blocks

• Add ability to prevent editing blocks using useBlockEditingMode() #50643 @noisysocks

Patterns

• Add: Patterns to the template start modal. #47322 @jorgefilipecosta

Data

• Data: refuse to register an already registered store #49134 @jsnajdr

[noahtallen]

The dev note I added under #49649 doesn't just apply to plugins, but it's a small enough change that I don't think it needs a separate post.

[kevin940726]

Added dev note in #49673 (comment) for the relevant part of the PR. LMK if there's anything else I should include! 🙇

[noisysocks]

#50643 @noisysocks

Decided to not make this API public for 6.3 so no dev note required yet.

[tellthemachines]

Dev notes for layout-related work:

layout stabilisation
spacer block orientation
post template layout and spacing
compound layout class
reduced specificity layout rules

Edit: added layout definitions dev note.

(These could all go together in one layout-related post)

[tellthemachines]

Ready for review

The draft post that groups all layout-related dev notes from the comment above: https://make.wordpress.org/core/?p=106122&preview=1&_ppp=f90c033a3b

[ellatrix]

Proposed Dev Note for the iframe PRs:

https://make.wordpress.org/core/?p=106178&preview=1&_ppp=c7bb7ce20d

Post Editor Iframed

From WordPress 6.3, the post editor will be iframed if all registered blocks have a Block API version 3 or higher. Adding version 3 support means that the block should work inside an iframe, though the block may still be rendered outside the iframe if not all blocks support version 3.

It is worth noting that the Site Editor and Page Template Editor have always been iframed, alongside block and pattern previews, and will continue to be iframed regardless of the Block API version.

In order to make adoption easier, all assets (styles and scripts) added through the enqueue_block_assets PHP action will now also be enqueued for the iframe. See this PR.

Please try to make your blocks compatible, and let me know if you run into any problems or have suggestions. In a future version of WordPress, the editor content will load within an iframe regardless of the Block API version.

For more information about why we are iframing the editor content, see:

https://make.wordpress.org/core/2021/06/29/blocks-in-an-iframed-template-editor/ [embed]

[aaronrobertshaw]

Proposed dev note for the Block Selectors API:

https://make.wordpress.org/core/?p=106203&preview=1&_ppp=8dda7565b7

Unfortunately, I'll be AFK for a little over a week so might need someone to pick this up to address any feedback 🙏

[Leonardus-Nugraha]

Thanks @ellatrix , @aaronrobertshaw , @noahtallen , @kevin940726 , and @tellthemachines. I've reviewed the dev notes drafts, and they're up for final checking by @bph before publishing.

I'd also remind everyone that we still need dev notes for the following PRs. Can they be delivered this Friday, if possible?
#48076 @ellatrix
#49475 @scruffian
#49655 @ellatrix
#50257 @ntsekouras
#51144 @glendaviesnz
#50139 @ntsekouras
#50385 @ntsekouras
#51020 @ndiego
#47322 @jorgefilipecosta
#50621 @andrewserong
#50510 @scruffian
#50691 @youknowriad
#51169 @youknowriad
#49134 @jsnajdr