more v2 -> v3 structure migration

docs/about/products/astar-portal/index.md

@@ -0,0 +1,7 @@
+---
+title: Astar Portal
+---
+
+# Overview
+
+About Astar Portal. [INSERT]

docs/about/products/astar-portal/troubleshooting.md

@@ -0,0 +1,36 @@
+---
+sidebar_position: 16
+---
+
+# Portal Troubleshooting Guide
+
+This section will guide you to troubleshoot and solve most issues when connecting to the portal.
+
+## Can't Connect Wallet To The Portal
+
+**Allow Polkadot.js to access the portal**
+1. Go to Polkadot.js browser extension.
+2. Click on the `Gear` icon.
+3. Click on `Manage Website Access`.
+4. Make sure `https://portal.astar.network` is allowed.
+
+**Allow Polkadot.js to be used on Astar/Shiden**
+1. Go to Polkadot.js browser extension.
+2. Click on the `3 dots`.
+3. On the dropdown menu, select `Allow use on any chain`.
+4. If you have other extensions installed, please revoke access of those extensions.
+
+## Getting Errors Or Unable To Execute Certain Functions
+Some of you may be unable to execute certain funtions. Please try these steps.
+1. Update metadata (if required).
+2. Clear cache, restart browser and connect wallet to the portal again.
+3. On the top right corner, switch to a different endpoint.
+4. Brave browser is known to give errors. Use Chrome or Firefox instead.
+5. Use VPN.
+
+## Unable To Claim Staking Rewards
+1. If you can't claim the staking rewards on the portal. Visit [HERE](https://docs.astar.network/docs/use/user-guides/manual_claim).
+2. If the transferrable balance in the wallet is too low, you might not be able to claim the staking rewards. Top up your wallet or turn off `auto-restake` and then claim the rewards. Turning off `auto-restake` reduces the amount of transactions therefore reducing the amount of gas needed.
+
+
+If none of the above is helpful, please contact any of the team members or ambassadors on [Discord](https://discord.gg/2FGq5KqwBh).

docs/build/build-on-layer-1/smart-contracts/EVM/infra/verify_smart_contract.md

@@ -34,7 +34,7 @@ Due to compiler constraints, contracts **with OpenZeppelin-related source contra
 In this section, we will go through the process of verifying a smart contract **without OpenZeppelin-related source contracts.** 
 In the previous guide, we went through the process of using Remix IDE to deploy a smart contract on Astar EVM. Let's start from there:
 
-[How to use Remix IDE to deploy an on-chain storage contract on Astar EVM | Astar Docs](/docs/build/build-on-layer-1/builder-guides/astar_features/use_remix.md)
+[How to use Remix IDE to deploy an on-chain storage contract on Astar EVM | Astar Docs](/docs/build/builder-guides/layer-1/evm/astar_features/use_remix.md)
 
 Copy the deployed contract address under the `Deployed Contracts` section
 

docs/build/build-on-layer-1/smart-contracts/EVM/precompiles/xcm/xcm.md

@@ -244,5 +244,5 @@ XCM.Multilocation memory asset = XCM.Multilocation({
 Three builder guides on the subject of EVM XCM are available in Builder section:
 
 - [How to create and interact with a mintable XC20 asset via Solidity smart contract](https://docs.astar.network/build/build-on-layer-1/builder-guides/leverage_parachains/interact_with_xc20.md)   
-- [Harnessing Crust Network for NFT Minting: A Developer's Guide](/docs/build/build-on-layer-1/builder-guides/leverage_parachains/mint-nfts-crust.md)   
-- [How to set up a Zombienet for XCM testing](/docs/build/build-on-layer-1/builder-guides/leverage_parachains/zombienet.md)  
+- [Harnessing Crust Network for NFT Minting: A Developer's Guide](/docs/build/builder-guides/layer-1/evm/leverage_parachains/mint-nfts-crust.md)   
+- [How to set up a Zombienet for XCM testing](/docs/build/builder-guides/layer-1/evm/leverage_parachains/zombienet.md)  

docs/build/build-on-layer-1/smart-contracts/building-cross-chain-contracts/xcm/integration/add-to-portal.md

@@ -101,4 +101,4 @@ const xcmToken = {
 2. Deposit and withdrawal functions have additionally been tested with the `minBridgeAmount`.
 3. You've tested withdrawal of assets to accounts that have 0 balance of the assets being withdrawn (to check whether `minBridgeAmount` is higher than `Existential Deposit` defined on the origin chain).
 4. You've included Subscan link(s) to the XCM transaction details, for each of the assets you've registered.
-5. And finally, have deployed the forked app, and submitted the staging URL [ref](/docs/build/build-on-layer-1/builder-guides/integration_toolings/deploy-astar-portal.md).
+5. And finally, have deployed the forked app, and submitted the staging URL [ref](/docs/build/builder-guides/layer-1/evm/integration_toolings/deploy-astar-portal.md).

docs/build/build-on-layer-1/builder-guides/astar_features/astarBase.md → docs/build/builder-guides/layer-1/evm/astar_features/astarBase.md

@@ -399,6 +399,6 @@ That’s a wrap! Happy hacking!
 
 ## Reference
 
-- Official Guide for AstarBase](/docs/build/build-on-layer-1/builder-guides/astar_features/astarBase.md/)
+- Official Guide for AstarBase](/docs/build/builder-guides/layer-1/evm/astar_features/astarBase.md/)
 - Official Document for creating a React app:
    - [https://reactjs.org/docs/create-a-new-react-app.html](https://reactjs.org/docs/create-a-new-react-app.html)

docs/build/build-on-layer-1/builder-guides/hacking/hack_evm.md → docs/build/builder-guides/layer-1/evm/hacking/hack_evm.md

@@ -12,7 +12,7 @@ Read the linked chapters or use tutorials to be able to answer following questio
 
 ## Setup MetaMask and Remix
 * Did you install and connect your MetaMask to Shibuya? Which `Chain Id` did you use to setup Shibuya Network in MetaMask?
-* Connect to browser IDE Remix using this [tutorial](/docs/build/build-on-layer-1/builder-guides/astar_features/use_remix.md)
+* Connect to browser IDE Remix using this [tutorial](/docs/build/builder-guides/layer-1/evm/astar_features/use_remix.md)
 * Does your environment look like this:
 
 <Figure src={require('./img/custom_net.png').default } width="400px" />
@@ -29,7 +29,7 @@ Since it's inception, Solidity has become mainstream language for smart contract
 
 ## Setup Hardhat and Truffle
 The Truffle and Hardhat are preferred tools to develop, deploy and test smart contract. For this guide we will pick Hardhat.
-Setup your Hardhat environment using [How to use Hardhat to deploy on Shibuya](/docs/build/build-on-layer-1/builder-guides/astar_features/use_hardhat.md).
+Setup your Hardhat environment using [How to use Hardhat to deploy on Shibuya](/docs/build/builder-guides/layer-1/evm/astar_features/use_hardhat.md).
 
 
-What is [next](/docs/build/build-on-layer-1/builder-guides/hacking/next.md)? 
+What is [next](/docs/build/builder-guides/layer-1/evm/hacking/next.md)? 

docs/build/build-on-layer-1/builder-guides/hacking/hack_wasm.md → docs/build/builder-guides/layer-1/evm/hacking/hack_wasm.md

@@ -30,7 +30,7 @@ Please note that the current version of polkadot-JS is broken for contracts beca
 
 :::
 
-## From Zero to ink Hero [Tutorials](/docs/build/build-on-layer-1/smart-contracts/wasm/from-zero-to-ink-hero/flipper-contract/flipper.md)
+## From Zero to ink Hero [Tutorials](/docs/build/builder-guides/layer-1/wasm/from-zero-to-ink-hero/flipper-contract/flipper.md)
 Depending on your confidence, use any of these tutorial. If you are just starting, the Flipper contract is the way to go.
 * Your task is to deploy the contract from the tutorial to Shibuya Network.
   * After you build contract notice where the `.contract` and `metadata.json` are created.
@@ -40,4 +40,4 @@ Depending on your confidence, use any of these tutorial. If you are just startin
   * Use Polkadot-JS UI to reload same contract you just deployed using Contracts-UI.
 
 
-What is [next](/docs/build/build-on-layer-1/builder-guides/hacking/next.md)? 
+What is [next](/docs/build/builder-guides/layer-1/evm/hacking/next.md)? 

docs/build/build-on-layer-1/builder-guides/leverage_parachains/interact_with_xc20.md → docs/build/builder-guides/layer-1/evm/leverage_parachains/interact_with_xc20.md

@@ -124,7 +124,7 @@ In order to confirm receiving the asset on EVM, we need to add the specific asse
 - Convert the `asset ID` from hexadecimal to decimal
 - Add the prefix of `0xffffffff`
     - for example, our Cookbook Token, CKT, has `asset ID` of `229`. Following the step above, we will have the converted address of `0xffffffff000000000000000000000000000000E5`.
-- More information can be found in the following guide: [Send XC20 Assets to EVM](/docs/build/build-on-layer-1/builder-guides/leverage_parachains/interact_with_xc20.md#send-the-asset-to-evm)
+- More information can be found in the following guide: [Send XC20 Assets to EVM](/docs/build/builder-guides/layer-1/evm/leverage_parachains/interact_with_xc20.md#send-the-asset-to-evm)
 
 ![Untitled](mintable-xc20-cookbook/Untitled%207.png) 
 

docs/build/build-on-layer-1/smart-contracts/wasm/from-zero-to-ink-hero/flipper-contract/flipper.md → docs/build/builder-guides/layer-1/wasm/from-zero-to-ink-hero/flipper-contract/flipper.md

@@ -297,5 +297,5 @@ impl Flipper {
 ### Compile, Deploy and Interact with Contracts
 
 
-Follow this guide to deploy your contract [using Polkadot UI](https://docs.astar.network/docs/build/build-on-layer-1/smart-contracts/wasm/tooling/polkadotjs/). Once deployed, you will be able to interact with it.
+Follow this guide to deploy your contract [using Polkadot UI](https://docs.astar.network/docs/build/builder-guides/layer-1/wasm/tooling/polkadotjs/). Once deployed, you will be able to interact with it.
 

docs/build/build-on-layer-1/smart-contracts/wasm/from-zero-to-ink-hero/nft/Wizard/index.md → docs/build/builder-guides/layer-1/wasm/from-zero-to-ink-hero/nft/Wizard/wizard.md

@@ -5,7 +5,7 @@
 To create a smart contract which follows PSP34 standard use Openbrush Wizard:
 1. Open [Openbrush.io](https://openbrush.io/) website and go to bottom of the page.
 2. Select PSP34.
-3. Select the version to match the rest of the tutorial. Check *What will be used* in the [opening chapter](/docs/build/build-on-layer-1/smart-contracts/wasm/from-zero-to-ink-hero/nft/nft.md#what-will-be-used).
+3. Select the version to match the rest of the tutorial. Check *What will be used* in the [opening chapter](/docs/build/builder-guides/layer-1/wasm/from-zero-to-ink-hero/nft/nft.md#what-will-be-used).
 4. Name your contract. In this tutorial we will use `Shiden34`.
 5. Add your symbol name. In this tutorial we will use `SH34`.
 6. Select extensions: *Metadata*, *Mintable*, *Enumerable*.

docs/build/build-on-layer-1/smart-contracts/wasm/from-zero-to-ink-hero/nft/nft.md → docs/build/builder-guides/layer-1/wasm/from-zero-to-ink-hero/nft/nft.md

@@ -34,7 +34,7 @@ To follow this tutorial you will need:
 - Event handling.
 
 ## Summary
-[I. OpenBrush wizard](./Wizard/index.md)   
+[I. OpenBrush wizard](./Wizard/wizard.md)   
 [II. Override mint() method](./Override/override.md)   
 [III Custom Trait for mint()](./CustomTrait/customtrait.md)   
 [IV. PayableMint Trait definition](./PayableMintTrait/payableminttrait.md)