Skip to content

feat: expand TON Web3 documentation - #2340

Open
TONresistor wants to merge 10 commits into
ton-blockchain:mainfrom
TONresistor:docs/web3-update
Open

TONresistor wants to merge 10 commits into
ton-blockchain:mainfrom
TONresistor:docs/web3-update

Conversation

@TONresistor

@TONresistor TONresistor commented Oct 15, 2026 •

Copy link
Copy Markdown

Make Web3 services a main documentation section with a dedicated navigation tab, preserving existing URLs.

Organize TON DNS, Storage, Proxy and Sites into overviews, guides and references. Document TON Tunnel and Payment Network, and update the Web3 overview.

@TONresistor TONresistor changed the title expand TON Web3 documentation feat: expand TON Web3 documentation Oct 15, 2026
@TONresistor
TONresistor force-pushed the docs/web3-update branch 2 times, most recently from b14825a to 5d8ef85 Compare October 20, 2026 10:26
@TONresistor
TONresistor marked this pull request as ready for review October 20, 2026 15:01
@novusnota

Copy link
Copy Markdown
Collaborator

Hey @TONresistor, sorry for the delayed reply 🙏

First off, thank you for such an expansion — there are many interesting write-ups and pieces of neat content within the edits sent ❤️

That said, this PR is a tad too big to review and edit iteratively, so let's proceed this way: starting on Monday, I will create smaller PRs based on the core parts of this PR, such as DNS, Proxy, Sites, Storage, Tunnel, and Payment network. This will result in six smaller PRs. I'll do my best to maintain your authorship throughout the process, but I will ultimately decide on the final structure and wording. Yet, commit messages on merge to main will have a Co-Authored-By: ... note with you there. That's a given.

I believe this approach will help us retain your contributions while ensuring the highest documentation quality. I hope you agree with this plan!

Thanks again, and stay tuned for updates :)

@TONresistor

Copy link
Copy Markdown
Author

hey @novusnota thanks for the update! yes I agree with you it makes sense

I’d be happy to split this PR into 6 smaller PR myself if that helps, would you prefer that, or would you rather handle them ?

regarding the final structure, will you keep the dedicated main section for Web3 Services separate from Blockchain Foundations or that was a wrong move ?

@novusnota

novusnota commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

I’d be happy to split this PR into 6 smaller PR myself if that helps, would you prefer that, or would you rather handle them ?

I'd prefer handling them myself, if you don't mind — having a single one here works well for discovery and experimentation.

regarding the final structure, will you keep the dedicated main section for Web3 Services separate from Blockchain Foundations or that was a wrong move ?

To be frank, I'm not sure yet, but I played around with it a bit and it seems like a decent choice. I'll think this over before making the first PR.

UPD: Some time ago, we had Web3 as a separate section, but it was weak at the time, so we had to move it somewhere else. Foundations fit the bill, while the Ecosystem section fell short because Web3 weren't really external to the ecosystem at large, nor was it a first-class citizen. Web3 in TON has grown a bit since then :)

This branch has not been deployed

No deployments
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