ton-org · anton-trunov · Oct 28, 2025 · Oct 28, 2025 · Oct 28, 2025 · Oct 28, 2025
diff --git a/guides/first-smart-contract.mdx → contract-dev/first-smart-contract.mdx b/guides/first-smart-contract.mdx → contract-dev/first-smart-contract.mdx
@@ -96,7 +96,7 @@ Every smart contract in TON is typically divided into three sections: **storage*
 - **Getters**: Provide read-only access to contract data without modifying state. For example, we’ll create a getter to return the current value of the counter.
 
 <Warning>
-  Due to the [TON architecture](/guides/from-ethereum#on-chain-get-methods), getters cannot be called from other contracts.
+  Due to the [TON architecture](/from-ethereum#on-chain-get-methods), getters cannot be called from other contracts.
   Inter-contract communication is possible only through **messages**.
 </Warning>
 

diff --git a/docs.json b/docs.json
@@ -37,39 +37,7 @@
     "pages": [
       "start-here",
       "get-support",
-      {
-        "group": "Step-by-step guides",
-        "pages": [
-          "guides/first-dapp",
-          "guides/first-smart-contract",
-          "guides/from-ethereum",
-          "guides/payment",
-          "guides/airdrop",
-          "guides/debug",
-          "guides/telegram",
-          "guides/tma",
-          "guides/react",
-          "guides/auth",
-          "guides/game",
-          "guides/dapp",
-          "guides/wallet",
-          "guides/cex",
-          {
-            "group": "Frontend",
-            "expanded": true,
-            "pages": []
-          },
-          {
-            "group": "Backend",
-            "pages": []
-          },
-          {
-            "group": "Mobile",
-            "pages": []
-          },
-          "guides/more"
-        ]
-      },
+      "from-ethereum",
       {
         "group": "Ecosystem",
         "pages": [
@@ -137,6 +105,8 @@
             "group": "TON Connect",
             "pages": [
               "ecosystem/ton-connect/index",
+              "ecosystem/ton-connect/dapp",
+              "ecosystem/ton-connect/wallet",
               "ecosystem/ton-connect/manifest",
               "ecosystem/ton-connect/message-lookup",
               {
@@ -342,6 +312,7 @@
       {
         "group": "Contract development",
         "pages": [
+          "contract-dev/first-smart-contract",
           {
             "group": "IDEs and editor plugins",
             "pages": [

diff --git a/ecosystem/interoperability/oracles/overview.mdx b/ecosystem/interoperability/oracles/overview.mdx
@@ -59,7 +59,7 @@ Read more: [Randomness in TON](/contract-dev/random)
 
 ## Oracles in TON
 
-Since the TON execution model is asynchronous, the classic ways to interact with oracles (get methods during transaction) can't be applied here. You can learn about the differences in ["Coming from Ethereum"](/guides/from-ethereum) article. The best pattern to retrieve data from an oracle is the [Request-Response pattern](/contract-dev/carry-value) - you send an internal message to the oracle contract and verify the response, getting the needed data.
+Since the TON execution model is asynchronous, the classic ways to interact with oracles (get methods during transaction) can't be applied here. You can learn about the differences in ["Coming from Ethereum"](/from-ethereum) article. The best pattern to retrieve data from an oracle is the [Request-Response pattern](/contract-dev/carry-value) - you send an internal message to the oracle contract and verify the response, getting the needed data.
 
 This model works well with pull oracles, since you can always guarantee the lowest possible latency for real-world data. If you use push oracle, you will still need to process two internal messages (request and response) to retrieve data. However, data relevance is limited by the data provider's up-time and pushing intervals: if the data provider pushes updated data every 10 minutes, you will commonly receive information that is outdated by 5 minutes. But using pull oracle, you can ensure pushes as often as your service needs by updating the data yourself.
 

diff --git a/ecosystem/rpc/price.mdx b/ecosystem/rpc/price.mdx
@@ -20,7 +20,7 @@ There is no established solution for real-time jetton swap market data; however,
 
 ## On-chain API
 
-Currently, it is not possible to retrieve **historical** jetton prices on-chain - since TON contracts [are limited by storage](/guides/from-ethereum#limited-contract-storage), it is quite hard to implement such an API fully on-chain. However, it is possible to retrieve **current** prices via the Request-Response pattern on some DEXes; refer to the specific service documentation to learn more about it.
+Currently, it is not possible to retrieve **historical** jetton prices on-chain - since TON contracts [are limited by storage](/from-ethereum#limited-contract-storage), it is quite hard to implement such an API fully on-chain. However, it is possible to retrieve **current** prices via the Request-Response pattern on some DEXes; refer to the specific service documentation to learn more about it.
 
 For example, on the [DeDust](https://dedust.io) DEX, it is possible to retrieve pool information on-chain using an internal message with the following [TL-B](/languages/TL-B/overview) schema:
 

diff --git a/guides/dapp.mdx → ecosystem/ton-connect/dapp.mdx b/guides/dapp.mdx → ecosystem/ton-connect/dapp.mdx
@@ -411,16 +411,16 @@ Discover wallet integration guides or explore complete examples:
 <Columns cols={2}>
   <Card
     title="Integrate a wallet"
-    href="/guides/wallet"
+    href="/ecosystem/ton-connect/wallet"
   />
 
   <Card
     title="WalletKit overview"
     href="/ecosystem/ton-connect/walletkit"
   />
 
-  <Card
-    title="CEX: Centralized EXchange"
-    href="/guides/cex"
-  />
+  {/* <Card
+      title="CEX: Centralized EXchange"
+      href="/guides/cex"
+    /> */}
 </Columns>
diff --git a/ecosystem/ton-connect/index.mdx b/ecosystem/ton-connect/index.mdx
@@ -63,13 +63,13 @@ Proceed with integration and usage recipes.
   <Card
     icon="flask"
     title="How to integrate a dApp with TON"
-    href="/guides/dapp"
+    href="/ecosystem/ton-connect/dapp"
   />
 
   <Card
     icon="wrench"
     title="Common usage examples"
-    href="/guides/dapp#usage"
+    href="/ecosystem/ton-connect/dapp#usage"
   />
 </Columns>
 
@@ -108,7 +108,7 @@ Follow the step-by-step guide.
 <Card
   icon="flask"
   title="How to make a wallet on TON"
-  href="/guides/wallet"
+  href="/ecosystem/ton-connect/wallet"
 />
 
 Or skim the related reference pages.
@@ -155,29 +155,29 @@ For more, see the TON Connect articles from Google Docs.
   />
 </Columns>
 
-## Complete integration recipes
+{/* ## Complete integration recipes
 
-Comprehensive guides that walk you through complete integration scenarios, covering everything from initial setup to production deployment. Each recipe includes code examples, best practices, and troubleshooting tips.
+  Comprehensive guides that walk you through complete integration scenarios, covering everything from initial setup to production deployment. Each recipe includes code examples, best practices, and troubleshooting tips.
 
-<Columns cols={1}>
+  <Columns cols={1}>
   <Card
     icon="flask"
     title="How to integrate TON into a Centralized Exchange (CEX)"
     href="/guides/cex"
   />
-</Columns>
+  </Columns> */}
 
-## Curated guides and tutorials from the community
+{/* ## Curated guides and tutorials from the community
 
-Tutorials and guides created by the TON community to help developers integrate TON into their applications. They provide practical, real-world examples and alternative approaches to common integration challenges.
+  Tutorials and guides created by the TON community to help developers integrate TON into their applications. They provide practical, real-world examples and alternative approaches to common integration challenges.
 
-<Columns cols={1}>
+  <Columns cols={1}>
   <Card
     icon="scroll"
     title="Index of curated community tutorials"
     href="/guides/more"
   />
-</Columns>
+  </Columns> */}
 
 ## Join the community
 

diff --git a/ecosystem/ton-connect/message-lookup.mdx b/ecosystem/ton-connect/message-lookup.mdx
@@ -7,7 +7,7 @@ import { Aside } from "/snippets/aside.jsx";
 <Aside
   type="danger"
 >
-  You should never use external message tracking for payment processing purposes. Check out [payment processing](/guides/payment) for more details.
+  You should never use external message tracking for payment processing purposes. Check out [payment processing](/processing/overview) for more details.
 </Aside>
 
 ## Introduction

diff --git a/guides/wallet.mdx → ecosystem/ton-connect/wallet.mdx b/guides/wallet.mdx → ecosystem/ton-connect/wallet.mdx
@@ -106,11 +106,11 @@ Discover app integration guides or explore complete examples:
 <Columns cols={2}>
   <Card
     title="Integrate a dApp"
-    href="/guides/dapp"
+    href="/ecosystem/ton-connect/dapp"
   />
 
-  <Card
-    title="CEX: Centralized EXchange"
-    href="/guides/cex"
-  />
+  {/* <Card
+      title="CEX: Centralized EXchange"
+      href="/guides/cex"
+    /> */}
 </Columns>
diff --git a/ecosystem/ton-connect/walletkit/index.mdx b/ecosystem/ton-connect/walletkit/index.mdx
@@ -21,7 +21,7 @@ First, follow this step-by-step guide:
 
 <Card
   title="How to integrate a wallet with TON"
-  href="/guides/wallet"
+  href="/ecosystem/ton-connect/wallet"
 />
 
 Then, follow relevant usage recipes:

diff --git a/guides/from-ethereum.mdx → from-ethereum.mdx b/guides/from-ethereum.mdx → from-ethereum.mdx
diff --git a/guides/airdrop.mdx b/guides/airdrop.mdx
diff --git a/guides/auth.mdx b/guides/auth.mdx
diff --git a/guides/cex.mdx b/guides/cex.mdx
diff --git a/guides/first-dapp.mdx b/guides/first-dapp.mdx
diff --git a/guides/game.mdx b/guides/game.mdx
diff --git a/guides/more.mdx b/guides/more.mdx
diff --git a/guides/payment.mdx b/guides/payment.mdx
diff --git a/guides/react.mdx b/guides/react.mdx
diff --git a/guides/telegram.mdx b/guides/telegram.mdx
diff --git a/guides/tma.mdx b/guides/tma.mdx
diff --git a/guides/usdt.mdx b/guides/usdt.mdx
diff --git a/index.mdx b/index.mdx
@@ -147,13 +147,13 @@ export const JourneyStep = ({ title, icon, iconType, href, cta, children }) => {
       </p>
     </div>
     <Columns cols={4}>
-      <Card
+      {/* <Card
         title="Step-by-step guides"
         icon="shoe-prints"
         iconType="solid"
         href="/guides/first-dapp"
         cta="Your first dApp"
-      />
+      /> */}
       <Card
         title="Ecosystem"
         icon="leaf"
@@ -249,20 +249,20 @@ export const JourneyStep = ({ title, icon, iconType, href, cta, children }) => {
         title="Writing your first smart contract"
         icon="4"
         iconType="solid"
-        href="/guides/first-smart-contract"
+        href="/contract-dev/first-smart-contract"
       />
       <JourneyStep
         title="What is a dApp?"
         icon="5"
         iconType="solid"
         href="/foundations/glossary#decentralized-application-dapp"
       />
-      <JourneyStep
+      {/* <JourneyStep
         title="Your first dApp on TON"
         icon="6"
         iconType="solid"
         href="/guides/first-dapp"
-      />
+      /> */}
     </Journey>
     <Journey
       title="Nomad"
@@ -272,18 +272,18 @@ export const JourneyStep = ({ title, icon, iconType, href, cta, children }) => {
         title="Coming from Ethereum"
         icon="ethereum"
         iconType="solid"
-        href="/guides/from-ethereum"
+        href="/from-ethereum"
       >
         Compare the execution model and the ecosystem of TON
       </JourneyStep>
-      <JourneyStep
+      {/* <JourneyStep
         title="Your first TON dApp"
         icon="mobile-notch"
         iconType="solid"
         href="/guides/first-dapp"
       >
         From nothing to a deployed and working contract with a web frontend
-      </JourneyStep>
+      </JourneyStep> */}
     </Journey>
     <Journey
       title="Ace"

diff --git a/languages/func/index.mdx b/languages/func/index.mdx
@@ -99,7 +99,7 @@ The [TON Blockchain course](https://stepik.org/course/176754/) covers FunC and s
 >
   I cannot find where the "Introduction" page is in the new docs!!!!!!!
 
-  The best place to start developing with FunC is the [Introduction](/guides/first-smart-contract) section.
+  The best place to start developing with FunC is the [Introduction](/contract-dev/first-smart-contract) section.
 </Aside>
 
 Below, you can find additional materials shared by community experts:

diff --git a/standard/tokens/jettons/how-to-get-wallet-data.mdx b/standard/tokens/jettons/how-to-get-wallet-data.mdx
@@ -5,8 +5,7 @@ sidebarTitle: "Get Jetton wallet data"
 
 import { Image } from '/snippets/image.jsx';
 
-To retrieve the Jetton wallet's account jetton amount, owner identification information, and other details related to a specific Jetton wallet contract,
-use the `get_wallet_data()` [get method](/guides/first-smart-contract#6-2-reading-contract-data-with-get-methods) within the Jetton wallet contract.
+To retrieve the Jetton wallet's account jetton amount, owner identification information, and other details related to a specific Jetton wallet contract, use the `get_wallet_data()` [get method](/foundations/messages/overview) within the Jetton wallet contract.
 
 This method returns the following data:
 

diff --git a/standard/wallets/comparison.mdx b/standard/wallets/comparison.mdx
@@ -2,7 +2,7 @@
 title: "Comparison"
 ---
 
-[Unlike some other blockchains](/guides/from-ethereum), wallets in TON are represented as distinct smart contracts. They handle transaction signing, replay protection, and even gasless transfers. Different wallet versions implement different custom logic, suitable for various use cases.
+[Unlike some other blockchains](/from-ethereum), wallets in TON are represented as distinct smart contracts. They handle transaction signing, replay protection, and even gasless transfers. Different wallet versions implement different custom logic, suitable for various use cases.
 
 This article will cover the differences between these wallets and identify the best pick for each task.
 

diff --git a/standard/wallets/history.mdx b/standard/wallets/history.mdx
@@ -13,7 +13,7 @@ In this article, we will explore the various versions and modifications of TON w
 
 We should first understand that wallets are not a specific entity in the TON ecosystem. They are still just smart contracts consisting of code and data, and in that sense, are equal to any other actor (i.e., smart contract) in TON.
 
-Read more about [differences](/guides/from-ethereum).
+Read more about [differences](/from-ethereum).
 
 Like your own custom smart contract, or any other one, wallets can receive external and internal messages, send internal messages and logs, and provide `get methods`.
 So the question is: what functionality do they provide, and how do they differ between versions?