You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current seven-tab structure (Home, Build on Celo, Tooling, Contribute to Celo, Infra Partners, Specs, Legacy) mixes audiences, jobs and topics on one axis. Verified at bdf40b37: "Home" is protocol reference with no real homepage; Tooling holds 90 of 292 pages (31%) across ten unrelated groups; Legacy conflates dead L1 content with pages that still apply on L2; 105 duplicate files sit in _deprecated/; 25 tracked pages are unreachable from navigation (including the whole dev-environment-setup group); wallets, fee abstraction and thirdweb are each documented in three or more places; 167 redirects dead-end.
Decisions (agreed — not re-opened in the child issues)
Decision
Outcome
Tab shape
7 → 4: Learn / Build / Operate / Contribute
Specs tab
Folded into Operate as a "Specification" section; redirects from old specs paths
Legacy tab
Removed, not archived. Still-relevant content migrated to Learn (history) or Operate (old L1 node context) before deletion
Tooling tab
Dissolved into Build
Build-tab order
Quickstart → Agents → Mini Apps → Network info → Guides → Tools → Reference
thirdweb
Stays as one tool page at parity with other tools; no code examples, no recommendations
MiniPay
One overview that routes to docs.minipay.xyz for the mini-app lifecycle
Code examples
Troubleshooting-first: keep edge-case examples (e.g. paying gas in USDC); drop large end-to-end examples derivable from SDK docs
Writing standard
AGENTS.md at repo root: headings, structure, writing style, move/redirect checklist
Highest priority now
Analytics + an AI assistant (not Mintlify Pro; research Mintlify-compatible and open-source options)
End-user vs tooling
Every page states who it is for; end-user project listings also live on celo.org/ecosystem
Orphans
Sheet of the orphaned pages only; team marks re-nav/delete; applied in one pass
Tabs at a07223d8 are Home · Build on Celo · Tooling · Contribute to Celo · Operate — Operate has landed; Learn (#2258) and Build (#2259) are the two renames still outstanding.
Overlap rules: #2252 touches no orphaned page (it adds the check); #2253 decides the 22 non-thirdweb orphans; the 3 thirdweb orphans belong to #2255. #2256, #2257, #2264 change content in place; #2258–#2260 move paths and do not rewrite content. #2254 owns legacy/, #2258 owns home/, #2259 owns build-on-celo/ + tooling/, #2260 owns infra-partners/ + specs/. #2257 leaves the spec-vs-guide trim to #2227.
Gate for every child PR
npx mintlify broken-links green (CI), the orphan check green once #2253 lands, and every moved or deleted path has a redirect in docs.json.
Why
The current seven-tab structure (Home, Build on Celo, Tooling, Contribute to Celo, Infra Partners, Specs, Legacy) mixes audiences, jobs and topics on one axis. Verified at
bdf40b37: "Home" is protocol reference with no real homepage; Tooling holds 90 of 292 pages (31%) across ten unrelated groups; Legacy conflates dead L1 content with pages that still apply on L2; 105 duplicate files sit in_deprecated/; 25 tracked pages are unreachable from navigation (including the whole dev-environment-setup group); wallets, fee abstraction and thirdweb are each documented in three or more places; 167 redirects dead-end.Decisions (agreed — not re-opened in the child issues)
AGENTS.mdat repo root: headings, structure, writing style, move/redirect checklistChildren, in execution order
453efdc2a9b0a19c3604c629762173a0a07223d8; specs.celo.org stub re-pointing split to celo-org/specs#199f2ee83afa8175ebbbfa4f52dea9ba97f; residual retired-testnet refs split to #2290a4233070seo.organizationafter reviewe38da175retitled 7 of 9; the thirdweb pair goes with #2255Tabs at
a07223d8are Home · Build on Celo · Tooling · Contribute to Celo · Operate — Operate has landed; Learn (#2258) and Build (#2259) are the two renames still outstanding.Overlap rules: #2252 touches no orphaned page (it adds the check); #2253 decides the 22 non-thirdweb orphans; the 3 thirdweb orphans belong to #2255. #2256, #2257, #2264 change content in place; #2258–#2260 move paths and do not rewrite content. #2254 owns
legacy/, #2258 ownshome/, #2259 ownsbuild-on-celo/+tooling/, #2260 ownsinfra-partners/+specs/. #2257 leaves the spec-vs-guide trim to #2227.Gate for every child PR
npx mintlify broken-linksgreen (CI), the orphan check green once #2253 lands, and every moved or deleted path has a redirect indocs.json.Prior art (pinned to commits, not branches)
a14395f8926eb43424e0d20e6d67ab96f2c8209b—RESTRUCTURE_PLAN.md(rationale, migration mechanics, Appendix A file-by-file map; its Operate section is stale — see story: Operate tab — move infra-partners/* to operate/* and fold Specs in as a Specification section #2260) andCLAUDE.md(absorbed by task: Add AGENTS.md — repo guidance for structure, headings, writing style, and code-example policy #2251)9bd831fe0dc55c29f3e276dd1aee163330513039—restructure-research/01(11-site benchmark),02(agent-first review),03(Web2 readability audit incl. the Self Agent ID spec),04(freshness automation proposal),05(skills & feedback discussion)description), docs.json: duplicate navigation entry for odis-use-case-phone-number-privacy #2240 (duplicate nav entry), Disambiguate colliding page titles (Overview x3, Bridging, Escrow, Encrypted Payment Comments) #2241 (colliding titles), llms.txt: stale OpenAPI spec registration emits a 404 (Mintlify support ticket) #2238 (llms.txt OpenAPI 404)Non-goals
Freshness automation (doc 04 in #2210) — not decided; gets its own issue if and when it is. Re-adding the Startup Pathway link.
Measured at:
bdf40b37