Skip to content

Restructure documentation to GitBook three-layer architecture#23

Merged
Troublor merged 70 commits into
mainfrom
william/doc/restructure-to-gitbook
Apr 1, 2026
Merged

Restructure documentation to GitBook three-layer architecture#23
Troublor merged 70 commits into
mainfrom
william/doc/restructure-to-gitbook

Conversation

@Troublor

@Troublor Troublor commented Apr 1, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Restructures the entire documentation site from flat Pandoc-generated HTML into a three-layer GitBook architecture: User Guide (user/), Developer Docs (dev/), and Specification (maintained in mega-evm, linked via absolute URLs).
  • Removes all legacy build artifacts (Pandoc templates, HTML output, manifest files) and migrates content into GitBook-flavored Markdown with proper frontmatter, custom blocks, and GitBook space variables.
  • Adds comprehensive new developer documentation: gas estimation, debugging with mega-evme, RPC method reference pages (eth_subscribe, eth_callAfter, eth_getLogsWithCursor, realtime_sendRawTransaction, error codes), realtime API guide, volatile data access, resource limits, system contracts, contracts & tokens registry, tooling & infrastructure partners, Build with AI, and developer FAQ.
  • Adds user guide pages: get started, connect wallet, bridge, faucet, featured apps, and user FAQ.
  • Adds top-level narrative pages: architecture overview and mini-blocks explainer.
  • Adds layer-specific AGENTS.md writing rules for each directory and doc-audit skills (correctness, freshness, readability).
  • Fixes broken internal links, a GitBook rendering bug (duplicate endtab), a typo (debug_replyBlock → debug_replayBlock), and corrects eth_getLogsWithCursor availability status.

Troublor added 30 commits March 26, 2026 18:54
…i-block terminology

- Reorganize user guide: replace mainnet.md/testnet.md with topic pages
  (get-started, connect, bridge, contracts) using mainnet/testnet tabs
- Add missing legacy content: L1 contracts, Multicall3, chain params
- Rename 'mini block' to 'mini-block' across all docs (70 occurrences)
- Add mini-block and EVM block definitions to spec glossary
- Add uptime.megaeth.com network status to user pages
- Move README.md to top-level in SUMMARY.md
- Fix all cross-links to deleted pages
…ctions (same addresses on mainnet and testnet)
…rview

- Rename dev/getting-started.md to dev/overview.md, reframe as overview
- Remove duplicate 'Connect to MegaETH' section from overview
- Add dev/gas-estimation.md: eth_estimateGas usage, toolchain config, common errors
- Add dev/debugging.md: debug RPC methods, mega-evme replay/simulation, tracers
- Slim overview.md gas estimation and debugging sections to link to new pages
- Update gas-model.md tips to cross-link to gas estimation page
- Update all cross-references (SUMMARY, README, bridge, contracts, spec)
…missing

Rewrite 20 descriptions that duplicated the page's opening paragraph
with distinct SEO summaries. Add missing descriptions to 6 spec pages
(overview, glossary, hardfork-spec, dual-gas-model, gas-detention,
upgrades/overview).
Move the Access to Volatile Data section from evm-differences.md into
a new dev/volatile-data.md page. Add best practices: defer reads, split
heavy transactions, use DELEGATECALL for oracle, separate gas-sensitive
logic. Include good/bad Solidity patterns in tabs. Keep a summary + link
in evm-differences.md. Update cross-references in debugging.md and
gas-estimation.md.
Under the current absolute cap, read order is irrelevant. Replace
'read late' advice with 'keep under 20M' guidance. Move the read-late
pattern into a Rex4 (unstable) expandable where it actually applies.
@claude

claude Bot commented Apr 1, 2026

Copy link
Copy Markdown
Contributor

Review: GitBook restructure

This is a major restructure (62 commits, 79 files) migrating the docs from Pandoc/Cloudflare Pages to a GitBook three-layer architecture. The structure, navigation, and most content look good. A few issues need attention before merge.

Blocking:

  • Factual error in landing page: "sub-millisecond block times" (mini-blocks are ~10ms = sub-second)
  • Gas limit contradiction: resource-limits.md says 10,000,000,000 per-transaction; gas-estimation.md and dev/faq.md both say the on-chain transaction gas limit is 1,000,000,000. One of these is wrong.

Non-blocking:

  • .claude/doc-audit.md references docs/integration/AGENTS.md (line 3) and claims resource-limits.md says 2B (line 30), both stale — the audit was written against an earlier version of the files.

Comment thread docs/README.md
Comment thread docs/dev/execution/resource-limits.md Outdated
Comment thread .claude/doc-audit.md Outdated
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Apr 1, 2026

Copy link
Copy Markdown

Deploying megaeth-documentation with  Cloudflare Pages  Cloudflare Pages

Latest commit: ef916c6
Status:🚫  Build failed.

View logs

@claude

claude Bot commented Apr 1, 2026

Copy link
Copy Markdown
Contributor

