[bruno-andrade-azion]

Summary

• Triages the 105 English pages that sit in no navigation tree (MM-16244). All 105 already passed lint:navcheck on main: 100 were parked in src/nav/redirects.json as "discarded" and 5 in src/nav/exempt.json. This PR checks each parking and finishes it.
• Retires 63 pages (en + pt-br, 126 files). 62 of them already 301 in production, but their sources stayed in the repo: the old Build, Deliver, Observe, Secure, and Platform homes, the five by-solution architecture landings, the develop-with-azion pages, the Store and Observe journey pages (MM-16240), the 35 template-showcase landings (MM-16247), Form Builder, peering, and the templates-and-integrations overview. The 63rd page, the legacy How to create a digital certificate guide, was live. It now 301s to Upload a digital certificate. That guide gains a Bind the certificate to a v3 domain section (Console + API v3), so the v3 steps the old guide carried are not lost. The PR also deletes the 64 images that only these pages used (about 24 MB).
• Keeps the 19 Reference Architecture pages and places them in the Use Cases tree. src/nav/redirects.json marked them "folded into its use-case page", but they were never redirected, and the use-case catalog (gtm-definitions/use-cases.md) lists each one as the Docs of a Reference Architecture (Published or Needs update). docs(architectures): keep security-modernization and bot-management as API v3 versions #2589 also keeps WAAP and Online Fraud Prevention as the v4 pages for its v3 versions. Each page gets a "hidden": true row next to its use case, in that use case's Solution group. The page keeps its URL, sidebar context, and breadcrumb, and it stays out of the menu, the hub, and prev/next. Removing the "discarded" entries also means pnpm nav:url-map can no longer turn these live pages into 301s.

How to test

1. cd apps/docs && pnpm lint:navcheck. Expect: passes, 18 discarded, 5 exempt, with no soft-max warning for the hidden rows.
2. pnpm nav:migrate (dry run). Expect: 0 page/language permalinks to move.
3. pnpm build:local (Node 26; NODE_USE_SYSTEM_CA=1 behind a TLS-intercepting proxy). Expect: Complete!.
4. Open /en/documentation/use-cases/build-and-run-applications/microservices-applications/. The breadcrumb reads Use Cases > Build and run applications > Microservices API on Functions, the sidebar opens on that group, and the page is not a menu row. Repeat with the pt-br twin /pt-br/documentacao/casos-de-uso/construir-e-executar-aplicacoes/aplicacoes-microsservicos/.
5. Open /en/documentation/guides/application-security/tls-and-certificates/digital-certificates/#bind-the-certificate-to-a-v3-domain and the pt-br /pt-br/documentacao/guias/seguranca-de-aplicacoes/tls-e-certificados/certificado-digital/#vincule-o-certificado-a-um-dominio-v3. The intro's v3 sentence links to this section.
6. node scripts/ci/ratchet.mjs linkcheck and node scripts/ci/ratchet.mjs slugcheck from the repo root, after the build.

URL changes and redirects

Removed permalinks:

• 62 page/language pairs (124 URLs) already had a 301 in apps/docs/redirects/{en,pt-br}/0[01].json. Each one still resolves in one hop to a live page.
• /en/documentation/guides/application-security/tls-and-certificates/create-a-digital-certificate/ -> /en/documentation/guides/application-security/tls-and-certificates/digital-certificates/ (added, redirects/en/01.json)
• /pt-br/documentacao/guias/seguranca-de-aplicacoes/tls-e-certificados/criar-certificado-digital/ -> /pt-br/documentacao/guias/seguranca-de-aplicacoes/tls-e-certificados/certificado-digital/ (added, redirects/pt-br/01.json)

Retargeted, so no reader goes through a chain or lands on an unrelated page:

• /products/deliver/ (en + pt-br, 00.json) pointed at the retired /products/deploy/ and now goes straight to the docs home.
• /products/peering/, /docs/products/peering/ and /products/azion-network-program/ (en + pt-br, 00.json and 01.json, 10 rows) pointed at Professional Services, which has no peering content. They now point to the support contacts table, which lists the peering and NOC addresses: /en/documentation/support/#other-contacts and /pt-br/documentacao/suporte/#outros-contatos.

No URL of a kept page changes. The 19 architecture pages keep theirs, as nav:migrate confirms.

Notes

• Where the other orphans went: 18 entries stay in src/nav/redirects.json for their owners: 7 for docs(platform): retire the v3 build and deploy journey pages #2587 (MM-16238), 8 for docs(secure): retire the pre-Workloads security journey and guide pages #2586 (MM-16239), 2 for MM-16268 (the WAF and Bot Manager example hubs, to be registered in firewall.json), and liveness-detection for docs(templates): point Deploy links to the current Marketplace catalog (MM-16236) #2582 (MM-16236), which already deletes it. 5 entries stay in exempt.json: the 2 architectures docs(architectures): keep security-modernization and bot-management as API v3 versions #2589 (MM-16243) keeps as v3 versions, coming-soon (resolve.ts uses it as a constant), and the 2 Orchestrator architectures (no catalogued use case).
• Merge conflicts to expect:
  • src/nav/redirects.json with docs(secure): retire the pre-Workloads security journey and guide pages #2586, docs(platform): retire the v3 build and deploy journey pages #2587, and docs(templates): point Deploy links to the current Marketplace catalog (MM-16236) #2582. Apply both sides' removals.
  • The end of redirects/{en,pt-br}/01.json with docs(secure): retire the pre-Workloads security journey and guide pages #2586, docs(platform): retire the v3 build and deploy journey pages #2587, and docs(architectures): keep security-modernization and bot-management as API v3 versions #2589. Keep both appended blocks.
  • docs(architectures): keep security-modernization and bot-management as API v3 versions #2589 edits the two by-solution security hubs that this PR deletes. Keep the deletion: their URLs already 301 to /use-cases/.
• Tooling: lint-navcheck.ts now counts only visible children for the soft max, so hidden rows don't trigger warnings. The hidden comment in schema.ts now covers Reference Architecture pages.
• Follow-ups (not in this PR):
  • Link each Reference Architecture page from its use-case page. Only 4 of the 19 are linked today.
  • Update the catalog's "Docs:" lines and rewrite the 12 pages it marks "Needs update".
  • Confirm with the Functions and Marketplace owners whether Form Builder still ships. Its only page was already 301'd to the Marketplace hub.
  • ai_agent_autonomous_security keeps its URL under Build and run AI workloads, while the catalog files it under Secure applications and networks.
  • AGENTS.md still names apps/redirects-massive/ for the redirect files.
• Checks run locally: build:local passes. lint:navcheck passes. nav:migrate reports 0 moves. ci:ratchet linkcheck reports 159 issues (baseline 221), and none of them involves a URL in this diff. ci:ratchet slugcheck reports 6 (baseline 6). Five independent read-only reviews checked the deleted pages and their redirects, lost content, the hidden rows, redirect integrity, sibling-PR conflicts, and completeness.
• Jira: MM-16244 · Epic MM-16212