Repository navigation
docs: own the loader folder of the docs site with an explicit navigation - #124
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).
.github/nanoforge.json:docs.categorycli→loader. The new docs-sync deletes and rewrites the category's folder, so loader can't sharedocs/cliwith the CLI any more. The docs site shows it as a "Loader" group of the CLI dropdown.docs/docs/loader/1-overview.mdx→docs/docs/overview.mdx(and client, website, server),docs/docs/navigation.json../2-client→./client),mintlify/componentsimports removed.How do you test this PR?
./2-clientlinks before the fix; after it, check passes. Synced into the docs branch:mint validate,broken-linksanda11ypass.pnpm lintpass; the push hook ran lint, build and unit tests (pass).Merge danger
Door: two-way. URLs move from
/docs/cli/loader/...to/docs/loader/...(redirected by the docs PR).Blast radius: docs pages and the docs category 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). Don't release loader with this config before NanoForge-dev/actions#117: the old sync would writedocs/loadernext to the olddocs/cli/loader.Follow-up issues
None.
Quality gate
mint a11y