docs: rename Infra Partners to Operate, fold Specs in as a Specification section - #2289
Merged
Conversation
…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.
…te card at nodes overview
GigaHierz
approved these changes
Aug 27, 2026
GigaHierz
left a comment
Contributor
There was a problem hiding this comment.
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.
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.
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/*tooperate/*andspecs/*tooperate/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
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)./infra-partners/and 10 under/specsre-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/overviewand/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.navigation.global.anchors, the home-page card insnippets/home.jsx, the AGENTS.md directory list and canonical-fact table, and CODEOWNERS collapsed to a single/operate/ @celo-org/blockchainentry.main:tooling/nodes/run-a-celo-nodewas 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/specsredirects here must not be removed.Verification
The orphan set is unchanged from the base branch; none of the 39 moved pages is in it.
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.mint devbattery of 13 URLs confirms the redirect behavior, including the ordering question:/infra-partners/notices/jovian-upgradestill lands on/operate/notices/archive/jovian-upgrade(the specific alias beats the wildcard), and every redirect resolves to a 200 page in one hop.specs.celo.org/l2_migration.html#changes-for-json-rpc-usersspecs.celo.org/token_duality.html#the-transfer-precompilespecs.celo.org/deployments.html#mainnetspecs.celo.org/smart_contract_updates_from_l1.html#epochs-and-rewardsspecs.celo.org/tx_fees.html#base-fee-floorNot 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 samedocs.json.