docs: remove the Legacy tab

.github/CODEOWNERS

@@ -18,9 +18,6 @@
 # Infrastructure Partners section - Blockchain team (was cel2)
 /infra-partners/ @celo-org/blockchain
 
-# Legacy section - Blockchain team (L1 content)
-/legacy/ @celo-org/blockchain
-
 # Specs section (was specs.celo.org) - Blockchain team
 /specs/ @celo-org/blockchain
 

AGENTS.md

@@ -8,7 +8,7 @@ Structural work in progress is tracked in the restructure epic, [#2266](https://
 
 - A [Mintlify](https://mintlify.com) site. Content is MDX; navigation, redirects and theme live in `docs.json`. There is no build step beyond the Mintlify CLI.
 - `docs.json` is the single source of truth for what is reachable. **A file on disk is unreachable until it is listed under `navigation`.**
-- Content directories today: `home/`, `build-on-celo/`, `tooling/`, `contribute-to-celo/`, `infra-partners/`, `specs/`, `legacy/`.
+- Content directories today: `home/`, `build-on-celo/`, `tooling/`, `contribute-to-celo/`, `infra-partners/`, `specs/`.
 - `snippets/` holds reusable JSX/MDX (`/snippets/ColoredText.jsx`, `/snippets/YouTube.jsx`, `/snippets/AddNetworkButton.jsx`). Import with an absolute path after the frontmatter: `import {YouTube} from '/snippets/YouTube.jsx'`.
 - Static assets: `img/`, `images/`, `assets/`, `logo/`.
 

build-on-celo/fee-abstraction/using-fee-abstraction.mdx

@@ -33,7 +33,7 @@ Allowlisted addresses may be **adapters** rather than full ERC20 tokens. Adapter
 
 To get the underlying token address for an adapter, call `adaptedToken()` on the adapter contract. Newer adapters — including the USD₮ and USA₮ ones — expose this as `getAdaptedToken()` instead, so try both if the first call reverts.
 
-For more on gas pricing, see [Gas Pricing](/legacy/protocol/transaction/gas-pricing).
+For more on gas pricing, see [Transaction Fees](/specs/transaction-fees).
 
 ### Adapter Addresses
 
@@ -140,7 +140,7 @@ async function main() {
 
 ### 2. Prepare the Transaction
 
-Set `feeCurrency` to the adapter address (USDC/USD₮/USA₮) or token address (USDm, EURm, BRLm). Use transaction type `123` (`0x7b`), which is [CIP-64](/legacy/protocol/transaction/transaction-types) compliant.
+Set `feeCurrency` to the adapter address (USDC/USD₮/USA₮) or token address (USDm, EURm, BRLm). Use transaction type `123` (`0x7b`), which is [CIP-64](/home/protocol/transactions/transaction-types) compliant.
 ```js
 let tx = {
   // ... other transaction fields

build-on-celo/index.mdx

@@ -71,6 +71,6 @@ Following a successful Baklava upgrade, the Celo L2 Mainnet officially went live
 
 * [Layer 2 Specification](/specs)
 * [Node Operator Guide](/infra-partners/operators/overview)
-* [What's Changed?](/legacy/overview)
+* [About Celo L1](/home/celo-l1)
 * [Cel2 Code](https://github.com/celo-org/optimism)
-* [FAQ](/legacy/faq)
+* [FAQ](/infra-partners/operators/faq)

contribute-to-celo/community-rpc-nodes/how-it-works.mdx

@@ -17,11 +17,11 @@ The term "validator" is used in the code and corresponding explanation due to hi
 
 ## RPC Elections
 
-In Celo's RPC elections (formerly [validator elections](/legacy/protocol/pos/validator-elections)), holders of the native asset CELO participate in the process to support network operations and earn rewards for voting.
+In Celo's RPC elections (formerly [validator elections](/home/protocol/staking/validator-elections)), holders of the native asset CELO participate in the process to support network operations and earn rewards for voting.
 
 The election process follows these steps:
 
-1. **Lock CELO tokens**: Holders must first move their CELO balances into the [Locked Celo](/legacy/protocol/pos/locked-gold) (formerly "Celo Gold") smart contract before participating in elections.
+1. **Lock CELO tokens**: Holders must first move their CELO balances into the [Locked Celo](/home/protocol/staking/locked-celo) (formerly "Celo Gold") smart contract before participating in elections.
 
 2. **Vote for Groups**: Rather than voting directly for individual node providers, accounts cast their votes for validator groups that manage collections of nodes.
 

contribute-to-celo/community-rpc-nodes/registering-as-rpc-node.mdx

@@ -33,7 +33,7 @@ If you don't have enough CELO, you can practice the registration process on the
 Private keys are the central primitive of any cryptographic system and need to be handled with extreme care. Loss of your private key can lead to irreversible loss of assets.
 </Danger>
 
-This guide contains a large number of keys, so it is important to understand the purpose of each key. [Read more about key management.](/legacy/validator/key-management/summary)
+This guide contains a large number of keys, so it is important to understand the purpose of each key. [Read more about key management.](/home/protocol/staking/key-management/summary)
 
 ### Account and Signer Keys
 
@@ -135,7 +135,7 @@ For detailed instructions on registering your node URL and metadata, see [Regist
 
 ## Register the Nodes and Group
 
-To participate in elections as an RPC provider, you must register both your group and individual node. When registering a Group, you'll need to specify a [commission](/legacy/protocol/pos/validator-groups#group-share) - this is the percentage of epoch rewards that group members pay to the group.
+To participate in elections as an RPC provider, you must register both your group and individual node. When registering a Group, you'll need to specify a [commission](/home/protocol/staking/validator-groups#group-share) - this is the percentage of epoch rewards that group members pay to the group.
 
 Since we want to keep our account key secure, we'll first authorize the validator signing key instead of using the account key for validation: