Author：Web3 Mythology

For months, developers told us the same thing: "TON documentation is scattered, inconsistent, and impossible to navigate". New builders from the US were especially vocal about it.

So starting in late July, TON Studio rebuilt the entire thing from scratch. It's live now at docs.ton.org.

What Changed

Software engineers who understand blockchain have rewritten the content with a flat structure, so you're no longer hunting through nested menus. Furthermore, the landing page routes you based on what you're trying to do — whether it's exploring TON, building contracts, integrating wallets, or troubleshooting with the community.

We added new sections and rewrote existing pages across the board:

• mytonctrl and mylocalton guides
• Development setup (Sandbox and Blueprint, with major help from TonTech)
• IDEs and SDKs
• Analytics, oracles, bridges
• TON Connect for dApps and wallet services
• Ecosystem-wide standard contracts, such as: wallets, Jettons, and NFTs
• Smart contract development guidelines: common patterns, gas, and security best practices
• TVM instructions with improved search and better UX
• TL-B schemas
• Tolk, FunC, and Tact languages: in particular, FunC docs received a big overhaul
• "Coming from Ethereum" guide for developers making the switch

Dr. Nikolai Durov's original whitepapers are now in web format with cross-links and AI-generated summaries.

There are diagrams and Mermaid visualizations throughout the documentation.

Each new contribution is reviewed by AI against the style guide, along with automatic spell-checking, formatting checks, and navigation and redirect checks, before anything goes live.

Ask Questions, Get Answers

There's more to AI than reviews — we built an AI assistant directly into the docs.

Instead of clicking through pages or jumping into Telegram chats every time you hit a roadblock, just ask your question in plain language. The AI searches the entire documentation and pulls relevant answers.

What's Next

We're continuing to add release pipelines with assigned technical owners, a simpler process for community contributions, interactive components and code playgrounds, more content to fill the gaps, and improved AI assistance as the knowledge base grows.

Community Feedback

This documentation exists because developers like you told us what wasn't working. Built with feedback from Zengo, RSquad, TonTech, the TON API team, TON Core, and shaped and delivered by TON Studio.

Give it a try: docs.ton.org

Found something wrong? Open a new issue.

Know a topic well? Help with content reviews and submit new content — contributions are welcome.

Building a project on TON? Consider hosting and maintaining its documentation with us. Having everything in one place makes it easier for developers to discover and helps the AI give better answers.