Skip to content

Restructure next into a job-oriented nav, moving 56 pages with redirects and repointed links - #435

Open
veejask-41 wants to merge 2 commits into
wso2:mainfrom
veejask-41:improvement-ai-gateway-docs-423
Open

Restructure next into a job-oriented nav, moving 56 pages with redirects and repointed links#435
veejask-41 wants to merge 2 commits into
wso2:mainfrom
veejask-41:improvement-ai-gateway-docs-423

Conversation

@veejask-41

Copy link
Copy Markdown
Contributor

Summary

Second phase of the AI Gateway docs revamp: applies the job-oriented navigation from #423 to
en/docs/ai-gateway/next/, moving every page into a directory that matches its new nav position,
with a redirect for each move and every inbound link repointed.

Level-2 nav no longer names components. LLM Proxy, Resiliency, Observability, Analytics,
Setup, Deployment, Performance and Management API are gone, replaced by the eleven job
sections the issue specifies. Guardrails are out from under LLM Proxy and now sit in
Control Content at level 2, which is what our own Overview already implied by saying they apply
at three levels.

Refs #423

What changed

  • 56 of 60 pages moved, and eight directories dissolved: llm-proxy/, setup/, deployment/,
    performance/, observability/, analytics/, resiliency/ and
    gateway-controller-management-api/. Nothing is orphaned — the only file not in nav is
    README.md, which was already out of nav.
  • Max nav depth is now 3. The current nav already breached the issue's limit: Deployment > Deployment Modes > Kubernetes > Overview and its two siblings sat at depth 4. Collapsing to
    Run the Gateway > Kubernetes fixes all three.
  • 61 redirect entries. 56 for this phase's moves, Phase 0's merged quick start, plus four
    pre-existing deployment-modes/ redirects whose targets this phase moves — those would have
    silently started pointing at deleted pages, so they are repointed at their final destinations
    rather than left to chain.
  • The auth page is refiled under Control Access
    gateway-controller-management-api/authentication.md becomes
    control-access/secure-the-management-api.md
  • The AWS Bedrock provider guide comes home. It was navved under the top-level Guides
    section, not under AI Gateway at all. It now sits in Connect LLM Providers.
  • The task guides are now reachable from AI Gateway.
  • Control Content is flattened and reordered. No sub-grouping by category, and ordered
    cheapest-first, so expanding it opens on Guardrails Overview rather than dropping the reader
    into AWS Bedrock Guardrail — the heaviest page in the set.
  • The MCP quick start is renamed to create-an-mcp-proxy.md. After Merge the two quick starts into one tabbed, video-free page and retit… #424 there is exactly one
    quick start in this doc set, so a second file with that name under a Create an MCP Proxy nav
    label was actively misleading.
  • llms.txt: 37 of the 39 AI Gateway URLs rewritten to the new paths.

Two changes go beyond a path substitution, both deliberate:

  • Three long-standing broken cross-references are fixed. The guardrail pages linked into
    api-gateway/next/policies/ with ../../../../../ where the tree only goes three levels deep.
    The move changes the arithmetic anyway, so these are corrected in passing. This is where the
    3-warning reduction comes from.

Verification

  • mkdocs build -c emits 41 warnings, down from 44, with zero new warnings.
  • Every relative link and asset in all 60 files resolved against the filesystem: 407 targets.
    Seven unresolved, all pre-existing or documented — five dead directory links in README.md
    (two predate this PR) and the two artifact-templating.md links.
  • All 367 anchor links validated against the built HTML. Zero broken. mkdocs does not check
    anchors, so this needed doing separately — it covers the 251 same-directory schemas.md#… links
    in the management API reference, which is the largest single link cluster in the tree.
  • 255 tags in the built site resolve. Image paths needed the same depth arithmetic as
    links: 11 performance charts and 2 policy-execution diagrams would otherwise have broken.
  • 61 redirects: every target exists, every stub is generated, no source file survives. Stubs
    forward the URL fragment, so deep links with anchors land on the right section.
  • Nav order matches the issue's proposed structure at all 14 positions; zero items nest
    four deep.
  • Frozen version folders (1.0.0/, 1.1.0/, 1.2.0/) are untouched. The only changes outside
    ai-gateway/ are three one-line link repoints in ai-workspace/ pages that pointed into the
    moved tree.

Action required at release time

en/mkdocs.yml carries 33 redirects mapping version-less ai-gateway/ onto
ai-gateway/1.1.0/. This PR points 112 canonical_url/md_url fields and 39 llms.txt
URLs at version-less new paths, which no released version serves yet. That follows the
frontmatter convention the revamp plan mandates and is consistent across all 56 pages, but it means
those 33 redirects must be repointed when next becomes a release, or those URLs will 404.
Nothing in this PR can resolve that.

@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 54bb2629-95ad-459b-9ee2-b5b814b989a2

📥 Commits

Reviewing files that changed from the base of the PR and between 2c282c3 and ad78880.

📒 Files selected for processing (6)
  • en/docs/ai-gateway/next/control-content/execution-order.md
  • en/docs/ai-gateway/next/mcp-proxy/create-an-mcp-proxy.md
  • en/docs/ai-gateway/next/run-the-gateway/immutable-gateway.md
  • en/docs/ai-gateway/next/run-the-gateway/sizing-and-performance/ai-gateway-runtime-with-four-cpus.md
  • en/docs/ai-gateway/next/run-the-gateway/sizing-and-performance/ai-gateway-runtime-with-two-cpus.md
  • en/docs/ai-gateway/next/run-the-gateway/sizing-and-performance/overview.md

📝 Walkthrough

Walkthrough

The PR reorganizes AI Gateway documentation paths. It updates page metadata, internal links, navigation, redirects, standalone indexes, and image references. It also renames the MCP quick-start page and removes its introductory video.

Changes

AI Gateway documentation restructure

