Skip to content

docs: add Documentation Checklist + surface chain-contribution flow#2049

Open
ryanRfox wants to merge 1 commit intox402-foundation:mainfrom
ryanRfox:docs/extend-default-assets-cross-sdk-checklist
Open

docs: add Documentation Checklist + surface chain-contribution flow#2049
ryanRfox wants to merge 1 commit intox402-foundation:mainfrom
ryanRfox:docs/extend-default-assets-cross-sdk-checklist

Conversation

@ryanRfox
Copy link
Copy Markdown
Contributor

Fixes #2048.

Changes

  • DEFAULT_ASSETS.md: append Documentation Checklist + promote docs update to its own named step in 'Adding a New Chain'
  • docs/core-concepts/network-and-token-support.mdx:
    • Fix broken /DEFAULT_ASSETS.md link (absolute github.com URL)
    • Split 'Adding Support for New Networks' into 'Runtime Registration' and 'Contributing a New Default Asset'
    • Move 'Running Your Own Facilitator' under '## Facilitators' where it belongs

Verified locally via Mintlify dev server.

AI disclosure

This PR used an agentic coding workflow and was reviewed by Ryan R. Fox (an actual human) before posting.

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 16, 2026

@ryanRfox is attempting to deploy a commit to the Coinbase Team on Vercel.

A member of the Team first needs to authorize it.

DEFAULT_ASSETS.md's 'Adding a New Chain' numbered flow stopped at 'Update
all three SDKs' → 'Submit a PR' and did not mention the user-facing docs
surfaces that also enumerate every chain with default-asset support. As a
result, recent onboarding PRs have shipped with stale docs (e.g. the
Radius PR x402-foundation#2038 updated the SDKs but not the docs table or Go README).
The existing Cross-SDK Checklist at the bottom enumerates only the three
code registries, mirroring the same gap.

network-and-token-support.mdx has a parallel discoverability problem:
the pointer to DEFAULT_ASSETS.md used a repo-relative path that resolves
to a broken link on docs.x402.org, and the pointer sat inside the
'Default Assets for Dollar-String Pricing' intro rather than under
'Adding Support for New Networks' where a would-be contributor actually
looks. The 'Adding' section itself described only runtime registration
(server.register from consumer code) and did not mention the separate
upstream-contribution path, and it also contained a 'Running Your Own
Facilitator' subsection that is about facilitator infrastructure, not
about adding networks — a topical mismatch. The page also ordered the
'Facilitators' section before 'Adding Support for New Networks', which
inverts the natural read → use → extend → operate narrative.

Changes:

  * DEFAULT_ASSETS.md:
      - Promote 'Update user-facing documentation' to a numbered step in
        'Adding a New Chain' (new step 3, between 'Update all three SDKs'
        and 'Submit a PR'), with a cross-reference to the new checklist.
      - Append a new 'Documentation Checklist' section below the existing
        Cross-SDK Checklist, naming the two hot docs surfaces
        (network-and-token-support.mdx and go/mechanisms/evm/README.md)
        that must also be updated on a new chain onboarding.

  * docs/core-concepts/network-and-token-support.mdx:
      - Remove the oddly-placed 'See DEFAULT_ASSETS.md' link from the
        Dollar-String Pricing intro; replace with an in-page anchor
        pointing at the new contribution subsection.
      - Split 'Adding Support for New Networks' into two subsections:
        'Runtime Registration' (the existing content, unchanged) and
        a new 'Contributing a New Default Asset' subsection that links
        to DEFAULT_ASSETS.md via an absolute github.com URL (so the
        link works on the published docs site) and explicitly names
        the cross-SDK + docs checklist.
      - Move 'Running Your Own Facilitator' out of 'Adding Support for
        New Networks' into the existing 'Facilitators' section, where
        it belongs topically.
      - Swap top-level section order: 'Adding Support for New Networks'
        now precedes 'Facilitators', matching the read → use → extend →
        operate narrative.

No code changes. Documentation only.
@ryanRfox ryanRfox force-pushed the docs/extend-default-assets-cross-sdk-checklist branch from c8ee259 to 28d8426 Compare April 16, 2026 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Chain-onboarding docs: checklist gap + broken link on docs.x402.org

1 participant