Skip to content

docs: rename Infra Partners to Operate, fold Specs in as a Specification section - #2289

Merged
GigaHierz merged 3 commits into
mainfrom
palango/2260-operate-tab
Aug 27, 2026
Merged

docs: rename Infra Partners to Operate, fold Specs in as a Specification section#2289
GigaHierz merged 3 commits into
mainfrom
palango/2260-operate-tab

Conversation

@palango

@palango palango commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Node operators, RPC providers, and custodians had their docs split across two tabs: "Infra Partners" held the run-a-node guides and network notices, "Specs" the protocol specification. This renames the tab to Operate, moves infra-partners/* to operate/* and specs/* to operate/specification/*, and folds the Specs tab's two sidebar groups into Operate. Redirects follow the standard set by #2279 and used in the Legacy-tab removal (#2280): wildcards cover the old paths, and every existing destination is re-pointed at its final page so nothing chains. Closes #2260.

Changes

  • All 39 pages move with git mv (23 infra-partners, 16 specs). The Operate tab keeps the existing groups and appends the two from Specs: Network Notices (with Archive), Node Operation, Node Management, Reference, Specification (with Deployments), Protocol Upgrades (with L2 Migration).
  • Redirects: 61 destinations under /infra-partners/ and 10 under /specs re-pointed to the new paths, and four entries added at the end of the array: /infra-partners/:slug*/operate/:slug*, /specs/:slug*/operate/specification/:slug*, plus bare /infra-partners/operate/notices/overview and /specs/operate/specification. The wildcards sit after the 13 pre-existing /infra-partners/* sources (the six notice aliases into the archive, and the integration paths), which keep matching first.
  • About 140 inbound links rewritten across 47 files, plus the hardcoded FAQ anchor in navigation.global.anchors, the home-page card in snippets/home.jsx, the AGENTS.md directory list and canonical-fact table, and CODEOWNERS collapsed to a single /operate/ @celo-org/blockchain entry.
  • Two scope items from story: Operate tab — move infra-partners/* to operate/* and fold Specs in as a Specification section #2260 were already done on main: tooling/nodes/run-a-celo-node was a four-line external-link stub deleted in docs: surface llms.txt and the docs MCP server as AI entry points #2237 (redirect already in place), and the task: Remove the Legacy tab — migrate still-relevant L1 content to Learn/Operate, delete the rest #2254 "keep → Operate" set is only the operator FAQ, which was already in the tree.

specs.celo.org

The redirect stubs (celo-org/specs#195) hard-code docs.celo.org/specs/... targets and forward URL fragments, so old specs.celo.org links now take one extra hop through the new /specs/:slug* wildcard. celo-org/specs#199 tracks re-pointing the stubs at /operate/specification/... after this deploys; until then the /specs redirects here must not be removed.

Verification

$ npx mintlify broken-links
success no broken links found

$ bash scripts/check-orphans.sh
Found 23 orphan page(s): .mdx files not referenced in docs.json navigation

The orphan set is unchanged from the base branch; none of the 39 moved pages is in it.

  • A scripted audit over all 706 redirect entries confirms every non-wildcard destination exists on disk, is listed in navigation, and is not itself a redirect source.
  • All 23 anchored references into operate/* (20 content links, 3 redirect destinations) were checked against the headings of the moved files; the link checker ignores anchors, so this was scripted separately.
  • A mint dev battery of 13 URLs confirms the redirect behavior, including the ordering question: /infra-partners/notices/jovian-upgrade still lands on /operate/notices/archive/jovian-upgrade (the specific alias beats the wildcard), and every redirect resolves to a 200 page in one hop.
  • All 23 specs.celo.org stub targets resolve through at most one redirect. Five sampled specs.celo.org-era URLs with fragments were verified hop by hop (stub forwards the hash, redirect resolves, heading exists):
    • specs.celo.org/l2_migration.html#changes-for-json-rpc-users
    • specs.celo.org/token_duality.html#the-transfer-precompile
    • specs.celo.org/deployments.html#mainnet
    • specs.celo.org/smart_contract_updates_from_l1.html#epochs-and-rewards
    • specs.celo.org/tx_fees.html#base-fee-floor

Not verified: the production redirect chain end to end, since the new redirects only take effect on deploy. Each hop was verified independently against mint dev, which serves the same docs.json.

…specs/ under operate/

Moves 23 infra-partners pages to operate/ and 16 spec pages to
operate/specification/, folds the Specs tab's two groups into the Operate
tab, re-points 71 redirect destinations, and adds wildcard redirects for
both old path prefixes.
…e/ paths

Rewrites ~140 internal links across 47 files, points the home-page
Integrate card at the operator overview instead of the removed
integration index, collapses the two CODEOWNERS blocks into /operate/,
and updates the AGENTS.md directory list and canonical-fact paths.
@palango
palango requested review from a team as code owners August 27, 2026 15:51
@palango
palango requested review from GigaHierz, piersy and seolaoh and removed request for a team, piersy and seolaoh August 27, 2026 15:51

@GigaHierz GigaHierz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Reviewed the full restructure on the PR head. All 39 moved pages are reachable under the new Operate tab, the specs→operate/specification and infra-partners→operate rename mapping preserves every slug, all 706 redirects resolve to live pages with no chains and correct wildcard ordering, 146 internal /operate/* links plus 17 anchors resolve, no orphans introduced, and no stale 'Infra Partners' strings remain. CI green. LGTM.

@GigaHierz
GigaHierz merged commit a07223d into main Aug 27, 2026
4 checks passed
@GigaHierz
GigaHierz deleted the palango/2260-operate-tab branch August 27, 2026 19:10
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.

story: Operate tab — move infra-partners/* to operate/* and fold Specs in as a Specification section

2 participants