Layer / File(s) Summary
Entry links and indexes
en/docs/ai-gateway/next/README.md, en/docs/ai-gateway/next/overview.md, en/docs/ai-gateway/next/quick-start-guide.md, en/docs/ai-workspace/..., en/docs/llms.txt, en/docs/next/index.md
Top-level guides and indexes now reference the reorganized AI Gateway paths.
Provider, exposure, and traffic pages
en/docs/ai-gateway/next/connect-llm-providers/*, en/docs/ai-gateway/next/control-content/*, en/docs/ai-gateway/next/control-cost-and-traffic/*, en/docs/ai-gateway/next/expose-llms/*, en/docs/ai-gateway/next/monitor-traffic/*
Page metadata and related links now use the current provider, control, exposure, and monitoring paths.
MCP, access, and Management API references
en/docs/ai-gateway/next/mcp-proxy/*, en/docs/ai-gateway/next/control-access/*, en/docs/ai-gateway/next/reference/management-api/*
MCP and Management API pages now use reorganized URLs. Authentication references target the shared access page.
Gateway operation and deployment pages
en/docs/ai-gateway/next/run-the-gateway/*
Gateway, Kubernetes, deployment, and sizing pages now use updated metadata, links, and relative asset paths.
Navigation and redirects
en/mkdocs.yml
AI Gateway navigation now uses job-oriented sections. Legacy paths redirect to the reorganized pages.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Possibly related issues

Possibly related PRs

Suggested reviewers: thushani-jayasekera

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main navigation restructure, page moves, redirects, and link updates.
Description check ✅ Passed The description clearly explains the purpose, scope, implementation, verification results, and release-time migration requirement.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 9

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@en/docs/ai-gateway/next/control-content/execution-order.md`:
- Line 83: Shorten the alt text for the image in the execution-order
documentation, and apply the same change to the other image at the corresponding
location. Keep each alt text at or below 155 characters while preserving the
detailed explanation in the surrounding text.

In `@en/docs/ai-gateway/next/control-content/overview.md`:
- Around line 17-19: Revise one of the two consecutive sentences beginning with
“Guardrails” in the overview content, while preserving both sentences’ meaning
and the existing links and documentation style.

In `@en/docs/ai-gateway/next/mcp-proxy/create-an-mcp-proxy.md`:
- Line 17: Update the changed Markdown heading from “## Quick Start” to sentence
case, “## Quick start,” while preserving the existing heading level and content.

In `@en/docs/ai-gateway/next/reference/management-api/llm-provider-management.md`:
- Around line 4-5: Update the Management API index entry in README.md from the
obsolete gateway-controller-management-api path to
reference/management-api/overview.md, while leaving the surrounding navigation
entries unchanged.

In `@en/docs/ai-gateway/next/run-the-gateway/configuration.md`:
- Line 95: Update the documentation sentence to remove spaces around the em
dash, changing “Secrets — see” to “Secrets—see”. Also update both “Artifact
Templating” links at the referenced locations to use
../../../api-gateway/next/setup/artifact-templating.md.

In `@en/docs/ai-gateway/next/run-the-gateway/immutable-gateway.md`:
- Line 82: Update the Gateway Artifact Templating reference in
immutable-gateway.md to use the next-version setup/artifact-templating.md link
instead of the 1.1.0 path, leaving the surrounding templating guidance
unchanged.

In
`@en/docs/ai-gateway/next/run-the-gateway/sizing-and-performance/ai-gateway-runtime-with-four-cpus.md`:
- Line 29: Shorten the alt text for the throughput and average-response-time
charts in ai-gateway-runtime-with-four-cpus.md (lines 29 and 41) and
ai-gateway-runtime-with-two-cpus.md (lines 29 and 40) to sentence-case
descriptions of the chart type, metric, and runtime size, each no longer than
155 characters. In overview.md (line 37), shorten the deployment architecture
alt text to 155 characters or fewer and omit instance details covered by the
table.

In `@en/mkdocs.yml`:
- Around line 1444-1500: Extend the existing “AI Gateway revamp phase 1:
job-oriented nav” comment above the redirect mappings to explicitly note that
all redirects containing the literal “next” path segment must be updated when
that version is released, preventing legacy links from returning 404.
- Around line 679-690: Remove the duplicate navigation entries for the nine
ai-and-mcp guide pages from either the nested “Guides” section near “Configure
AI Coding Assistants” or the top-level “Guides” section, keeping each page
listed exactly once. Preserve the existing navigation hierarchy and retain all
nine unique guide links.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 418b856c-5f4a-4243-9d37-20ce3409921c

📥 Commits

Reviewing files that changed from the base of the PR and between d0c2388 and 2c282c3.

📒 Files selected for processing (65)
  • en/docs/ai-gateway/next/README.md
  • en/docs/ai-gateway/next/connect-llm-providers/configure-aws-bedrock-provider.md
  • en/docs/ai-gateway/next/connect-llm-providers/llm-templates.md
  • en/docs/ai-gateway/next/control-access/secure-the-management-api.md
  • en/docs/ai-gateway/next/control-content/aws-bedrock-guardrail.md
  • en/docs/ai-gateway/next/control-content/azure-content-safety.md
  • en/docs/ai-gateway/next/control-content/content-length.md
  • en/docs/ai-gateway/next/control-content/execution-order.md
  • en/docs/ai-gateway/next/control-content/json-schema.md
  • en/docs/ai-gateway/next/control-content/overview.md
  • en/docs/ai-gateway/next/control-content/pii-masking-regex.md
  • en/docs/ai-gateway/next/control-content/prompt-decorator.md
  • en/docs/ai-gateway/next/control-content/prompt-template.md
  • en/docs/ai-gateway/next/control-content/regex.md
  • en/docs/ai-gateway/next/control-content/semantic-prompt-guard.md
  • en/docs/ai-gateway/next/control-content/sentence-count.md
  • en/docs/ai-gateway/next/control-content/url.md
  • en/docs/ai-gateway/next/control-content/word-count.md
  • en/docs/ai-gateway/next/control-cost-and-traffic/model-round-robin.md
  • en/docs/ai-gateway/next/control-cost-and-traffic/model-weighted-round-robin.md
  • en/docs/ai-gateway/next/control-cost-and-traffic/semantic-caching.md
  • en/docs/ai-gateway/next/control-cost-and-traffic/timeouts.md
  • en/docs/ai-gateway/next/expose-llms/multi-provider-routing.md
  • en/docs/ai-gateway/next/expose-llms/streaming-responses.md
  • en/docs/ai-gateway/next/mcp-proxy/create-an-mcp-proxy.md
  • en/docs/ai-gateway/next/mcp-proxy/mcp-acl-list.md
  • en/docs/ai-gateway/next/mcp-proxy/mcp-authentication.md
  • en/docs/ai-gateway/next/mcp-proxy/mcp-authorization.md
  • en/docs/ai-gateway/next/mcp-proxy/mcp-rewrite.md
  • en/docs/ai-gateway/next/monitor-traffic/analytics-header-filter.md
  • en/docs/ai-gateway/next/monitor-traffic/logging.md
  • en/docs/ai-gateway/next/monitor-traffic/moesif-analytics.md
  • en/docs/ai-gateway/next/monitor-traffic/tracing.md
  • en/docs/ai-gateway/next/overview.md
  • en/docs/ai-gateway/next/quick-start-guide.md
  • en/docs/ai-gateway/next/reference/management-api/certificate-management.md
  • en/docs/ai-gateway/next/reference/management-api/llm-provider-management.md
  • en/docs/ai-gateway/next/reference/management-api/llm-provider-template-management.md
  • en/docs/ai-gateway/next/reference/management-api/llm-proxy-management.md
  • en/docs/ai-gateway/next/reference/management-api/mcp-proxy-management.md
  • en/docs/ai-gateway/next/reference/management-api/overview.md
  • en/docs/ai-gateway/next/reference/management-api/schemas.md
  • en/docs/ai-gateway/next/reference/management-api/secrets-management.md
  • en/docs/ai-gateway/next/run-the-gateway/configuration.md
  • en/docs/ai-gateway/next/run-the-gateway/database-setup.md
  • en/docs/ai-gateway/next/run-the-gateway/immutable-gateway.md
  • en/docs/ai-gateway/next/run-the-gateway/kubernetes/gateway-operator.md
  • en/docs/ai-gateway/next/run-the-gateway/kubernetes/kubernetes-standalone.md
  • en/docs/ai-gateway/next/run-the-gateway/kubernetes/overview.md
  • en/docs/ai-gateway/next/run-the-gateway/production-deployment/ai-workload-tuning.md
  • en/docs/ai-gateway/next/run-the-gateway/production-deployment/control-plane-connection.md
  • en/docs/ai-gateway/next/run-the-gateway/production-deployment/database-configuration.md
  • en/docs/ai-gateway/next/run-the-gateway/production-deployment/deploy-and-verify.md
  • en/docs/ai-gateway/next/run-the-gateway/production-deployment/overview.md
  • en/docs/ai-gateway/next/run-the-gateway/production-deployment/resources-and-scaling.md
  • en/docs/ai-gateway/next/run-the-gateway/production-deployment/security-hardening.md
  • en/docs/ai-gateway/next/run-the-gateway/sizing-and-performance/ai-gateway-runtime-with-four-cpus.md
  • en/docs/ai-gateway/next/run-the-gateway/sizing-and-performance/ai-gateway-runtime-with-two-cpus.md
  • en/docs/ai-gateway/next/run-the-gateway/sizing-and-performance/overview.md
  • en/docs/ai-workspace/1.0.0/policies/overview.md
  • en/docs/ai-workspace/next/policies/overview.md
  • en/docs/ai-workspace/next/sync-gateway-created-artifacts.md
  • en/docs/llms.txt
  • en/docs/next/index.md
  • en/mkdocs.yml

Comment thread en/docs/ai-gateway/next/control-content/execution-order.md Outdated
Comment thread en/docs/ai-gateway/next/control-content/overview.md
Comment thread en/docs/ai-gateway/next/mcp-proxy/create-an-mcp-proxy.md Outdated
Comment thread en/docs/ai-gateway/next/run-the-gateway/configuration.md
Comment thread en/docs/ai-gateway/next/run-the-gateway/immutable-gateway.md Outdated
Comment thread en/mkdocs.yml
Comment thread en/mkdocs.yml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant