Repository navigation
docs: add the navigation of the docs site pages - #225
Merged
Merged
Conversation
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.
What does this PR do?
No linked issue: part of the docs layout rework (NanoForge-dev/actions#117). With it, the editor docs reach the docs site for the first time.
docs/docs/navigation.json: the sidebar order (Getting started, Using the editor, Plugins), from the list that was indocs/docs/README.md.docs/docs/README.mdremoved: every.mdindocs/docswould be a published page, and its copy instructions are obsolete. Its screenshot notes move toCLAUDE.md, with the rule that every page is listed once in the navigation.How do you test this PR?
mint validate,broken-linksanda11ypass.pnpm lint,pnpm typecheckpass; the push hook ran lint, typecheck and unit tests (pass).Merge danger
Door: two-way.
Blast radius: docs only.
Order: release NanoForge-dev/actions#117 as 3.2.0 first. Until then the old
@v3sync would copy these renamed pages next to the old ones and regenerate the docs repodocs.json. Then merge this PR, and NanoForge-dev/docs (opened next) last. After NanoForge-dev/actions#117, a release of this repo without this PR fails the docs step before writing anything (safe,continue-on-error).Follow-up issues
Quality gate
CLAUDE.mdmint a11y: all images have alt textEDITOR_TOKENcookie note in create-your-first-project is accurate and already public in this repo