Skip to content

feat(web3): add Web3 services documentation pages#1940

Open
TONresistor wants to merge 2 commits intoton-org:mainfrom
TONresistor:feat/web3-services-docs
Open

feat(web3): add Web3 services documentation pages#1940
TONresistor wants to merge 2 commits intoton-org:mainfrom
TONresistor:feat/web3-services-docs

Conversation

@TONresistor
Copy link

Summary

  • Add 5 new documentation pages under foundations/web3/: TON DNS, TON Storage, TON Proxy, TON Sites, and TON Payments
  • Update docs.json navigation with a new "Web3 services" group
  • Update foundations/services.mdx to link to the new section

Pages added

Page Description
ton-dns.mdx Domain name system — resolution, record categories, smart contract interactions, code examples
ton-storage.mdx Decentralized file storage — torrent-based architecture, bag management, provider network
ton-proxy.mdx ADNL-based network proxy — relay nodes, entry points, configuration
ton-sites.mdx Hosting sites over TON network — RLDP-HTTP, access methods, domain binding
ton-payments.mdx Payment channels — off-chain microtransactions, channel lifecycle

Test plan

  • Verify all 5 pages render correctly on Mintlify dev server
  • Check navigation in sidebar under "Web3 services" group
  • Validate internal links between pages
  • Review code examples for correctness

Add 5 new documentation pages for TON Web3 services:
- TON DNS: domain system with TL-B schemas, smart contract interactions, and code examples
- TON Proxy: HTTP-to-ADNL bridge with CLI reference for forward and reverse proxy modes
- TON Sites: web services accessible through ADNL/RLDP with hosting guides
- TON Payments: off-chain payment channels with channel flow and dispute resolution
- TON Storage: distributed file storage with provider contracts, op codes, and get methods

All technical claims fact-checked against the ton-blockchain/ton C++ monorepo.
@github-actions
Copy link
Contributor

Skipping AI review because this PR is from a fork. A maintainer can start the review by commenting /review in this PR.

@github-actions
Copy link
Contributor

Thank you for the contribution!

Unfortunately, it is too large, with over 600 added lines, excluding some generated or otherwise special files. Thus, this pull request is challenging to review and iterate on.

Please split the PR into several smaller ones and consider reverting any unrelated changes, writing less, or approaching the problem in the issue from a different angle.

I look forward to your next submissions. If you still intend to proceed as is, then you are at the mercy of the reviewers.

@novusnota
Copy link
Collaborator

@TONresistor wow, thanks! But could you please split this PR into about 5 distinct ones, with one per new page, please? That'd make it much easier to review and apply changes too.

If they're heavily interlinked, that's fine and you can keep those links as is — we'll be merging them in quick succession once they all are reviewed and approved on our end.

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.

2 participants