docs.ton.org is now structured around developer workflows

Documentation update

Over the past week, TON Tech team updated docs.ton.org: navigation was redesigned around developer scenarios (including link fixes), a new Applications section was created (TON Connect, AppKit, TON Pay, WalletKit), TON Center API reference was improved, search was significantly upgraded and hundreds of smaller fixes were shipped across the documentation.

Previously, the entire documentation lived inside one flat sidebar: application developers, smart contract developers and infrastructure engineers all saw the same long list of sections mixed together. Before starting actual work, developers first had to understand how the documentation itself was structured.

The new navigation is now split by scenarios:

• TON overview — an entry point for developers who are just getting started with TON: what TON is, how to create a first wallet, get test coins and choose a development path
• Blockchain basics — the shared technical foundation: account model, messages, TVM, cells, shards, fees, nodes and explorers. Useful both for smart contract developers and application builders
• Smart contracts — for smart contract developers: Acton, Tolk and the surrounding toolchain
• Applications — for developers building applications on TON and Telegram Mini Apps: TON Connect, AppKit, TON Pay, WalletKit, APIs and SDKs

Each section now has its own sidebar and landing page with connected explanations of the tooling instead of one shared documentation tree. To support more flexible navigation and components than Mintlify (the previous documentation engine) allowed, the documentation was migrated to Fumadocs, a new open-source documentation framework.

Applications

The Applications section now includes a shared introduction connecting the tooling stack: AppKit (SDK for applications, Telegram Mini Apps and TON integrations), TON Connect (wallet connection protocol), TON Pay (payments) and WalletKit (SDK for wallets).

Full documentation with references and how-to guides was created for both AppKit and TON Connect.

TON Center

TON Center API reference was rebuilt around practical endpoint usage.

The sidebar and page layouts were updated, OpenAPI sections are now expanded by default so request parameters and response schemas are visible immediately without opening nested sections. The built-in playground now accepts requests without a token: developers can open the Get address balance page, press Send and see a mainnet response directly in the browser — without switching to Postman or generating an API key.

Search

Previously, search worked on a flat index: a match inside a page title and a mention of a term somewhere in a paragraph had the same weight. Because of this, search results often surfaced related but incorrect pages.

We rebuilt the search system from scratch, created benchmarks for common developer queries and added weighting for titles and keywords. Search now prioritizes page titles and section anchors. For example, queries like gasless or get coins now immediately return the correct page.

AI Agents и LLMS.TXT

To enable AI agents to interact with the documentation, we added docs.ton.org/llms.txt and docs.ton.org/llms-full.txt.

Every page now also has a /llms.mdx/*.md endpoint that returns content in a markdown format readable by AI agents and IDE assistants. Any reference page can now be passed to an AI agent with a single URL — without HTML wrappers or additional noise.

UX and stability

Hundreds of smaller improvements were shipped across the documentation:

• Main pages and section overviews — redesigned around the new structure so the entry flow matches what developers later see in the sidebar
• UI and components — moved some pixels around to make things nicer to look at
• Mobile experience — homepage cards now scroll horizontally with a soft fade effect and the logo no longer “jumps” during page transitions
• Redirects and broken links — redirects from old URLs were finalized after the migration and remaining broken links were cleaned up — old Google-indexed pages and external links now correctly lead to the new structure

What’s next

The MCP server and server-side search infrastructure are already ready for deployment. This will allow docs.ton.org to connect to IDE assistants and AI agents through a standard protocol. In parallel, an AI documentation assistant is already in development — currently one of the biggest requests from the community.

P.S. Under the hood, this update involved more than 250 commits in a single week.

Open docs.ton.org