Repository navigation
docs: add component hubs for op-node, op-proposer, op-challenger, op-deployer (A4 batch 2) - #21917
Merged
Merged
Conversation
…deployer (A4 batch 2)
Second reviewed batch of Stack Components hub pages, following the merged
hub skeleton template (Overview / Get started / How-tos / Configuration &
flags reference / Releases / Source & spec links). Hubs are thin
identity-and-links pages per the content guide's dual-sourcing ban.
- New hubs: op-stack/components/{op-node,op-proposer,op-challenger,op-deployer}.mdx
- Index: flip the four rows from Planned to linked hubs
- docs.json: new Derivation & Execution and Deployment & Infrastructure
subgroups; op-proposer and op-challenger join Settlement & Proofs
Tracks ethereum-optimism/solutions#969
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EBBBR8m2V8LjzMvuG7Go2L
Review-derived style convention for this batch: no em dashes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EBBBR8m2V8LjzMvuG7Go2L
…m/optimism into docs-improver/a4-hubs-batch2
) The op-challenger hub's flags slot now links the new generated challenger-configuration reference instead of the no-reference-yet fallback wording, and the op-node hub's flag-reference description matches the reworked generated op-node-config page. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Merged
3 tasks
sbvegan
reviewed
Jul 21, 2026
Apply review suggestions on PR #21917: call op-challenger the dispute game challenge service, and describe op-deployer as a deployment tool only, with its upgrade and manage commands marked deprecated and linked to the deprecation notice. Co-Authored-By: Claude <noreply@anthropic.com>
sbvegan
approved these changes
Jul 22, 2026
claude Bot
pushed a commit
that referenced
this pull request
Jul 22, 2026
Semantic-union resolutions: - docs.json: keep develop's op-node entry in the Stack Components "Derivation & Execution" subgroup and add A5's kona-node entry beside it - op-stack/components/index.mdx: keep develop's op-node Hub link (#21917) and A5's kona-node Hub link in the components table Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Jul 22, 2026
Open
ClaytonNorthey92
pushed a commit
to hemilabs/optimism
that referenced
this pull request
Sep 19, 2026
…deployer (A4 batch 2) (ethereum-optimism#21917) Co-authored-by: Claude <noreply@anthropic.com>
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.
Requested by Matthew Cruz · Slack thread
Tracks ethereum-optimism/solutions#969
What
Second batch of Option A slice 4 (component hubs) from the canonical-homes plan (
projects/docs-improver/plans/option-a-canonical-homes.mdin ethereum-optimism/solutions), following the skeleton template and Stack Components section merged in #21865:op-stack/components/op-node.mdx): the rollup node's one identity page, linking the Docker/source tutorials, consensus-client and blobs guides, the flag and JSON-RPC references, releases, source, and the rollup-node + derivation specs.op-stack/components/op-proposer.mdx): links the spin-up tutorial, permissionless-migration and Kona-proofs guides, the proposer configuration reference, releases, source, and the proposals + withdrawals specs.op-stack/components/op-challenger.mdx): links the spin-up tutorial, configuration guide, the run-a-fault-proof-challenger solution guide, prestate tutorial, the new generated challenger configuration reference (docs: roll the flag-reference generator out to op-node, op-proposer, op-challenger, op-conductor #21873), releases, source, and the honest-challenger + fault-dispute-game specs.op-stack/components/op-deployer.mdx): routes into the existing canonical OP Deployer doc set under the Chain Operators tab (the one component whose README already declares its docs source of truth).All four hubs follow the template's exact six-H2 skeleton and the content guide's dual-sourcing ban: identity prose plus links, no restated reference content.
Source citations
Every factual claim was verified against monorepo source at
develop(op-node/README.md,op-proposer/README.md,op-challenger/README.md,op-deployer/README.md, the linked docs pages' own content) and spec paths against the specs repo atmain(protocol/rollup-node.md,protocol/derivation.md,protocol/proposals.md,protocol/withdrawals.md,fault-proof/stage-one/honest-challenger-fdg.md,fault-proof/stage-one/fault-dispute-game.md,protocol/configurability.md). The branch is synced withdeveloppast #21873 (generated flag references): the op-challenger hub links the newchallenger-configurationreference, and the op-node hub's flag-reference description matches the reworked generatedop-node-configpage; both describe the generated tables only as those pages present them.Nav / redirects (serialized docs.json lane)
One docs.json hunk (two new subgroups + two added entries in Stack Components), merged cleanly with #21873's docs.json change after sync. No pages moved or deleted, so no redirects. Checks run locally after the sync: nav validator OK, redirect lint OK, link-policy lint clean against baseline with specs-mirror resolution, docs.json parses.
Reviewer checklist
op-node/,op-proposer/,op-challenger/,op-deployer/source🤖 Drafted by the docs-improver agent — review before merge.
🤖 Generated with Claude Code
Generated by Claude Code