docs(editor): sidebar navigation reorganization#659
Open
lancesnider wants to merge 15 commits intomainfrom
Open
docs(editor): sidebar navigation reorganization#659lancesnider wants to merge 15 commits intomainfrom
lancesnider wants to merge 15 commits intomainfrom
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
RobertHaynie
previously approved these changes
May 8, 2026
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
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.
Note: This PR is about structure, not content. If I did change content, it was as little as possible to support the new structure.
Before/After:
The goal of this PR is to:
Stuff I'm not 100% sure about
Layoutsparent category toResponsive Design. Pushback welcome.Hierarchical Relationships, which I don't love, but can't think of anything better.ExportingtoPublishingbecause it also includes share links.Assetsprobably feels like it should go underDesign. Once we cover components and scripts as assets, I think it makes more sense as a top-level category.