docs: migrate specs.celo.org into a new Specs tab - #2224
Open
palango wants to merge 11 commits into
Open
Conversation
Converts the 16 mdBook pages from celo-org/specs to MDX under specs/, mirroring the old sidebar hierarchy in docs.json. Removes the external-link stub (infra-partners/specs) in favor of the real content and assigns /specs/ to the blockchain team in CODEOWNERS.
Rewrites the 24 links in live sections to internal paths. The defunct core_contracts.html links now target /tooling/contracts/core-contracts. References in _deprecated/ are left untouched.
Removes the one-page Introduction group that duplicated the page label in the sidebar.
The March 2025 L2 migration is described in past tense, the completed Ice Cream and Isthmus activations likewise, and the upcoming Jovian upgrade now targets Mainnet and Celo Sepolia as its own timeline table already says (Alfajores and Baklava are deprecated).
palango
requested review from
karlb,
katen0ra and
seolaoh
and removed request for
a team
July 21, 2026 10:22
karlb
reviewed
Jul 21, 2026
karlb
left a comment
Contributor
There was a problem hiding this comment.
Some outdated text that is unrelated to the migration itself and two cases of redundant content.
Jovian activated on Celo Sepolia and Mainnet in March 2026; the timestamps come from infra-partners/notices/archive/jovian-upgrade. Block heights are not published for this upgrade, so the column is dropped.
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.
What
Moves the Celo L2 specification from specs.celo.org (mdBook, celo-org/specs) into this repo:
specs/, faithful to the source (doctoc TOCs stripped, H1s moved to frontmatter, links rewritten to internal paths).infra-partners/specsis removed;/infra-partners/specsredirects to/specs._deprecated/untouched)./specs/assigned to @celo-org/blockchain in CODEOWNERS.Merge order
Merge and deploy this PR first. A follow-up PR in celo-org/specs then replaces the mdBook site with redirect stubs pointing at these pages, so old specs.celo.org URLs keep working (fragments preserved).
Open items for @celo-org/blockchain
specs/transaction-fees.mdxstill contains the old note that the mainnet FeeHandler behavior is unconfirmed "as of 2024-11-15" (left verbatim on purpose). Current on-chain config: burn and carbon fractions are zero, 100% of fees go to a cLabs-named beneficiary.home/protocol/transactions/overview.mdxclaims 10% of transaction fees go to the carbon offset fund, which does not match the current on-chain carbon fraction (zero). Not touched in this PR.networks/*/network.mdaddress tables,block_time_and_gas_limit.md) were deliberately not migrated; their content is covered bytooling/contracts/*and the legacy transition docs.Follow-ups
specs/token-dualityvshome/protocol/celo-token,specs/fee-abstractionvsbuild-on-celo/fee-abstraction/*) is tracked in Deduplicate migrated Specs pages against the Home and Build guides #2227. Deferred so this PR stays a pure move, and so the trim happens once the celo-org/specs stub mapping pins down which heading fragments have to survive.