Add heading level curation documentation #66076
Conversation
ndiego
requested review from
ajitbohra,
juanmaguitar and
fabiankaegy
as code owners
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
| @@ -6,6 +6,37 @@ This page is dedicated to the many ways you can disable specific functionality i | |||
|
|
|||
| There might be times when you don’t want access to a block at all to be available for users. To control what’s available in the inserter, you can take two approaches: [an allow list](/docs/reference-guides/filters/block-filters.md#using-an-allow-list) that disables all blocks except those on the list or a [deny list that unregisters specific blocks](/docs/reference-guides/filters/block-filters.md#using-a-deny-list). | |||
|
|
|||
| ## Curate heading levels | |||
There was a problem hiding this comment.
I wonder if it's the right place for this documentation. It might be but I feel there's a lot of similar APIs that we need to surface in a consistent way (together). "allowedBlocks" attribute, "templateLock" attribute, "placeholder" attribute. (Attributes that "control" the behavior of blocks but not their output)
There was a problem hiding this comment.
It might be but I feel there's a lot of similar APIs that we need to surface in a consistent way (together).
💯 these attributes are not documented well. I'll add this to my to-do list.
* Add heading level curation documentation. Co-authored-by: ndiego <ndiego@git.wordpress.org> Co-authored-by: ryanwelcher <welcher@git.wordpress.org>
* Add heading level curation documentation. Co-authored-by: ndiego <ndiego@git.wordpress.org> Co-authored-by: ryanwelcher <welcher@git.wordpress.org>
Fixes #65706
What?
This PR updates the Curating the Editor docs with reference to the heading level curation method that is now available in Gutenberg and will soon be included in WordPress 6.7.
Why?
While this will be detailed in a dev note, having this information in the Curating the Editor documentation makes it more discoverable.