This is a large, well-structured restructure. The architecture is clean and the new content is comprehensive. Three outstanding issues from previous review rounds still need to be addressed before merging:

  1. docs/README.md — "sub-millisecond" is factually wrong (thread already open). Mini-blocks are ~10 ms, which is sub-second, not sub-millisecond. Fix: replace with "sub-second".

  2. Gas limit inconsistency: 10B vs 1B (thread already open on resource-limits.md). resource-limits.md states the per-transaction gas limit is 10,000,000,000 (10B), but dev/faq.md and dev/send-tx/gas-estimation.md both state it is 1,000,000,000 (1B). One of these is wrong — verify against the sequencer config and make all three files consistent.

  3. .claude/doc-audit.md references a non-existent layer (thread already open). Line 3 cites docs/integration/AGENTS.md, which does not exist in this PR. Line 30 also states resource-limits.md says "2,000,000,000 (2B)" but the actual file says 10B. Update the audit doc to match reality before merging.

Comment thread docs/SUMMARY.md Outdated
* [Debugging Transactions](dev/send-tx/debugging.md)
* [Read from MegaETH](dev/read/overview.md)
* [Realtime API](dev/read/realtime-api.md)
* RPC Reference

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Navigation broken: RPC Reference is a plain-text entry with no page link. GitBook requires every navigation item to have a target file. Either create a docs/dev/read/rpc/overview.md landing page and link it here, or collapse the section so each method appears directly under "Read from MegaETH".

Suggested change
* RPC Reference
* [RPC Reference](dev/read/rpc/overview.md)

Comment thread docs/dev/send-tx/contracts.md Outdated
Comment thread docs/dev/faq.md Outdated
Comment thread docs/dev/faq.md Outdated
Comment thread AGENTS.md Outdated
@claude

claude Bot commented Apr 1, 2026

Copy link
Copy Markdown
Contributor

Review

3 previously flagged issues remain unresolved — addressing those is a blocker.

Open threads (not addressed in latest push)

  1. docs/README.mdsub-millisecond block times is still present. Mini-blocks are ~10 ms (sub-second, not sub-millisecond).

  2. docs/dev/execution/resource-limits.md — per-transaction Gas limit is 10,000,000,000 in resource-limits.md but dev/faq.md line 54 says 1,000,000,000. Still inconsistent.

  3. .claude/doc-audit.md — references docs/integration/AGENTS.md (non-existent layer) and quotes resource-limits.md as saying 2 B gas when the file says 10 B.

New issue

AGENTS.md lines 110–111 — the "Cross-link to the EVM spec with relative paths" bullet contradicts the rest of the same file (spec doesn't live in this repo), docs/AGENTS.md, and every page in this PR (all use absolute GitBook URLs). Inline suggestion posted.

@claude

claude Bot commented Apr 1, 2026

Copy link
Copy Markdown
Contributor

Reviewed the current state of the PR. All 7 previously opened threads remain unresolved:

  1. docs/README.md — still says "sub-millisecond block times" (should be ~10ms)
  2. docs/dev/execution/resource-limits.md vs gas-estimation.md / dev/faq.md — Gas limit is 10B in resource-limits but 1B in the other two files; contradition unresolved
  3. .claude/doc-audit.md — still references non-existent docs/integration/AGENTS.md and claims resource-limits.md says 2B (it says 10B)
  4. docs/SUMMARY.md — "RPC Reference" is still a plain-text entry with no link target
  5. docs/dev/send-tx/contracts.md — heading hierarchy still jumps H1→H3, skipping H2
  6. docs/dev/faq.md — blockHash FAQ heading says 0xfff[...]fff but the answer describes a null value
  7. docs/dev/faq.md — token address question still points to the community wiki instead of contracts.md

Please address the open threads before merging.

@claude

claude Bot commented Apr 1, 2026

Copy link
Copy Markdown
Contributor

Review update — 2026-04-01

Resolved 7 of 8 previous threads — all addressed. One remains open:

docs/SUMMARY.mdRPC Reference still has no target file. GitBook requires every navigation entry to be a linked page. The plain-text RPC Reference grouping label will break navigation. Either add a docs/dev/read/rpc/overview.md landing page and link it, or promote the method pages one level up under "Read from MegaETH".

No new issues found — the restructure is solid.

@claude

claude Bot commented Apr 1, 2026

Copy link
Copy Markdown
Contributor

Reviewed the latest changes. All previous threads are resolved except one:

Still open: docs/SUMMARY.mdRPC Reference is still a plain-text entry with no linked page (thread PRRT_kwDOODfgX854HZ9b). GitBook will not render this as a navigation item. Either create a docs/dev/read/rpc/overview.md landing page and link it, or remove the grouping level and list the individual RPC methods directly under "Read from MegaETH".

No new issues found. Content is internally consistent (gas limits, heading levels, spec cross-links all clean).

@Troublor Troublor merged commit 7e0f519 into main Apr 1, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant