Add links to additional local dev tools in Block Development Environment readme #57682
Conversation
This file contains 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
ndiego
requested review from
ajitbohra,
ryanwelcher,
juanmaguitar and
fabiankaegy
as code owners
justintadlock
approved these changes
Jan 9, 2024
bph
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While
wp-envis the recommended tool in the Block Editor Handbook for local WordPress development environments, there are many other popular tools in the community, and there are developers who do not want to have to install Docker. This Twitter discussion is one example.In the Themes Handbook, we are noting a number of additional tools. Therefore, the purpose of this PR is to add a list of additional resources, while maintaining
wp-envas the recommended tool. This allows developers to choose the tool that works best for them while clarifying that you do not have to usewp-envif you prefer not to. We are also improving parity between the Themes Handbook and the Block Editor Handbook.