Docs: Move Glossary page to Getting Started. #54120
Merged
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
This was referenced Sep 1, 2023
ndiego
requested review from
gziolo,
ryanwelcher,
ajitbohra,
juanmaguitar and
fabiankaegy
as code owners
16 tasks
jorgefilipecosta
approved these changes
Sep 6, 2023
juanmaguitar
approved these changes
Sep 6, 2023
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.
What?
This PR aims to improve the developer experience by providing needed resources to the Getting Started section of the Block Editor Handbook. This is the second of two PRs, which moves the Glossary to Getting Started. The first PR moves the FAQ page to Getting Started.
Why?
While there is an argument that both of these pages could stay in the Explanations section, having them in the Gettings Started makes it easier for developers who are new to the Editor and blocks. It allows them easy access to fundamental terms and lets them review the answers to common questions they might have.
The corresponding redirect PRs in WordPress/wporg-developer are #274 and 273
Follow-up PRs will be created to improve the content of both pages once they are moved.