WIP: restructure

[palango]

@katen0ra As discussed yesterday, here's a proposal for a new structure.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
celo-docs	🟢 Ready	View Preview	Jul 3, 2026, 9:35 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[GigaHierz]

Closing without merging — superseded by the epic #2266, which carries the agreed structure and the ordered child issues.

What this PR proved and where it went (pinned at a14395f8):

• The migration mechanics (catch-all redirects, 6-PR sequence, mint broken-links gate) are adopted wholesale — story: Learn tab — move home/* (plus kept L1 content) to learn/* #2258, story: Build tab — merge "Build on Celo" and Tooling into build/*, with Agents and Mini Apps leading #2259, story: Operate tab — move infra-partners/* to operate/* and fold Specs in as a Specification section #2260, story: Homepage, Contribute rename, and an "AI resources" page — final pass #2261.
• Appendix A is the starting file map for the Learn / Build / Contribute moves; the Operate section is re-derived in story: Operate tab — move infra-partners/* to operate/* and fold Specs in as a Specification section #2260 because infra-partners/ changed after this was written.
• CLAUDE.md is absorbed by task: Add AGENTS.md — repo guidance for structure, headings, writing style, and code-example policy #2251 (AGENTS.md).

Decisions that changed versus the draft: Specs goes under Operate; Legacy is removed rather than archived (#2254); the Build tab leads with Agents and Mini Apps.

Thanks for laying this out — it did the hard part. Branch kept for reference; fresh PRs go against the child issues.