6.1 Dev Notes Tracking #42961

bph · 2022-08-04T08:08:55Z

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

Layout

Elements support @scruffian

Fluid typography @ramonjd

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

Create Block Scaffolding Tool @gziolo / @ryanwelcher

Style Engine @ramonjd @andrewserong

Block Library (Package)

Query Loop @ntsekouras

Components package

CustomSelectControl: Deprecate constrained width style #43230 @mirka

Margin deprecation @mirka (dev note here)

Popover @ciampo (dev note here)

New APIs

`useDisabled` hook + disabled component

Deprecated

Unsorted for now

theme.json

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

The text was updated successfully, but these errors were encountered:

ramonjd · 2022-08-04T21:54:22Z

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 · 2022-08-05T09:09:59Z

@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 · 2022-08-08T04:19:30Z

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 · 2022-08-09T13:45:56Z

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

bph · 2022-08-11T07:57:23Z

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

glendaviesnz · 2022-08-19T03:36:45Z

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

t-hamano · 2022-09-07T13:07:19Z

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 · 2022-09-07T13:39:22Z

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

scruffian · 2022-09-07T15:04:09Z

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

t-hamano · 2022-09-08T01:59:40Z

#42677 (comment)
I have left a comment about "the inheritance of template lock in the column block", as it was deemed necessary to include this as part of the dev note.

bph · 2022-09-13T19:04:42Z

@scruffian Thanks for the Dev Note! and the link!

oandregal · 2022-09-15T15:31:26Z

I've listed the authors of #43840 in the issue description. I was listed but I was involved.

ntsekouras · 2022-09-16T07:33:39Z

👋 - I was wondering if all the additions in the templates offered to create in site editor should be part of post like this already posted one: https://make.wordpress.org/core/2022/07/21/core-editor-improvement-deeper-customization-with-more-template-options/.

Related PRs that Needs Dev Note label was added are:

[Site Editor]: Re-architect templates addition #42457
[Site Editor]: Expand the template types that can be added - single custom post type and specific posts templates #41189
[FSE - Templates]: Add info to templates created from wp suggestion #41387

For Query Loop extensibility PRs, there is going to be a documentation page(related open PR), so I guess that would be enough? 🤔

Finally for the Query Loop parents filter is just a filter for the block to restrict the results based on their parent. I don't think it needs a separate dev note, but if we want we could add somewhere a sentence about it like:

Query Loop has now parent filtering support, with a new property in the existing query attribute, called parents. The filter is only shown for hierarchical post types and if you have selected multiple parents it will display the children of all of them(union).

gziolo · 2022-09-16T12:07:20Z

I started a draft post for Block API changes covering:

For the Create Block section, there is also an open PR that we should land closer to the release date that integrates the new render API from block.json and bumps the minimum required WordPress version to 6.1:

Create Block: Update templates to use APIs introduced in WP 6.1 #44185

Besides, we should mostly cover new CLI options / prompts that allow selecting different variants (dynamic vs static) and a way to scaffold code only for a block (without the plugin wrapper).

adamziel · 2022-09-20T02:37:39Z

@bph I've marked this one as done:

#41873

It was closed without merging as there wasn't enough alignment to move forward.

andrewserong · 2022-09-21T04:32:57Z

Layout: Use semantic classnames, centralize layout definitions, reduce duplication, and fix blockGap in theme.json #40875

I've added a draft note for the layout refactor in this comment (#40875 (comment)). The layout dev notes will likely all be consolidated with ones from @tellthemachines and @ramonjd into a single blog post, since lots of the individual PRs and changes are all related.

tellthemachines · 2022-09-21T06:57:01Z

Oh, I think we need to add #42763 (Try "constrained" content width as new layout type) and #42085 (Core CSS support for root padding and alignfull blocks) to this list. I'm writing dev notes for them, anyway 😅

bph · 2022-09-21T21:45:32Z

@tellthemachines I updated the tracking section above.

getdave · 2022-09-22T08:27:52Z

