6.1 Dev Notes Tracking

[bph]

Tracking all Dev Notes from Gutenberg plugin releases 13.1 - 14.1

After a review of the processes establish during 6.0 release cycle, the release leads for documentation agreed on some modifications. Please read the information below carefully. If you have questions, connect with @bph or @zzap 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.
During the course of the next few weeks, this first list will be completed after the last Gutenberg plugin.
We can already make decision on some features if warrant 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 receive privileges on the Make Core Blog. (Please connect with @bph or @zzap, if you need access)

• 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.
• 🗓 Deadline Extended: Sunday October 9th, 2022

---

• Block-based template parts for Classic themes #42729 @fabiankaegy (draft on Google Doc)

Global Styles

• Make global styles data filterable #44015 @oandregal
• Global Styles: Re-add third party blocks #44018 @scruffian (if ported back to 14.1)
• Block CSS: Move CSS from the stylesheet to the block definition #41689 @scruffian
• Update hook's names from global_styles_* to theme_json_* #44159 @oandregal
• Add settings hook #40547 @oandregal

Layout

• Layout: Add a disable-layout-styles theme supports flag to opt out of all layout styles #42544 @andrewserong (partial devnote)
• Theme.json: Add spacing size presets #41527 @glendaviesnz draft link below
• Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875 @tellthemachines
• Try "constrained" content width as new layout type #42763 @tellthemachines
• Core CSS support for root padding and alignfull blocks #42085 @tellthemachines
• Layout: Move generation of util classes to existing method to avoid adding global public method WP #41885 - covered under Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875
• Add utility classnames back to blocks that have layout attributes specified #41487 - also covered under Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875?
• Layout: Add default fallback gap value in block.json, and set to 2em for Columns blocks #41098

Elements support @scruffian

• Global Styles: Add support for heading elements #41981
• Elements: Button - Fix element selectors #41822
• Elements: Add UI for button elements #41659
• Add support for button elements to theme.json #40260
• Global Styles: Add support for caption elements #41140
• Support pseudo selectors on elements in theme json #41786
• Pseudo elements supports on button elements #43088 @getdave @MaggieCabrera
• Elements: Add an API make it easier to get class names #41753

Fluid typography @ramonjd

• Block supports: add fluid typography #39529 (Public Preview on Make Core Blog)

Create Block Scaffolding Tool @gziolo / @ryanwelcher

• Create Block: Fix warnings and errors reported during scaffolding and validation #40479
• [create-block] Split documentation into two sections #43718
• Create Block: Refactor handling for template variants #43481
• Create Block: Remove i18n references from save properties #43035
• Create Block: update document links in templates #42839
• Create Block: More careful prompts to continue when minimum system requirements are not met #42254
• Create Block: Added prompt to continue when minimum system requirements not met #42151
• [Create Block] Adding a --no-plugin flag to scaffold only block files. #41642
• Create Block: Improve block templates #41273
• [Create-block] Add --variant flag to allow creation of different block type variants #41289
• [x ] Create Block: Update templates to use APIs introduced in WP 6.1 #44185 (merged for GB 14.5 - after 6.1 )

Style Engine @ramonjd @andrewserong

• Add initial version of the style engine #37978
• Style engine: pre-core migration documentation and house keeping #43840
• Style Engine: block supports backend #39446
• Style engine: move backend scripts to package #39736
• Style Engine: add margin support to frontend #39790
• Style engine: add border to frontend #41803
• Style Engine: add typography and color to backend  #40332
• Style Engine: add typography and color to frontend #40665
• Style engine: enqueue block support styles #42452
• Style Engine: add border to backend #40531

Block Library (Package)

• Block Library: Add filter for inner blocks in the Navigation block #37998 @afragen
• Cover block: fix duotone when background is set to fixed #40554 @matiasbenedetto / @youknowriad
• Use page list instead of placeholder as fallback #42735 @draganescu / @getdave
• Navigation: Move block CSS to JSON #41898
• Block CSS: Move CSS from the stylesheet to the block definition #41689
• Cover Block: Keep the inner contents in a physical direction even in RTL languages #43663 @t-hamano
• Column Block: enable global template_lock inheritance #42677 @t-hamano

Query Loop @ntsekouras

• [Block Library - Query Loop]: Add allowedControls in block variations for better extensibility #43632
• [Block Library - Query Loop]: Add parents filter #40933

Components package

• CustomSelectControl: Deprecate constrained width style #43230 @mirka

Margin deprecation @mirka (dev note here)

