Restructure Mesa docs & remove duplicates#1211
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
e7087bc to
1a5b29a
Compare
…tables to one-liners
…etup.mdx for tutorials
…link from archive-upgrade and parent index
1a5b29a to
77528a0
Compare
… upgrade-steps/index description
…mitation, manual mode, exchange danger-box, backward-compatible phrasing. Add links from Mesa flag ref to external snark-workers/rosetta docs.
77528a0 to
c434bbd
Compare
| sidebar_label: Upgrade | ||
| hide_title: true | ||
| description: Upgrade phase of the Mesa hard fork — network halt, state export, and Mesa build publication. | ||
| description: Upgrade phase of the Mesa hard fork — network halt, state export, Mesa build publication, and fork schedule values per network. |
There was a problem hiding this comment.
I don't agree with this overall move of the schedule to the "upgrade" step of the Upgrade Steps, because this step is clearly about what happens after stop_network_slot.
So introducing the section where we explain what stop transaction and what stop network slots are, seems to late at this point in time.
I think Fork Schedule was ok where it was before the upgrade step
|
|
||
| ### Mainnet | ||
|
|
||
| :::warning Values not yet published |
There was a problem hiding this comment.
this icon is not rendering correctly in the current published version of the docs
| ### Faster Blocks | ||
| ### Faster Blocks — [MIP6](https://github.com/MinaProtocol/MIPs/blob/main/MIPS/mip-0006-slot-reduction-90s.md) | ||
|
|
||
| Mesa reduces the slot time to 90 seconds and unsets the default zkApp soft limit (previously 24 commands per block). Defined in [MIP6](https://github.com/MinaProtocol/MIPs/blob/main/MIPS/mip-0006-slot-reduction-90s.md). |
There was a problem hiding this comment.
We may need to add that we lowered zkApp soft limit from 24 to 12.
|
|
||
| | Actor | What to do | | ||
| |---|---| | ||
| | **Block Producers** | Verify your node is on the Mesa chain (`mina client status`). If automode, check that the `activated` file exists in your config directory (see [Troubleshooting](/network-upgrades/mesa/troubleshooting#how-do-i-know-which-binary-my-node-is-using)). Monitor block production. | |
There was a problem hiding this comment.
Where did this table land?
| to: '/network-upgrades/mesa/archive-upgrade', | ||
| }, | ||
| { | ||
| from: '/mesa-upgrade/fork-schedule', |
There was a problem hiding this comment.
I would not make this change
| to: '/network-upgrades/mesa/appendix/archive-node-schema-changes', | ||
| }, | ||
| { | ||
| from: '/network-upgrades/mesa/fork-schedule', |
Summary
Restructures the Mesa network upgrade documentation to eliminate duplication, improve information architecture, and fix flow issues. 711 insertions, 777 deletions across 16 files. No information was lost; all removed content is preserved via cross-links to canonical sources.
Structural changes
1. Split overloaded pages
preflight-network.mdx(was 305 lines) → split into:preflight-network.mdx(lean) — version matrix, Docker images, Debian packages, nightly builds (reference)preflight-setup.mdx(new) — operator tutorials: Docker/Debian daemon setup, archive node, Rosetta, verification, support (how-to)2. Merge sparse / redundant pages
fork-schedule.mdx→ merged intoupgrade-steps/upgrade.mdx. The fork schedule is only relevant during the Upgrade phase, so it lives there now. File deleted.index.mdx→glossary.mdx. Index now lists one-liner summaries linking to glossary entries.index.mdx→requirements.mdx. Requirements page now serves double duty: hardware specs + pre-upgrade procedures.3. Slim the overview page
index.mdxphase tables reduced from full per-actor procedures (50+ lines each) to one-liner summaries linking toupgrade-steps/pages.## Examplessection removed (was already linked from the phase flow).Deduplication
Eliminated triplicated callout
The "Mesa preflight hard fork completed" info box was copy-pasted verbatim in 3 files. Now lives only in
preflight-network.mdx; the other two link to it.Removed duplicate flag configuration
The 120-line collapsible flag reference in
post-upgrade.mdxwas removed (initially), then restored with improvements after discovering 8 flags (RAYON_NUM_THREADS,--shutdown-on-disconnect, etc.) were undocumented elsewhere. Now includes explicit links to canonical sources innode-operators/docs.Cross-linked repeated explanations
snark-workers/getting-starteddata-and-history/rosettaImproved content
archive-upgrade.mdx: Version info uses<Tabs>(Preflight/Devnet/Mainnet) instead of a monolithic info box. Network-agnostic phrasing fixed ("Mainnet database" → "archive database with Berkeley-era data").requirements.mdx: Full per-actor pre-upgrade checklist added (Block Producers, SNARK Coordinators, Archive Nodes, Exchanges, zkApp Developers).upgrade.mdx: Fork schedule merged in; timestamp/slot conflation fixed.post-upgrade.mdx: Duplicate## Report Issuesheading removed. Flag reference restored with improved intro and canonical links.Configuration changes
sidebars.js: Removedfork-scheduleentry, addedpreflight-setupentry.docusaurus.config.js: Added redirects for/mesa-upgrade/fork-scheduleand/network-upgrades/mesa/fork-schedule→/network-upgrades/mesa/upgrade-steps/upgrade.Verification