docs: dig-dns 13-locale materialization + Super Supporter discount docs#22
Merged
MichaelTaylor3d merged 1 commit intoJul 9, 2026
Conversation
… 14 locales Closes #178, #188 - #178: the dig-dns section of universal-installer.md (--with-dig-dns, the extension's open-by-URN detection) shipped English-only in #18/#19; materialize the current English page into the other 13 locale copies so every locale has the same content (this repo's established i18n practice materializes English into i18n/<locale> for pages pending real translation, matching every other page in the tree). - #188: document the Super Supporter NFT discount on capsule/store publish pricing (previously undocumented) in the FAQ "What does it cost?" answer and the on-chain-anchoring Costs section: 50% off, live full-wallet ownership check at publish time via DIGHUb, and where to mint one (150 $DIG at hub.dig.net). Materialized into all 13 locales; this pass also backfills the pre-existing *domain*-discount paragraph that was added to the English FAQ (#143) but never materialized into the locale copies. - Regenerated static/openrpc.json + openrpc-node.json (`npm run gen`) so their embedded version matches the bumped package.json. Verified: `npm run build` (all 14 locales, onBrokenLinks/onBrokenAnchors throw), `npm run typecheck`, and `npm run test:unit` all pass. Patch bump (0.3.10 -> 0.3.11): docs-only content addition, no behavior/API change.
MichaelTaylor3d
deleted the
docs/178-188-dig-dns-i18n-and-super-supporter-discount
branch
MichaelTaylor3d
added a commit
that referenced
this pull request
Jul 10, 2026
…very (#22) Add a Protocol-track specification page for the window.chia Chia wallet provider — the EIP-1193 of Chia — grounded in the real implementations (hub wallet-methods.js, dig-sdk ChiaProvider, and the DIG Browser native dig_provider.js reference impl): - provider object shape (isDIG/isConnected/request/connect/on/off) and the EIP-1193-style request({method,params}) contract; - every canonical CHIP-0002 method (the shared WALLET_METHODS list) with params, return shapes, and HTTP-derived error codes; - the connect / 202-pending consent contract (per-origin, unspoofable origin); - a capability/version field (chiaVersion + capabilities) for feature-detect; - EIP-6963-style multi-provider discovery (chia:announceProvider / chia:requestProvider + provider-info shape) so multiple Chia wallets can coexist (today injection bails if window.chia already exists). Normative surface (implemented today) vs proposed surface (capability/version, extended methods, error-code alignment, the discovery mechanism, extra events) is marked inline. DIG Browser is named the reference implementation; @dignetwork/dig-sdk's ChiaProvider the recommended consumer. Wired into the Protocol sidebar track (new docs/protocol category), linked from the build-a-dapp tutorial and the glossary, added to the agent-facing llms.txt and the knowledge-graph generator's controlled vocabulary (new provider-spec concept). Also corrected the outdated "loopback" claim in the using-window-chia guide to the real frame-scoped Mojo bridge. npm run build green (no broken links/anchors). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GjQgGAisBupqs7vpkmUhuN
MichaelTaylor3d
added a commit
that referenced
this pull request
Jul 10, 2026
…very (#22) Add a Protocol-track specification page for the window.chia Chia wallet provider — the EIP-1193 of Chia — grounded in the real implementations (hub wallet-methods.js, dig-sdk ChiaProvider, and the DIG Browser native dig_provider.js reference impl): - provider object shape (isDIG/isConnected/request/connect/on/off) and the EIP-1193-style request({method,params}) contract; - every canonical CHIP-0002 method (the shared WALLET_METHODS list) with params, return shapes, and HTTP-derived error codes; - the connect / 202-pending consent contract (per-origin, unspoofable origin); - a capability/version field (chiaVersion + capabilities) for feature-detect; - EIP-6963-style multi-provider discovery (chia:announceProvider / chia:requestProvider + provider-info shape) so multiple Chia wallets can coexist (today injection bails if window.chia already exists). Normative surface (implemented today) vs proposed surface (capability/version, extended methods, error-code alignment, the discovery mechanism, extra events) is marked inline. DIG Browser is named the reference implementation; @dignetwork/dig-sdk's ChiaProvider the recommended consumer. Wired into the Protocol sidebar track (new docs/protocol category), linked from the build-a-dapp tutorial and the glossary, added to the agent-facing llms.txt and the knowledge-graph generator's controlled vocabulary (new provider-spec concept). Also corrected the outdated "loopback" claim in the using-window-chia guide to the real frame-scoped Mojo bridge. npm run build green (no broken links/anchors). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GjQgGAisBupqs7vpkmUhuN
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
1 participant
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.
Summary
universal-installer.md(--with-dig-dns, the extension's open-by-URN detection) shipped English-only in docs.dig.net#18/docs(browser): document the extension's open-by-URN home input (#172) #19. Materializes the current English page into the other 13 locale copies (i18n/<locale>/docusaurus-plugin-content-docs/current/run-a-node/universal-installer.md) so every locale has the same content — following this repo's established i18n practice (every other page's locale copy is currently materialized English pending a real-translation pass; this keeps the page consistent with the rest of the tree rather than being the first one-off real translation).hub.dig.net), and where to mint one (150 $DIG). Added todocs/support/faq.md("What does it cost?") anddocs/digstore/cli/onchain-anchoring.md("Costs"), scoped accurately — the discount currently applies only when publishing through DIGHUb; thedigstoreCLI'sinit/commitalways charge the full live price. Materialized into all 13 locales. This pass also backfills a pre-existing gap found in the same file: the domain-handle discount paragraph (added to the English FAQ for #143) had never been materialized into the 13 locale copies either.static/openrpc.json+static/openrpc-node.json(npm run gen) so their embeddedversionfield matches the bumpedpackage.json(this repo'sgen-machine-specs.mjsdrift-gates these againstpackage.json).Closes DIG-Network/dig_ecosystem#178
Closes DIG-Network/dig_ecosystem#188
Verification
npm run build— clean, all 14 locales,onBrokenLinks/onBrokenAnchors: "throw"(would fail on any broken link/anchor) — passed with exit 0.npm run typecheck— clean.npm run test:unit— passing (1/1).npm run test:a11y(Playwright, this local Windows sandbox) — 19-20 pre-existing failures reproduced identically on a cleanmaincheckout with no working-tree changes (verified viagit stash), confirming they are an environment-specific flakiness (headless-chromium timing /data-themepersistence in this sandbox) unrelated to this change — nothing in this PR touches interactive components, JS, or the pages those failing specs exercise (home, quickstart, onion-routing, store-structure).SemVer
Patch
0.3.10→0.3.11— docs-only content addition/materialization, no public API or behavior change (matches this repo's convention of a patch bump fordocs:commits, e.g. the #18 dig-dns doc PR bumped 0.3.6→0.3.7).Test plan