• (Custom)GradientPicker: Remove and deprecate outer margins #43436
• AnglePickerControl: Deprecate margin bottom #43867
• FontSizePicker: Deprecate bottom margin #43870

Popover @ciampo (dev note here)

• Popover: add anchor prop #43691 @ciampo
• Popover: stabilize __unstableShift prop to shift #43845 @ciampo
• Refactor popover to use separate flip and resize props instead of forcePosition #43546 @ciampo
• Popover: enable auto-updating every animation frame #43617 @ciampo

New APIs

• Add a filter to build_query_vars_from_query_block #43590 @sunyatasattva
• Stabilize the useResourcePermissions hook #43268 @adamziel
• Blocks: Add new render field to block.json #42430 @gziolo
• Block Library: Make it possible to import individual blocks #42258 @gziolo

useDisabled hook + disabled component

• Make the useDisabled hook stable #40890 @youknowriad
• Improve the useDisabled hook and Disabled component #40631 @youknowriad

Deprecated

• Block Editor: Deprecate 'BlockColorsStyleSelector' component #40502
• Blocks: officially deprecated the children and node matchers #44265

Unsorted for now

• Update templateLock value from noContent to contentOnly #44131
• [Site Editor]: Re-architect templates addition #42457
• Placeholder: Add an illustration option to the Placeholder component #41605
• useSelect: improve transition from async to sync mode #40680
• Testing: Remove enzyme completely #44494 @tyxla
• Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875
• Add ability to unset duotone in themes with default duotone set #39564

theme.json

• Add ability to unset duotone in themes with default duotone set #39564
• [Blocks] Paragraph and Heading: add gradient support #43119
• Pseudo elements supports on button elements #43088
• Theme.json: Add support for heading / caption elements in theme.json schema #42433
• Theme.json: Fix schema for button elements #42431
• Adds text decoration support to post title block #42328
• Theme.json Schema: add support for button elements #42133
• Add visited to link element allowed pseudo selector list #42096
• Update Theme JSON $schema to account for pseudo selector support #41936
• Global Styles: Allow references to values in other locations in the tree #41696
• Theme.json: Add spacing size presets #41527
• File, Search Blocks: Lower CSS specificity  #41393
• Gallery: Opt-in to axial (column/row) block spacing controls #41175

Preference Persistence

• Add new preferences persistence API, and save editor preferences in user meta #39795 @talldan

---

Update 10/8
removed - #42485 not in 6.1

Updates: 10/03 - bph
several more PR references

Updates: 9/21 / - bph

• Added Style Engine PRs
• delete Move block css from supports > __experimentalStyle to a top level style key in block.json #41873 per Adams comment below

to be continued

[ramonjd]

Fluid typography @ramonjd

Thanks @bph! I have a dev note ready to roll, but have shelved it until we're closer to RC1. I am told this is the usual protocol.

[bph]

@ramonjd and all

Publishing close to RC 1 is not a hard rule. It only makes sure that there isn't something in the dev notes, the might have changed between drafting it and release.

On the doc release team we need a bit of a lead time as Dev Notes need to be reviewed by two people before publishing. If all dev notes are published a day before RC 1, it creates an unnecessary bottleneck and undue stress on the team.

Ideally, the draft on the make blog could be available around Beta 1. Then it can get into the queue for reviewers, finalized and published by RC 1, to make it into the Field Guide.

[andrewserong]

Thanks for the ping @bph!

• Layout: Add a disable-layout-styles theme supports flag to opt out of all layout styles #42544 @andrewserong

For this one, I don't believe a separate post is required, it can be added to any dev note blog post on smaller changes. I've drafted a comment on the PR for inclusion in such a post: #42544 (comment) — the main purpose of the dev note is to communicate to creators of themes that currently use an undocumented approach of opting out of Layout styles to use the new formal approach.

[bph]

Thank you, @andrewserong - I marked this dev note as done for now.

[bph]

Thanks @ramonjd for message about the Draft Dev Note ready for review 👏  🙌

[glendaviesnz]

Draft for spacing presets available for review at https://make.wordpress.org/core/?p=98177&preview=1&_ppp=00c8d7730a

[t-hamano]

• Cover Block: Keep the inner contents in a physical direction even in RTL languages #43663

I commented on the above PR because I thought it should be mentioned in the dev note.
In my opinion, it is better to include it as part of the group post, such as Block Editor miscellaneous Dev Notes for WordPress 6.0.

[bph]

Thank you so much @t-hamano to add this here and put this on our radar for WP 6.1.

[scruffian]

@bph I created a draft for elements support: https://make.wordpress.org/core/?p=98557