I added a dev note for pseudo class support for elements in theme.json. It's being tech reviewed by @scruffian and @draganescu.

afragen · 2022-09-22T21:30:59Z

Block Library: Add filter for inner blocks in the Navigation block

I added a short dev note for this.

https://make.wordpress.org/core/?p=98980&preview=1&_ppp=56c57f986f

tellthemachines · 2022-09-26T07:42:40Z

Hey folks, there's a draft post for all Layout-related dev notes here: https://make.wordpress.org/core/?p=99019&preview=1&_ppp=992173a9ba

ramonjd · 2022-09-27T02:10:08Z

I've thrown up a first draft for the Style Engine dev note here:

https://make.wordpress.org/core/?p=99063&preview=1&_ppp=10ef94cb0b

Thank you!

oandregal · 2022-10-04T10:37:53Z

I've noticed that in the 6.1 cycle there has been a few features introduced in theme.json. Some I've tracked (there may be more):

hover/focus/active states
spacing presets
fluid typography
new elements
filters

I suggest that we create a "theme.json in WordPress 6.1" devnote to compile them all (whether or not some of those individual features merit its own devnote as well).

cc people that led the changes in this area in case anyone wants to draft it up. @scruffian @MaggieCabrera @mikachan @ajlende @getdave @draganescu @glendaviesnz @andrewserong @ramonjd @aaronrobertshaw

getdave · 2022-10-04T13:20:12Z

hover/focus/active states

Here's the Dev Note for this.

bph · 2022-10-04T22:39:08Z

@oandregal looking at your list in your comment

This is the current list of stand-alone Dev Notes already drafted on the Make Blog:

Fluid Font Sizes
Styling Elements in Block Themes (@scruffian will expand a bit on the hover/focus/active states.)
Spacing Presets

This is the list of theme.json PRs. See link list above.

My idea would be to add "More Theme.json Updates" Dev Note covering the list and link to already existing Dev notes.

bph · 2022-10-04T22:48:23Z

@jorgefilipecosta @t-hamano We already have a "Block Library Updates" (public preview) Dev note in the works, where we can add a paragraph about these PRs
#42677
#43663

And if you can, also for #40554

What do you think? You can add it all in a comment on this issue together.

ryanwelcher · 2022-10-06T18:43:21Z

@bph combined dev note for the create-block stuff.

Create-Block Dev notes WP 6.1

#WordPress 6.1 introduces many updates and new features to the @wordpress/create-block.

New Features

Block Variants

The new –variant flag allows users of the tool to choose a block variant to be scaffolded. The internal templates provided by the create-block package support a dynamic and static variant with will scaffold a dynamic and static block respectively. If no variant is passed, the static variant is used.

Scaffolding using the dynamic variant:

npx @wordpress/create-block custom-block --variant=dynamic

Template authors can define variants by adding a variants object to the template definition with each property being the name of a variant and its value an object containing values that can add to or overwrite the default values defined in the defaultValues key. See the create-block-tutorial-template for an example of defining variants.

Related pull requests:

–no-plugin mode

A highly requested feature for the package was to be able to add additional blocks to an existing plugin. With the addition of the --no-plugin flag that is now possible!

When the command is run with the flag, a new set of block files will be created in the directory where the command was run in a directory named for the slug passed.

npx @wordpress/create-block custom-block --no-plugin

Related pull requests: #41642

Enhancements:

I18n references have been removed from the internal templates to avoid potential issues with translated strings causing block validation errors ( #43035 )
Improvements to the developer experience by prompting to continue the scaffolding process if the tool thinks system requirements are not met ( #42151, #42254 ) and some more general fixes to the scaffold to remove some warnings and errors ( #40479, #41273 ).
Adds support for the new render block.json key ( #44185 )

Documentation

The documentation around creating External Templates has been split into its own section ( #43718) and links to the documentation in the associated create-block-tutorial-template have been fixed to link to the correct places ( #42839 ).

@bph Make draft if here: https://make.wordpress.org/core/?p=99350&preview=1&_ppp=79a1db742d

ntsekouras · 2022-10-07T06:39:56Z

Extending the Query Loop block

Extenders needed a way to present bespoke versions of the Query Loop block, with their own presets, additional settings and without customization options which are irrelevant to their use-case. With WordPress 6.1 the Query Loop block offers very powerful ways to create such versions, through block variations.

To make Wordpress recognize your variation you need to set the isActive block variation property. For providing an easy and consistent way for extenders to recognize and scope their own variation a new namespace property has been introduced in Query Loop block.

Query Loop block now supports controlling which filters are displayed in the user through the allowedControls property, making it easier to be configured by users.

Now you have control over the query executed to fetch the desired posts. You can change the query executed in the block editor by setting extra arguments to the query attribute of the block, and you can do the same for the front end by using the query_loop_block_query_vars filter.

Customizing Query Block Layout

To customize your variation's layout you can use the innerBlocks attribute to set the blocks that are available at the start, bypassing the set-up stage. You can also create specific Query Loop variation patterns to be suggested in the setup, and replace flows of the block. To connect a pattern to a Query Loop variation, add the name of your variation prefixed with the Query Loop name (e.g. core/query/$variation_name) to the pattern’s blockTypes property.

An example block variation would look like this:

const MY_VARIATION_NAME = 'my-plugin/books-list';

registerBlockVariation( 'core/query', {
    name: MY_VARIATION_NAME,
    title: 'Books List',
    description: 'Displays a list of books',
    isActive: [ 'namespace' ],
    icon: /** An SVG icon can go here*/,
    attributes: {
        namespace: MY_VARIATION_NAME,
        query: {
            perPage: 6,
            pages: 0,
            offset: 0,
            postType: 'book',
            order: 'desc',
            orderBy: 'date',
            author: '',
            search: '',
            exclude: [],
            sticky: '',
            inherit: false,
        },
    },
    allowedControls: [ 'inherit', 'order', 'taxQuery', 'search' ],
    scope: [ 'inserter' ],
);

There is a new documentation page specifically for extending Query Loop block to learn more.

props @sunyatasattva for the documentation page.

make.wordpress draft: https://make.wordpress.org/core/?p=99476&preview=1&_ppp=c35ff058a0

oandregal · 2022-10-07T09:03:29Z

@bph I've looked into changes and don't see anything left. People that worked actively in this area may want to double-check, cc @scruffian @ajlende @MaggieCabrera etc.

t-hamano · 2022-10-07T13:26:05Z

@bph

I will leave a note which should be added in the Block Libraries update in WordPress 6.1 post.

This note refers to three PRs:

Column Block: enable global template_lock inheritance #42677: @t-hamano, @jorgefilipecosta
Cover Block: Keep the inner contents in a physical direction even in RTL languages #43663: @t-hamano, @aaronrobertshaw
Cover block: fix duotone when background is set to fixed #40554: @matiasbenedetto, @ajlende

If there are any misleading or unnatural phrases, please feel free to update them.

Navigation Block Menu Items filter

Content has already been created by @afragen.

Improvement of Cover Block

Markup changes

The markup has been changed to resolve the issue that duotone doesn't work with fixed background. Previously, the background image was applied to the root of the block, but it is now applied to the inner div with the img role and .wp-block-cover__image-background class.

Current:

<div class="wp-duotone-xxxxxx-xxxxxx-x wp-block-cover has-parallax" style="background-image:url(http://example.com/wp-content/uploads/2022/10/cover.jpg)">
	<span aria-hidden="true" class="wp-block-cover__background has-background-dim"></span>
	<div class="wp-block-cover__inner-container">
		<p>Inner Contents</pss=>
	</div>
</div>

New:

<div class="wp-duotone-xxxxxx-xxxxxx-x wp-block-cover has-parallax">
	<span aria-hidden="true" class="wp-block-cover__background has-background-dim"></span>
	<div role="img" class="wp-block-cover__image-background wp-image-xx has-parallax" style="background-image:url(http://example.com/wp-content/uploads/2022/09/cover.jpg)"></div>
	<div class="wp-block-cover__inner-container">
		<p>Inner Contents</p>
	</div>
</div>

For more info see #40554.

Keep the same position for both LTR and RTL languages

In the cover block, the content inside can be changed the content position, such as "Top Left" or "Center Right". But when changed to RTL languages, the content position flips left to right as compared to the LTR language. However, content position determines "physical" placement and should not be affected by language direction.

To solve this problem, the same position is now kept for both LTR and RTL languages. Because of this change, the content within the existing cover block in RTL languages is flipped left to right (i.e., in its original position), but if this is not what you are looking for, you can re-position it.

For more info see #43663.

Global template_lock inheritance in the column block

The block template defines a default list of blocks in an editor session. To prevent manipulation of the block list, all blocks can be locked by template_lock property.

However, in column blocks, the editor would crash on certain operations because it would initialize the lock status defined in the block template. To resolve this issue and to be more consistent about template lock status inheritance, column blocks now inherit the lock status of block templates.

For more info see #42677.

bph · 2022-10-07T15:50:10Z

Awesome, Thank you @t-hamano !

zzap · 2022-10-07T15:59:18Z

Just to let everyone know, I've been going through the drafts at Core blog and adding 6.1 label to a bunch of dev notes. That is the most important label for the release so please use it if.

Thank you for awesome work ❤️

bph · 2022-10-07T16:02:38Z

I have been doing that, to and I added dev-note-6.1 so we can collectively just refer to them in one tag. :-)

zzap · 2022-10-07T16:21:53Z

Yeah, but 6.1 + dev-notes are the ones that end up in here https://make.wordpress.org/core/6-1/

bph · 2022-10-08T15:24:55Z

Update: October 8th, 2022

Yesterday, 4 dev notes were published, six are finished and in the queue to be reviewed, one is still in progress.

Published 📣

In Review 👓

In Progress 📝

Block API changes in WordPress 6.1

Not claimed PRs

In the list in the issue description above we still have a few white check boxes next to PRs.

Please double-check if there are still dev notes that need to be created.
If you feel they are worth a mention but don't value a stand-alone Dev note, maybe you can write a one paragraph blurb as to the nature of the change(s) and put it in a comment on this issue.
If you feel it's worth a mention but only in the "But wait there is more" section of the Field guide (example 6.0), please note that too.

ramonjd · 2022-10-08T20:52:49Z

@bph Could we possibly hold off on publishing the fluid typography dev note for a few days? There are some bugs we're scrambling to iron out and it will affect the content of the dev note, which I will update in due course. See:

Fluid typography: custom font sizes should be converted to fluid font sizes values #44758

🙇

talldan · 2022-10-10T07:37:55Z

Persisted preferences - https://make.wordpress.org/core/wp-admin/post.php?post=99657&action=edit

Writing this did make me realise there's a bug in 6.1 RC related to the backport for persisted preferences, so I'll work on fixing that asap. 🤦‍♂️

oandregal · 2022-10-10T08:37:58Z

Oh, I forgot commenting about the settings hook. This is something client-specific and unrelated to server-side filters. It's about having a theme.json per block instance. Not all pieces to make this work have landed in 6.1, so I'm leaning towards not publishing the devnote just for now. cc @jorgefilipecosta in case he has thoughts.

jorgefilipecosta · 2022-10-10T10:20:14Z

Oh, I forgot commenting about the settings hook. This is something client-specific and unrelated to server-side filters. It's about having a theme.json per block instance. Not all pieces to make this work have landed in 6.1, so I'm leaning towards not publishing the devnote just for now. cc @jorgefilipecosta in case he has thoughts.

Yes, I agree it is something experimental that we will continue trying on the plugin. The dev note should not go out for now.

tyxla · 2022-10-10T12:09:07Z

@bph I've added a dev note for #44494 as a comment in the PR: #44494 (comment).

Mamaduka · 2022-10-10T13:04:36Z

I've added two dev notes for Block Editor misc post - #40502 (comment) and #42186 (comment).

bph · 2022-10-10T16:16:58Z

Thank You @tyxla and @Mamaduka for your notes! 😸

jorgefilipecosta · 2022-10-11T18:05:43Z

Here I add the missing dev note for #41791.
It can be included on a misc editor dev note.

Start content patterns for all post types.

With WordPress 6.0, we introduced the ability to add patterns that appear in a modal each time a new page was created, allowing the user to start from a set of pre-made patterns instead of in a blank state. In WordPress 6.1, this feature is expanded to all the post types.
To use this feature, one should include 'core/post-content' in the blockTypes array (same as what happened for pages) and include the desired postTypes where the modal should appear in a newly introduced postTypes property. If postTypes are specified, the pattern is only available on the post types that were set.
Example:

register_block_pattern( 'custom-pattern', array(
			'title'      => _x( 'Start post pattern', 'Block pattern title', 'gutenberg' ),
			'blockTypes' => array( 'core/paragraph', 'core/post-content' ),
			'postTypes' => array( 'product' ),
			'content'    => '<!-- wp:paragraph -->
<p>A start post pattern</p>
<!-- /wp:paragraph -->',
		) );

bph · 2022-10-26T22:46:19Z

20 post published

This is definitely more than 5.9 (9) and 6.0 (9) together. :-) 🙌 🤯

👏 props to @scruffian @glendaviesnz @ramonjd @oandregal @draganescu @jorgefilipecosta @tellthemachines @scruffian @getdave @andrewserong @fabiankaegy @Mamaduka @annezazu @afragen @t-hamano @ellatrix @adamziel @gziolo @ciampo @mirka @aaronrobertshaw @talldan @ramonjd @ntsekouras @ryanwelcher @mburridge and Abha Thakor.

I close this issue, but if you find PRs that still need to have a mention in the Field Guide 6.1 by all means comment below and ping me.

r-interactive · 2024-06-07T20:58:14Z

Extending the Query Loop block

Extenders needed a way to present bespoke versions of the Query Loop block, with their own presets, additional settings and without customization options which are irrelevant to their use-case. With WordPress 6.1 the Query Loop block offers very powerful ways to create such versions, through block variations.

To make Wordpress recognize your variation you need to set the isActive block variation property. For providing an easy and consistent way for extenders to recognize and scope their own variation a new namespace property has been introduced in Query Loop block.

Query Loop block now supports controlling which filters are displayed in the user through the allowedControls property, making it easier to be configured by users.

Now you have control over the query executed to fetch the desired posts. You can change the query executed in the block editor by setting extra arguments to the query attribute of the block, and you can do the same for the front end by using the query_loop_block_query_vars filter.

Customizing Query Block Layout

To customize your variation's layout you can use the innerBlocks attribute to set the blocks that are available at the start, bypassing the set-up stage. You can also create specific Query Loop variation patterns to be suggested in the setup, and replace flows of the block. To connect a pattern to a Query Loop variation, add the name of your variation prefixed with the Query Loop name (e.g. core/query/$variation_name) to the pattern’s blockTypes property.

An example block variation would look like this:
const MY_VARIATION_NAME = 'my-plugin/books-list';

registerBlockVariation( 'core/query', {
    name: MY_VARIATION_NAME,
    title: 'Books List',
    description: 'Displays a list of books',
    isActive: [ 'namespace' ],
    icon: /** An SVG icon can go here*/,
    attributes: {
        namespace: MY_VARIATION_NAME,
        query: {
            perPage: 6,
            pages: 0,
            offset: 0,
            postType: 'book',
            order: 'desc',
            orderBy: 'date',
            author: '',
            search: '',
            exclude: [],
            sticky: '',
            inherit: false,
        },
    },
    allowedControls: [ 'inherit', 'order', 'taxQuery', 'search' ],
    scope: [ 'inserter' ],
);
There is a new documentation page specifically for extending Query Loop block to learn more.

props @sunyatasattva for the documentation page.

make.wordpress draft: https://make.wordpress.org/core/?p=99476&preview=1&_ppp=c35ff058a0

I have questions about ‘connecting’ a pattern with a Query Loop variation, mentioned in the section “Customize your variation layout”:

“In order for a pattern to be “connected” with a Query Loop variation, you should add the name of your variation prefixed with the Query Loop name (e.g. core/query/$variation_name) to the pattern’s blockTypes property. For more details about registering patterns see here.”

I don’t quite understand, and it’s not working for me. It will be great if there’s a simple example on how to connect a pattern with a query loop variation.

I do have the variation created in the js file, using registerBlockVariation(), similar to the examples that you have above. My variation name is 'my-test-variation'

const MY_VARIATION_NAME = 'my-test-variation';

registerBlockVariation(
  'core/query',
  {
    name: MY_VARIATION_NAME,
    title: 'Books List',
    description: 'Displays a list of books',
    isActive: [ 'namespace' ],
    icon: 'book-alt',
    attributes: {
        namespace: MY_VARIATION_NAME,
        query: {
            perPage: 6,
            pages: 0,
            offset: 0,
            postType: 'book',
            order: 'desc',
            orderBy: 'date',
            author: '',
            search: '',
            exclude: [],
            sticky: '',
            inherit: false,
        },
    },
    allowedControls: [ 'inherit', 'order', 'taxQuery', 'search' ],
    scope: [ 'inserter','block' ],
  }
);

I have registered a pattern using register_block_pattern() in my functions.php, like below:

register_block_pattern(
    'test/posts-1-col',
    array(
        'title'      => __( 'My Test Pattern', 'my-plugin' ),
        'blockTypes' => array( 'core/query/my-test-variation' ),
        'content'    => '<!-- wp:query {"query":{"pages":0,"offset":0,"postType":"post","order":"desc","orderBy":"date","author":"","search":"","exclude":[],"sticky":"","inherit":true},"layout":{"type":"default"}} -->
<div class="wp-block-query">
  <!-- wp:post-template -->

  <!-- wp:group {"tagName":"article","style":{"spacing":{"padding":{"top":"var:preset|spacing|small","bottom":"var:preset|spacing|small"},"blockGap":"1.5rem"}},"layout":{"type":"default"}} -->
  <article class="wp-block-group" style="padding-top:var(--wp--preset--spacing--small);padding-bottom:var(--wp--preset--spacing--small)">
    <!-- wp:post-title {"isLink":true} /-->
    <!-- wp:post-excerpt /-->
  </article>
  <!-- /wp:group -->
  <!-- /wp:post-template -->


  <!-- wp:query-pagination {"paginationArrow":"arrow","layout":{"type":"flex","justifyContent":"center"}} -->
    <!-- wp:query-pagination-numbers /-->
  <!-- /wp:query-pagination -->

  <!-- wp:query-no-results -->
    <!-- wp:pattern {"slug":"spruce/hidden-no-results"} /-->
  <!-- /wp:query-no-results -->
</div>
<!-- /wp:query -->',
    )
);

What am I missing?

Thank you!

bph self-assigned this Aug 4, 2022

zzap mentioned this issue Aug 17, 2022

WordPress 6.1 release docs contributors WordPress/Documentation-Issue-Tracker#413

Closed

t-hamano mentioned this issue Sep 7, 2022

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

Merged

bph mentioned this issue Sep 13, 2022

Block-based template parts for Classic themes #42729

Merged

bph added the [Status] In Progress Tracking issues with work in progress label Sep 14, 2022

bph mentioned this issue Oct 4, 2022

Column Block: enable global template_lock inheritance #42677

Merged

bph added this to WP 6.1 Documentation Oct 7, 2022

bph moved this to In Progress in WP 6.1 Documentation Oct 7, 2022

bph mentioned this issue Oct 11, 2022

Add: Ability to use creation patterns for other post types besides page #41791

Merged

bph removed the [Status] In Progress Tracking issues with work in progress label Oct 18, 2022

bph closed this as completed Oct 26, 2022

Repository owner moved this from In Progress to Done in WP 6.1 Documentation Oct 26, 2022

6.1 Dev Notes Tracking #42961

6.1 Dev Notes Tracking #42961

Comments

bph commented Aug 4, 2022 • edited Loading

Tracking all Dev Notes from Gutenberg plugin releases 13.1 - 14.1

Stand-alone post

Part of a group post

Global Styles

Layout

Elements support @scruffian

Fluid typography @ramonjd

Create Block Scaffolding Tool @gziolo / @ryanwelcher

Style Engine @ramonjd @andrewserong

Block Library (Package)

Query Loop @ntsekouras

Components package

Margin deprecation @mirka (dev note here)

Popover @ciampo (dev note here)

New APIs

useDisabled hook + disabled component

Deprecated

Unsorted for now

theme.json

Preference Persistence

ramonjd commented Aug 4, 2022

bph commented Aug 5, 2022

andrewserong commented Aug 8, 2022

bph commented Aug 9, 2022 • edited Loading

bph commented Aug 11, 2022

glendaviesnz commented Aug 19, 2022

t-hamano commented Sep 7, 2022

bph commented Sep 7, 2022

scruffian commented Sep 7, 2022

t-hamano commented Sep 8, 2022

bph commented Sep 13, 2022

oandregal commented Sep 15, 2022

ntsekouras commented Sep 16, 2022

gziolo commented Sep 16, 2022 • edited Loading

adamziel commented Sep 20, 2022

andrewserong commented Sep 21, 2022

tellthemachines commented Sep 21, 2022

bph commented Sep 21, 2022

getdave commented Sep 22, 2022 • edited Loading

afragen commented Sep 22, 2022 • edited Loading

tellthemachines commented Sep 26, 2022 • edited Loading

ramonjd commented Sep 27, 2022

oandregal commented Oct 4, 2022 • edited Loading

getdave commented Oct 4, 2022

bph commented Oct 4, 2022

bph commented Oct 4, 2022

ryanwelcher commented Oct 6, 2022 • edited Loading

Create-Block Dev notes WP 6.1

New Features

Block Variants

–no-plugin mode

Enhancements:

Documentation

ntsekouras commented Oct 7, 2022 • edited Loading

Extending the Query Loop block

Customizing Query Block Layout

oandregal commented Oct 7, 2022

t-hamano commented Oct 7, 2022

Navigation Block Menu Items filter

Improvement of Cover Block

Markup changes

Keep the same position for both LTR and RTL languages

Global template_lock inheritance in the column block

bph commented Oct 7, 2022

zzap commented Oct 7, 2022

bph commented Oct 7, 2022

zzap commented Oct 7, 2022

bph commented Oct 8, 2022 • edited Loading

Update: October 8th, 2022

Published 📣

In Review 👓

In Progress 📝

Not claimed PRs

ramonjd commented Oct 8, 2022

talldan commented Oct 10, 2022

oandregal commented Oct 10, 2022

bph commented Aug 4, 2022 •

edited

Loading

`useDisabled` hook + disabled component

bph commented Aug 9, 2022 •

edited

Loading

gziolo commented Sep 16, 2022 •

edited

Loading

getdave commented Sep 22, 2022 •

edited

Loading

afragen commented Sep 22, 2022 •

edited

Loading

tellthemachines commented Sep 26, 2022 •

edited

Loading

oandregal commented Oct 4, 2022 •

edited

Loading

ryanwelcher commented Oct 6, 2022 •

edited

Loading

ntsekouras commented Oct 7, 2022 •

edited

Loading

bph commented Oct 8, 2022 •

edited

Loading

jorgefilipecosta commented Oct 11, 2022 •

edited by getdave

Loading

r-interactive commented Jun 7, 2024 •

edited

Loading