Move mxpy to own directory

danielailie · danielailie · commit 04a909294f39 · 2025-06-05T14:58:25.000+03:00
diff --git a/docs/developers/data/code-metadata.md b/docs/developers/data/code-metadata.md
@@ -31,7 +31,7 @@ When deploying (or upgrading) a smart contract using **mxpy**, its default _code
 - `--metadata-payable` - mark the contract as `payable`
 - `--metadata-payable-by-sc` - mark the contract as `payable by smart contracts`
 
-For more information, please follow [mxpy CLI](/sdk-and-tools/sdk-py/mxpy-cli).
+For more information, please follow [mxpy CLI](/sdk-and-tools/mxpy/mxpy-cli).
 
 [comment]: # (mx-context-auto)
 
diff --git a/docs/developers/reproducible-contract-builds.md b/docs/developers/reproducible-contract-builds.md
@@ -174,7 +174,7 @@ A more straightforward alternative to the previous bash script is to use **mxpy*
 
 First, make sure you have the:
 
-- latest [mxpy](/sdk-and-tools/sdk-py/installing-mxpy) installed,
+- latest [mxpy](/sdk-and-tools/mxpy/installing-mxpy) installed,
 - latest [docker engine](https://docs.docker.com/engine/install/) installed.
 
 Then, use the `reproducible-build` command (below, the image tag is just an example):
@@ -227,11 +227,11 @@ Please note that as a **Beta** feature still in development, certain steps descr
 :::
 
 :::tip
-Make sure that you have the latest `mxpy` installed. In order to install mxpy, follow the instructions at [install mxpy](/sdk-and-tools/sdk-py/installing-mxpy).
+Make sure that you have the latest `mxpy` installed. In order to install mxpy, follow the instructions at [install mxpy](/sdk-and-tools/mxpy/installing-mxpy).
 :::
 
 1. The contract must be deterministically built as described [above](/developers/reproducible-contract-builds#building-via-docker-reproducible-build).
-2. To start with the verification process, we need to first deploy the smart contract. For deploying contracts have a look [here](/sdk-and-tools/sdk-py/smart-contract-interactions/#deploy--upgrade).
+2. To start with the verification process, we need to first deploy the smart contract. For deploying contracts have a look [here](/sdk-and-tools/mxpy/mxpy-cli#deploying-a-smart-contract).
 3. Upon deploying, the output will not only provide information such as the transaction hash and data, but also the address of the newly deployed contract.
 4. In order to verify your contract the command you have to use is (below, the image tag is just an example):
 
diff --git a/docs/developers/sc-calls-format.md b/docs/developers/sc-calls-format.md
@@ -128,7 +128,7 @@ There are multiple tools that one can use in order to convert an address into he
 
 ### Converting addresses using mxpy
 
-Make sure you have `mxpy` [installed](/sdk-and-tools/sdk-py/installing-mxpy).
+Make sure you have `mxpy` [installed](/sdk-and-tools/mxpy/installing-mxpy).
 
 ```bash
 mxpy wallet bech32 --decode erd1qyu5wthldzr8wx5c9ucg8kjagg0jfs53s8nr3zpz3hypefsdd8ssycr6th
diff --git a/docs/developers/setup-local-testnet.md b/docs/developers/setup-local-testnet.md
@@ -19,7 +19,7 @@ If not specified otherwise, the localnet starts with two shards plus the metacha
 
 ## Prerequisites: mxpy
 
-In order to install **mxpy**, follow [these instructions](/sdk-and-tools/sdk-py/installing-mxpy).
+In order to install **mxpy**, follow [these instructions](/sdk-and-tools/mxpy/installing-mxpy).
 
 :::note
 This guide assumes you are using `mxpy v9.7.1` or newer.
diff --git a/docs/sdk-and-tools/mxpy/installing-mxpy.md b/docs/sdk-and-tools/mxpy/installing-mxpy.md
diff --git a/docs/sdk-and-tools/mxpy/mxpy-cli.md b/docs/sdk-and-tools/mxpy/mxpy-cli.md
diff --git a/docs/sdk-and-tools/mxpy/smart-contract-interactions.md b/docs/sdk-and-tools/mxpy/smart-contract-interactions.md
@@ -28,7 +28,7 @@ Let's take the following example:
 
 ### mxpy
 
-We're going to use [**mxpy**](/sdk-and-tools/sdk-py/mxpy-cli) to deploy the contract. Follow the installation guide [here](/sdk-and-tools/sdk-py/installing-mxpy) - make sure to use the latest version available.
+We're going to use [**mxpy**](/sdk-and-tools/mxpy/mxpy-cli) to deploy the contract. Follow the installation guide [here](/sdk-and-tools/mxpy/installing-mxpy) - make sure to use the latest version available.
 
 [comment]: # (mx-context-auto)
 
diff --git a/docs/sdk-and-tools/overview.md b/docs/sdk-and-tools/overview.md
@@ -65,10 +65,8 @@ You might also want to have a look over [**xSuite**](https://xsuite.dev), a tool
 
 | Name                                                                             | Description                               |
 | -------------------------------------------------------------------------------- | ----------------------------------------- |
-| [mxpy](/sdk-and-tools/sdk-py/)                                                   | High level overview about mxpy.           |
-| [Installing mxpy](/sdk-and-tools/sdk-py/installing-mxpy)                         | How to install and get started with mxpy. |
-| [mxpy cli](/sdk-and-tools/sdk-py/mxpy-cli)                                       | How to use the Command Line Interface.    |
-| [Smart contract interactions](/sdk-and-tools/sdk-py/smart-contract-interactions) | Interact with Smart Contract.             |
+| [Installing mxpy](/sdk-and-tools/mxpy/installing-mxpy)                         | How to install and get started with mxpy. |
+| [mxpy cli](/sdk-and-tools/mxpy/mxpy-cli)                                       | How to use the Command Line Interface.    |
 
 [comment]: # (mx-context-auto)
 
diff --git a/docs/sdk-and-tools/sdk-py/sdk-py-cookbook-v1.md b/docs/sdk-and-tools/sdk-py/sdk-py-cookbook-v1.md
@@ -2,7 +2,7 @@
 id: sdk-py-cookbook
 title: Cookbook (v1)
 pagination_prev: sdk-and-tools/sdk-py/sdk-py-cookbook-v0
-pagination_next: sdk-and-tools/sdk-py/installing-mxpy
+pagination_next: sdk-and-tools/mxpy/installing-mxpy
 ---
 
 [comment]: # (mx-abstract)
diff --git a/docs/sovereign/software-dependencies.md b/docs/sovereign/software-dependencies.md
@@ -28,7 +28,7 @@ sudo pipx ensurepath --global
 
 ### mxpy
 
-Ensure you are using the latest version of mxpy. Follow the installation or upgrade instructions provided [here](/sdk-and-tools/sdk-py/installing-mxpy#install-using-pipx) if you haven't done so already.
+Ensure you are using the latest version of mxpy. Follow the installation or upgrade instructions provided [here](/sdk-and-tools/mxpy/installing-mxpy#install-using-pipx) if you haven't done so already.
 
 ### multiversx-sdk
 
diff --git a/docs/validators/staking/staking.md b/docs/validators/staking/staking.md
@@ -82,7 +82,7 @@ Make sure `mxpy` is installed by issuing this command on a terminal:
 mxpy --version
 ```
 
-If `mxpy` is not installed (`command not found`), please follow [these instructions](/sdk-and-tools/sdk-py/installing-mxpy).
+If `mxpy` is not installed (`command not found`), please follow [these instructions](/sdk-and-tools/mxpy/installing-mxpy).
 
 Make sure `mxpy` is installed and has the latest version before continuing.
 
diff --git a/docs/validators/staking/unjailing.md b/docs/validators/staking/unjailing.md
@@ -125,15 +125,15 @@ unJail@<BLS1>@<BLS2>@…@<BLS99>
 
 Submitting the unjailing transaction using `mxpy` avoids having to write the "Data" field manually. Instead, the transaction is constructed automatically by `mxpy` and submitted to the network directly, in a single command.
 
-Make sure `mxpy` is installed and has the latest version before continuing. If `mxpy` is not installed, please follow [these instructions](/sdk-and-tools/sdk-py/installing-mxpy).
+Make sure `mxpy` is installed and has the latest version before continuing. If `mxpy` is not installed, please follow [these instructions](/sdk-and-tools/mxpy/installing-mxpy).
 
 [comment]: # (mx-context-auto)
 
 ## **Your Wallet PEM file**
 
 To send transactions on your behalf _without_ using the online MultiversX Wallet, `mxpy` must be able to sign for you. For this reason, you have to generate a PEM file using your Wallet mnemonic.
 
-Please follow the guide [Deriving the Wallet PEM file](/sdk-and-tools/sdk-py/mxpy-cli). Make sure you know exactly where the PEM file was generated, because you'll need to reference its path in the `mxpy` commands.
+Please follow the guide [Deriving the Wallet PEM file](/sdk-and-tools/mxpy/mxpy-cli). Make sure you know exactly where the PEM file was generated, because you'll need to reference its path in the `mxpy` commands.
 
 After the PEM file was generated, you can issue transactions from `mxpy`directly.
 
diff --git a/docusaurus.config.js b/docusaurus.config.js
@@ -420,11 +420,15 @@ const config = {
           },
           {
             from: "/sdk-and-tools/sdk-py/configuring-mxpy",
-            to: "/sdk-and-tools/sdk-py/mxpy-cli",
+            to: "/sdk-and-tools/mxpy/mxpy-cli",
+          },
+          {
+            from: "/sdk-and-tools/sdk-py/mxpy-cli",
+            to: "/sdk-and-tools/mxpy/mxpy-cli",
           },
           {
             from: "/sdk-and-tools/sdk-py/deriving-the-wallet-pem-file",
-            to: "/sdk-and-tools/sdk-py/mxpy-cli",
+            to: "/sdk-and-tools/mxpy/mxpy-cli",
           },
           {
             from: "/developers/log-events/esdt-events",
diff --git a/sidebars.js b/sidebars.js
@@ -211,9 +211,14 @@ const sidebars = {
                       "sdk-and-tools/sdk-py/sdk-py-cookbook",
                     ]
                   },
-                  "sdk-and-tools/sdk-py/installing-mxpy",
-                  "sdk-and-tools/sdk-py/mxpy-cli",
-                  "sdk-and-tools/sdk-py/smart-contract-interactions",
+                ],
+              },
+              {
+                type: "category",
+                label: "Mxpy CLI",
+                items: [
+                  "sdk-and-tools/mxpy/installing-mxpy",
+                  "sdk-and-tools/mxpy/mxpy-cli",
                 ],
               },
               {
