created networks folder

packages/docs/pages/_meta.json

@@ -4,5 +4,5 @@
   "users": "User Guide",
   "operators": "Operator Guide",
   "integrating-with-namada" : "Integration Guide",
-  "testnets": "Testnets"
+  "networks": "Networks"
 }

packages/docs/pages/introduction/quick-start.mdx

@@ -18,7 +18,7 @@ If you build from source, and run `make install`, the binaries will be installed
 
 ## Joining a network
 
-See [the testnets page](./testnets.md) for details on how to join a testnet. The rest of this guide will assume you have joined a testnet chain using the `namadac utils join-network --chain-id <some-chain-id>` command.
+See [the testnets page](../networks/testnets.md) for details on how to join a testnet. The rest of this guide will assume you have joined a testnet chain using the `namadac utils join-network --chain-id <some-chain-id>` command.
 
 ## Run a ledger node
 

packages/docs/pages/introduction/troubleshooting.mdx

@@ -106,7 +106,7 @@ If you missed setting up as a validator pre-genesis, this means you must set up
 
 ### CometBFT
 
-When facing CometBFT issues as a validator, the most common cause of the issue is that we are running the wrong version of CometBFT. Keep an eye on the testnet docs [here](./introduction/testnets)
+When facing CometBFT issues as a validator, the most common cause of the issue is that we are running the wrong version of CometBFT. Keep an eye on the testnet docs [here](../networks/testnets.mdx)
 
 >Note that the common debug statement `Error reconnecting to peers` does not mean that your node is not working properly. Instead, it means there *exists at least one* validator on the network not working properly. To check whether this is a problem on your end, note the block height and see if it corresponds to the blockheight at [https://namada.world](https://namada.world)
 

packages/docs/pages/networks.mdx

@@ -0,0 +1,10 @@
+# Namada Netowrks
+
+This page is for namada networks.
+
+There are two network types:
+
+* [Mainnets](./networks/mainnets.mdx) - the main networks
+* [Testnets](./networks/testnets.mdx) - the test networks
+
+The mainnet chain-ids are prefixed with `main` and the testnet chain-ids are prefixed with `test`.

packages/docs/pages/networks/mainnets.mdx

@@ -0,0 +1,3 @@
+# Mainnets
+This page will be updated and filled wen mainnet is launched.
+

packages/docs/pages/users/fees.mdx

@@ -30,4 +30,4 @@ namada client transfer \
 
 (Assuming that `keysha2` exists and is in the wallet of the user)
 
-For testnet purposes, we recommend [using the faucet](../introduction/testnets/pow.md) to source NAM for transaction fees.
+For testnet purposes, we recommend [using the faucet](../networks/testnets/pow.md) to source NAM for transaction fees.

packages/docs/pages/users/wallet/web-wallet.mdx

@@ -6,9 +6,9 @@ When Namada is in `mainnet`, the web wallet will be available in most browser ex
 ### Installing from source (for development and experiment purposes)
 
 #### Connect to a testnet or run a local node
-1. Follow the instructions for the [testnets](../introduction/testnets.md) to connect to a testnet or set up a local node using [docker](../introduction/install/docker.md).
+1. Follow the instructions for the [testnets](../../networks/testnets.md) to connect to a testnet or set up a local node using [docker](../introduction/install/docker.md).
 2. Figure out where the base directory is stored and save its location as a variable such as `export BASE_DIR=<path/to/base/dir>`.
-   You can follow [these docs](../introduction/testnets/migrating-testnets.md#after-v0153) to save this variable. Go ahead and save the chain id as a variable as well. You can find the chain id by running `cat $BASE_DIR/global-config.toml`. Save this chain-id to the variable `export CHAIN_ID=<CHAIN_ID>`.
+   You can follow [these docs](../../networks/testnets/migrating-testnets.md#after-v0153) to save this variable. Go ahead and save the chain id as a variable as well. You can find the chain id by running `cat $BASE_DIR/global-config.toml`. Save this chain-id to the variable `export CHAIN_ID=<CHAIN_ID>`.
 3. You will need to edit the CometBFT config in order to allow the web wallet to connect to your node.
    The CometBFT config will be located in `$BASE_DIR/$CHAIN_ID/cometbft/config/config.toml`. You will need to change the `cors_allowed_origins` field to `["*"]`. You can do this by running
    ```shell copy