Update block categories based on categories proposed via the Style Book refresh Exploration#64080
Update block categories based on categories proposed via the Style Book refresh Exploration#64080
Conversation
|
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. |
| "apiVersion": 3, | ||
| "name": "core/post-date", | ||
| "title": "Date", | ||
| "category": "theme", |
There was a problem hiding this comment.
No, you're right. I misread the doc and renamed the theme category; undone as of the latest commit.
I'm still wondering what the best way is to introduce the concept of a subcategory. In the discussion, I raised the idea of using the keyword attribute, but I'm not sold yet.
a7c6563 to
b42d254
Compare
|
Superseded by #65430 |
|
Just saw this, thanks for starting it off. I was thinking something similar, but wasn't sure if changing block.json categories would be a breaking change. For example, if themes sorting core blocks by categories are expecting blocks to be in those categories. Might be an edge case. Creating a static list like #65430 does defer that decision at least. |

What?
This PR reorganizes block categories according to the new order proposed as a part of the Style Book refresh exploration — Issue: #53431
Why?
These changes align the block categories more closely with their functions and expected usage patterns. This reorganization aims to enhance the overall user experience by making block discovery more intuitive within the site editor.
How?
Testing Instructions
Testing Instructions for Keyboard