fix: resolve 333 v2 routes missing from docs.json nav coverage

[Copilot]

333 v2 pages existed on disk but were neither referenced in docs.json nav nor excluded by .mintignore, causing continuous "No docs config" noise in Mintlify dev output.

docs.json — add missing routable pages

• ES Solutions tab (new): Full Spanish Solutions tab (~111 pages) mirrored from CN — covers Livepeer Studio, Daydream, Streamplace, Embody, Frameworks, and all API reference sub-pages
• Gateway Providers portal: v2/gateways/using-gateways/gateway-providers → EN Public Gateways group
• Orchestrator setup steps (EN only — files exist only in English path):
  • install-go-livepeer → Installation group
  • orch-config → Configuration group
  • connect-to-arbitrum → Network Integration group
• Resource HUB gaps (ES/FR/CN): added resources-portal and documentation-guide/component-library/overview to each language's Resource HUB
• Deduplication: removed ~19 pre-existing duplicate page refs (get-clip, gateway-setup, configuration-flags, rooms/update-user, etc.)

.mintignore — exclude non-routable content

Pattern	Rationale
/v2/**/x-deprecated/**, /v2/**/x-unstaged/**	Extends existing top-level rule to all nested subdirs (es/fr/cn/developers/gateways/etc.)
/v2/**/docs-guide/**	Internal meta-content in all language dirs
/v2/**/README.mdx	Meta-files, not routable pages
Section index.mdx files (about, community, developers, gateways, home, internal, lpt, orchestrators, resources, solutions, es/fr/cn root)	Auto-generated ToC stubs
es/fr/cn developers/builder-opportunities/**, guides-and-resources/**, journey-mapping.mdx	Translation gaps — English nav structure not yet replicated in language tabs
es/fr/cn gateways/about-gateways/**, guides-and-resources/**	Old path structure, superseded by guides-and-tools/
/v2/gateways/quickstart/views/**, groups/**	MDX snippets injected into other pages, not standalone routes
/v2/developers/moved-to-about-livepeer-protocol/**	Redirect targets, content lives in /about/
Gateway references: go-livepeer/**, api-reference/AI-Worker/**, orphaned CLI-HTTP entries, empty stubs	Draft/alternate/empty pages not yet ready for nav
Gateway run-a-gateway: publish/**, v1/**, dual-docker, video-configuration-view, configuration-reference	WIP duplicates of existing nav pages
About, solutions, orchestrators, developers, resources, home draft pages	Marked WIP (MOVE ME, Coming Soon, ? remove?), empty, or superseded by current nav pages

Result: 0 missing routes (↓ from 333).

Scope

• docs.json — ES Solutions tab insertion, targeted page additions, duplicate removal
• .mintignore — new patterns for non-routable v2 content

Validation

# Script checks: all v2/*.mdx files are either in docs.json pages OR matched by .mintignore
python3 -c "
import json, os, re, fnmatch
# [load docs.json, walk v2/, apply mintignore patterns]
# → Total missing routes after all changes: 0
"

Follow-up Tasks

• Add translated builder-opportunities pages to ES/FR/CN Developers tabs (currently mintignored as translation gaps)
• Decide fate of v2/gateways/references/orchestrator-offerings, go-livepeer/cli-reference, and about/livepeer-network/livepeer-actors/* — either complete and add to nav or delete

Type of Change

• Bug fix (fixes an issue)
• New content (adds new documentation)
• Content update (improves existing content)
• Style/formatting fix
• Information architecture change
• Other (please describe)

Related Issues

Related to #

Changes Made

• Added ES Solutions navigation tab to docs.json (mirrors CN, ~111 pages)
• Added 3 orchestrator setup pages and 1 gateway providers page to EN nav groups
• Added resources-portal + component-library/overview to ES/FR/CN Resource HUB
• Removed ~19 pre-existing duplicate page references from docs.json
• Added ~130 lines of targeted .mintignore patterns covering all 333 previously-noisy routes

Testing

• Tested locally with npm run dev
• Verified all links work
• Checked formatting and style
• Reviewed against style guides
• Screenshots (if UI changes)

Screenshots (if applicable)

N/A — navigation config change, no visual diff possible without a running Mintlify instance.

Checklist

• My changes follow the style guides
• I've reviewed the Component Library for available components
• I've updated related pages if needed
• I've checked for broken links
• My changes are clear and easy to understand
• I've tested locally
• I've added/updated keywords and metadata if needed

Additional Notes

The ES Solutions tab was generated programmatically by transforming the CN Solutions tab (replacing v2/cn/ → v2/es/). All 110 of 111 referenced files confirmed to exist on disk; the sole exception (v2/resources/redirect) is a shared stub already used identically in EN/FR/CN nav without issue.

Pre-existing duplicates in docs.json (not introduced by this PR) were cleaned up as part of the same pass.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>docs.json coverage: 333 v2 routes missing from nav</issue_title>
<issue_description>## Summary
Mintlify dev is noisy with repeated "No docs config" errors because a large set of v2 pages exist on disk but are not referenced in docs.json (mintignore-filtered). This issue tracks the alignment work so we can decide which pages should be routable vs. ignored.

What we found

• Total missing v2 routes not in docs.json: 333
• Top-level counts (mintignore-filtered):
  • v2/es: 136
  • v2/developers: 42
  • v2/gateways: 38
  • v2/fr: 36
  • v2/cn: 34
  • v2/about: 11
  • v2/orchestrators: 8
  • v2/resources: 8
  • v2/home: 7
  • v2/solutions: 7
  • v2/internal: 2
  • v2: 1
  • v2/README: 1
  • v2/community: 1
  • v2/lpt: 1

Recommended next steps

Pick one or more of the following strategies per section:

1. Add to docs.json if the page should be routable.
2. Move to x- or internal* if the page is not ready for public nav.
3. Add targeted .mintignore patterns for content that should never be part of Mintlify builds.

Full missing route list

Missing routes (mintignore-filtered)

- v2/README
- v2/about
- v2/about/core-concepts/concepts/actors
- v2/about/faq-about
- v2/about/livepeer-network/demand-side
- v2/about/livepeer-network/fee-flow
- v2/about/livepeer-network/livepeer-actors/delegators
- v2/about/livepeer-network/livepeer-actors/end-users
- v2/about/livepeer-network/livepeer-actors/gateways
- v2/about/livepeer-network/livepeer-actors/orchestrators
- v2/about/livepeer-network/scaling
- v2/about/livepeer-network/supply-side
- v2/cn
- v2/cn/README
- v2/cn/contribute/CONTRIBUTING/AGENT-INSTRUCTIONS
- v2/cn/contribute/CONTRIBUTING/GIT-HOOKS
- v2/cn/contribute/CONTRIBUTING/README
- v2/cn/developers/builder-opportunities/bug-bounties
- v2/cn/developers/builder-opportunities/grants-and-programmes
- v2/cn/developers/builder-opportunities/oss-contributions
- v2/cn/developers/builder-opportunities/overview
- v2/cn/developers/builder-opportunities/rfps-and-proposals
- v2/cn/developers/guides-and-tools/developer-guides
- v2/cn/developers/guides-and-tools/resources
- v2/cn/developers/journey-mapping
- v2/cn/docs-guide/README
- v2/cn/docs-guide/README
- v2/cn/docs-guide/feature-guides/architecture-map
- v2/cn/docs-guide/feature-guides/automation-pipelines
- v2/cn/docs-guide/feature-guides/content-system
- v2/cn/docs-guide/feature-guides/data-integrations
- v2/cn/docs-guide/feature-guides/feature-map
- v2/cn/docs-guide/feature-map
- v2/cn/docs-guide/indexes/components-index
- v2/cn/docs-guide/indexes/pages-index
- v2/cn/docs-guide/indexes/templates-index
- v2/cn/docs-guide/indexes/workflows-index
- v2/cn/docs-guide/lpd
- v2/cn/docs-guide/lpd
- v2/cn/docs-guide/quality-testing/quality-gates
- v2/cn/docs-guide/scripts-index
- v2/cn/docs-guide/source-of-truth-policy
- v2/cn/docs-guide/source-of-truth-policy
- v2/cn/gateways/about/functions
- v2/cn/resources/documentation-guide/component-library/overview
- v2/cn/resources/resources-portal
- v2/community
- v2/developers
- v2/developers/ai-inference-on-livepeer/overview
- v2/developers/ai-inference-on-livepeer/workload-fit
- v2/developers/building-on-livepeer/quick-starts/README
- v2/developers/developer-guide
- v2/developers/developer-journey
- v2/developers/developer-platforms/all-ecosystem/ecosystem-products
- v2/developers/developer-platforms/builder-hub
- v2/developers/developer-platforms/daydream/daydream
- v2/developers/developer-platforms/frameworks/frameworks
- v2/developers/developer-platforms/livepeer-studio/livepeer-studio
- v2/developers/developer-platforms/streamplace/streamplace
- v2/developers/developer-platforms/streamplace/streamplace-architecture
- v2/developers/developer-platforms/streamplace/streamplace-funding-model
- v2/developers/developer-platforms/streamplace/streamplace-guide
- v2/developers/developer-platforms/streamplace/streamplace-integration
- v2/developers/developer-platforms/streamplace/streamplace-provenance
- v2/developers/developer-tools/external-tooling
- v2/developers/developer-tools/gateways
- v2/developers/guides-and-resources/contribution-guide
- v2/developers/guides-and-resources/developer-guides
- v2/developers/guides-and-resources/developer-help
- v2/developers/guides-and-resources/resources
- v2/developers/guides/partner-integrations
- v2/developers/journey-mapping
- v2/developers/livepeer-real-time-video/page-1
- v2/developers/livepeer-real-time-video/video-streaming-on-livepeer/README
- v2/developers/livepeer-real-time-video/video-streaming-on-livepeer/frameworks-spe
- v2/developers/livepeer-real-time-video/video-streaming-on-livepeer/streamdiffusion
- v2/developers/livepeer-real-time-video/video-streaming-on-livepeer/video-streaming-101
- v2/developers/moved-to-about-livepeer-protocol/livepeer-actors/README
- v2/developers/moved-to-about-livepeer-protocol/livepeer-actors/delegators
- v2/de...

</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes livepeer/docs#778

<!-- START COPILOT CODING AGENT TIPS -->
---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs.