Skip to content

docs: add 'Submit your dApp to the store' page (explore.dig.net listing flow)#9

Merged
MichaelTaylor3d merged 1 commit into
mainfrom
docs/submit-your-dapp-226
Jul 4, 2026
Merged

docs: add 'Submit your dApp to the store' page (explore.dig.net listing flow)#9
MichaelTaylor3d merged 1 commit into
mainfrom
docs/submit-your-dapp-226

Conversation

@MichaelTaylor3d

Copy link
Copy Markdown
Contributor

What

Adds a user-facing, task-oriented docs page — Submit your dApp to the store — explaining how a developer lists their dApp on the DIG Network dApp store (explore.dig.net):

  1. Connect a wallet at hub.dig.net/submit (the wallet is the submitter identity — no separate account).
  2. Fill in the submission form: metadata (slug, name, tagline, description, category, tags, URL, author, status, accent color, optional repo/version/license/links) + artwork.
  3. Submit for review and track status (Uploading → In review → Approved → Published, or Rejected / Needs a retry).
  4. An admin reviews; once approved, DIGHUb opens the listing on explore.dig.net automatically — the submitter never touches a repository or a pull request.

The page includes a full field reference and the exact PNG artwork sizes (icon-512 512×512 + og 1200×630 required to list; hero 1600×900 + 2 desktop screenshots to be featured; screenshot sizes and caps), all sourced from the shipped submission contract so the doc matches what the form enforces.

IA + cross-links

  • Slots into the App developers sidebar after "Get tipped for your store" (build-a-dapp/submit-to-the-store).
  • Cross-linked from the app-developers landing ("List your dApp in the store") and the DIGHUb how-to journey ("How do I list my dApp in the DIG Network dApp store?").

Saturation-search

Searched the docs tree for anything the submission flow makes stale — there was no prior mention of explore.dig.net or a dApp store anywhere in docs, so this is net-new content with no contradictions to fix.

Machine surfaces / i18n

  • static/llms.txt updated with the new page under "Build a dapp".
  • Materialized the page into all 14 locales (English source; matches the repo's existing untranslated-materialization pattern) so links resolve under onBrokenLinks: "throw".
  • Derived static/knowledge-graph.json regenerated (new node + edges). static/openrpc*.json regenerate to carry the bumped site version (they read package.json version).

Version bump

Minor: 0.1.0 → 0.2.0 — a new documentation page is a backwards-compatible new capability (docs: adding a new section).

How verified

  • npm run typecheck — clean
  • npm run build — green across all 14 locales (onBrokenLinks/onBrokenAnchors: "throw" — no broken links/anchors)
  • npm run test:unit — virtual-screen-reader trace passes
  • npm run test:a11y — all 22 Playwright a11y/SEO tests pass (axe WCAG 2.2 AA, ARIA snapshots, keyboard nav, mobile viewport)
  • CI green on this PR (will monitor)

…ng flow)

Add a task-oriented App-developers page covering how a developer lists their
dApp on the DIG Network dApp store (explore.dig.net): connect a wallet at
hub.dig.net/submit, fill in the submission form (metadata + artwork), track
status, and — once an admin approves — the listing is published automatically.
Documents the field reference, the exact PNG artwork sizes, and the submission
status lifecycle.

Slots into the App-developers sidebar after 'Get tipped for your store', with
cross-links from the app-developers landing and the DIGHUb how-to journey.
Materialized into all 14 locales so links resolve under onBrokenLinks:throw;
llms.txt + the derived knowledge-graph updated. Machine specs (openrpc*.json)
regenerate to carry the bumped site version.

Bump: minor (0.1.0 -> 0.2.0) — a new documentation page (new capability).
@MichaelTaylor3d MichaelTaylor3d merged commit 685d854 into main Jul 4, 2026
4 checks passed
@MichaelTaylor3d MichaelTaylor3d deleted the docs/submit-your-dapp-226 branch July 4, 2026 09:50
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