Repository navigation
docs: redirect the engine 3d research pages that moved out of the site - #7
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. This PR adds redirects for the engine pages that move out of the site in NanoForge-dev/Engine (
docs/rewrite-content):/docs/engine/lib-graphic-3d/*and/docs/engine/graphics-3d/editor-proposalnow go to/docs/engine/graphics-3d/index. Without them, those URLs 404 once the next engine release syncs its docs.How do you test this PR?
docs.json.mint validate,mint broken-linksandmint a11yon a scratch copy of the site with all four source branches (engine, cli, loader, editor) and the docs redirects synced in: all pass, 83 pages.pnpm exec prettier --checkand the pre-push hook (lint, tests): pass.Merge danger
Door: two-way,
docs.jsononly.Blast radius: the live docs.nanoforge.eu, at merge. Merging before the engine release is fine. If Mintlify gives the redirect precedence over a page that still exists, those research pages simply stop being reachable a little early.
Quality gate
reviewer: findings fixed in the last commitmint a11y)style-reviewer: pass