Clarify block name immutability and namespace best practices [docs]#71040
Merged
Mamaduka merged 1 commit intoWordPress:trunkfrom Aug 5, 2025
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. |
|
Thanks @dhananjaykuber this looks great. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #71022
What?
Updates the Block Name documentation to clarify that block names are immutable and provides improved guidance on namespace selection.
Why?
The current documentation doesn't emphasize that block names cannot be changed after deployment, which can lead to serious issues for developers who need to rename blocks later. Block names are stored in post content as HTML comments, making changes require manual post editing or database scripts. Additionally, many developers use generic namespaces like
create-block/*without understanding the long-term implications.How?
registerBlockCollection()limitation to single namespaces