docs(nav): consolidate deploy pages into one sidebar group#979
Merged
jrusso1020 merged 1 commit intoMay 20, 2026
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
miguel-heygen
approved these changes
May 20, 2026
Collaborator
miguel-heygen
left a comment
There was a problem hiding this comment.
Clean nav restructuring. All 4 deploy pages accounted for, no duplicates, no broken links. JSON valid, Validate docs green. Ship it.
vanceingalls
approved these changes
May 20, 2026
Collaborator
vanceingalls
left a comment
There was a problem hiding this comment.
Pure nav restructure in docs/docs.json — 9 insertions / 9 deletions, no other files touched.
Strengths
- Path-preserving:
docs/docs.json:91-99only re-groups existing sidebar entries; file paths and URLs unchanged, so no redirects needed. - All four referenced pages exist on the head SHA (
guides/deploy.mdx,deploy/aws-lambda.mdx,deploy/templates-on-lambda.mdx,deploy/migrating-to-hyperframes-lambda.mdx). - IA call is right: the three Lambda pages don't belong under Packages (which is for
core/engine/player/producer/studio/clipackage reference), and pullingguides/deploytogether with them surfaces deployment guidance at one shelf.
CI
Validate docs(Docs workflow): SUCCESS on head22c86a2c.CI / Format,Semantic PR title,File size check: SUCCESS. Build/Test/Typecheck/CLI smoke SKIPPED (docs-only path filter — expected).- Optional
Analyze (javascript-typescript)CodeQL still in-progress; not gating.
Nits
- None blocking. Ordering inside the new group (
guides/deployfirst, then Lambda specifics) matches the PR description's stated rationale (broadest audience first).
Additive note: @miguel-heygen already approved with the same read. No gap to surface.
Verdict: APPROVE
Reasoning: Pure docs nav move, no path/URL churn, four referenced pages verified to exist, required docs CI green.
Review by Vai
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
Move the three AWS Lambda deploy pages out of the Packages tab and pull
guides/deployout of the Guides group, into a single new Deploy group in the Documentation tab sidebar:The
Deploygroup is also removed from the Packages tab. File paths are unchanged — only thedocs.jsonsidebar entries move, so all existing URLs (/deploy/aws-lambda,/guides/deploy, etc.) keep working and no redirects are needed.Why
The three Lambda deploy pages (
deploy/aws-lambda,deploy/templates-on-lambda,deploy/migrating-to-hyperframes-lambda) were sitting under the Packages tab in a "Deploy" subgroup. That tab is for package-level reference docs (core, engine, player, producer, studio, cli) — Lambda deployment isn't a package, it's deployment guidance, so readers looking for "how do I deploy?" had to know to click Packages to find it.guides/deploycovers the same surface from a different angle (one-click Vercel + Cloudflare render-API templates) but lived in the Guides flow next to authoring topics. Putting all four under a single Deploy group surfaces them together at the level readers actually look.How
Single change in
docs/docs.json:"guides/deploy"from the Guides group (line 85).Order inside the new group: one-click templates first (broadest audience), then AWS Lambda distributed rendering, then the personalised-batch guide, then the Remotion migration page.
Test plan
npx mint broken-linksfromdocs/returns "no broken links found"; JSON validates withpython3 -c "import json; json.load(open('docs/docs.json'))". Diff is 9 insertions / 9 deletions in a single file.🤖 Generated with Claude Code