Nialexsan/v3 guides move

docs/build/getting-started/explore-more.mdx

@@ -16,7 +16,7 @@ Below are some additional tutorials to help you get started with Flow:
   {
     type: 'link',
     label: 'Flow App Quickstart',
-    href: '/guides/flow-app-quickstart',
+    href: '/build/guides/flow-app-quickstart',
     description: 'Simple walkthrough building a web3 app using the Flow Client Library (FCL)',
     customProps: {
       icon: <FontAwesomeIcon icon={faWindowMaximize} className="h-16" />,
@@ -30,7 +30,7 @@ Below are some additional tutorials to help you get started with Flow:
   {
     type: 'link',
     label: 'Fungible Token Guide',
-    href: '/guides/fungible-token',
+    href: '/build/guides/fungible-token',
     description: 'Steps to create, deploy, mint, and transfer fungible tokens on Flow',
     customProps: {
       icon: <FontAwesomeIcon icon={faCoins} className="h-16" />,
@@ -58,7 +58,7 @@ Below are some additional tutorials to help you get started with Flow:
   {
     type: 'link',
     label: 'Walkthrough Guides',
-    href: '/guides/flow-app-quickstart',
+    href: '/build/guides/flow-app-quickstart',
     description: 'Longer form guides to help you get started with Flow',
     customProps: {
       icon: <FontAwesomeIcon icon={faBook} className="h-16" />,

docs/build/getting-started/quickstarts/fcl-quickstart.md

@@ -138,4 +138,4 @@ You just built an app on Flow!
 
 ## Mutating Chain State and More
 
-For a deeper dive into writing an FCL app, such as how to change the chain state with FCL, check out [this guide](../../../guides/flow-app-quickstart.md) or the [FCL documentation](../../../tools/clients/fcl-js/index.md).
+For a deeper dive into writing an FCL app, such as how to change the chain state with FCL, check out [this guide](../../guides/flow-app-quickstart.md) or the [FCL documentation](../../../tools/clients/fcl-js/index.md).

docs/guides/flow-app-quickstart.md → docs/build/guides/flow-app-quickstart.md

@@ -14,7 +14,7 @@ sidebar_custom_props:
 This guide is a simple walkthrough to get started building a web3 app using the Flow Client Library (FCL).
 
 <Callout type="info">
- If you are looking for a scalfolds, check out [scaffolds available in the Flow CLI](../tools/flow-cli/super-commands.md#using-scaffolds).
+If you are looking for a scalfolds, check out [scaffolds available in the Flow CLI](../../tools/flow-cli/super-commands.md#using-scaffolds).
 </Callout>
 
 This simple guide uses the "Hello World" scaffold, it is meant to provide all the code needed to get a web application up and running.
@@ -24,10 +24,10 @@ This simple guide uses the "Hello World" scaffold, it is meant to provide all th
 ![Flow app anatomy](flow-dapp-anatomy.png)
 
 <Callout type="info">
-FCL (aka Flow Client Library) wraps the logic needed to communicate with the Flow blockchain. It's a npm package, [More Information](../tools/clients/fcl-js)
+FCL (aka Flow Client Library) wraps the logic needed to communicate with the Flow blockchain. It's a npm package, [More Information](../../tools/clients/fcl-js)
 </Callout>
 
-This guide assumes a good understanding of React. The concepts are easy to understand and apply to other libraries and framework. A strong understanding of Cadence (Flow's smart contract language) is not required. More information on Cadence, [learning the Cadence language](../build/cadence.md).
+This guide assumes a good understanding of React. The concepts are easy to understand and apply to other libraries and framework. A strong understanding of Cadence (Flow's smart contract language) is not required. More information on Cadence, [learning the Cadence language](../cadence.md).
 
 ### FCL concepts covered:
 
@@ -42,7 +42,7 @@ For more help, [Discord](https://discord.gg/flow). See links at the end of this
 
 ## Installation
 
-Make sure you have Flow CLI installed. [installation instructions](../tools/flow-cli/install.md).
+Make sure you have Flow CLI installed. [installation instructions](../../tools/flow-cli/install.md).
 
 ## Configuration
 
@@ -58,7 +58,7 @@ npm install
 # run the app in a later step
 ```
 
-We don't recommend keeping private keys in your `flow.json`, notice that Flow CLI already moved the emulator private key to a `emulator.key` file and point to it using the [key/location pattern](../tools/flow-cli/flow.json/security.md#private-account-configuration-file). This file should be added to your `.gitignore` file, so it won't be committed to your repository. 
+We don't recommend keeping private keys in your `flow.json`, notice that Flow CLI already moved the emulator private key to a `emulator.key` file and point to it using the [key/location pattern](../../tools/flow-cli/flow.json/security.md#private-account-configuration-file). This file should be added to your `.gitignore` file, so it won't be committed to your repository. 
 
 We won't be using emulator and running contracts locally in this quickstart, but FCL will complain if it finds private keys in your `flow.json` file.
 
@@ -85,7 +85,7 @@ Your `flow.json` file should look like this:
 ```
 
 <Callout type="info">
-The `flow.json` file is used to keep track of deployed contracts and accounts. [More Information](../tools/clients/fcl-js/api#using-flowjson)
+The `flow.json` file is used to keep track of deployed contracts and accounts. [More Information](../../tools/clients/fcl-js/api#using-flowjson)
 </Callout>
 
 
@@ -104,7 +104,7 @@ The `hello-world` web application comes with convenience npm commands to facilit
   3. Start web app
 
 <Callout type="info">
-Emulator is a local blockchain [More Information](../tools/emulator/index.md). Emulator has all the features as testnet and mainnet blockchains 
+Emulator is a local blockchain [More Information](../../tools/emulator/index.md). Emulator has all the features as testnet and mainnet blockchains 
 </Callout>
 
 ```sh
@@ -113,12 +113,12 @@ npm run dev:local
 
 Now that your app is running. FCL loads the configuration in `config/fcl.ts` This file contains configuration information for FCL, such as what Access Node and wallet discovery endpoint and which network to use (e.g. testnet or a local emulator). 
 
-- `accessNode.api` key specifies the address of a Flow access node. There are publically available access nodes, but have to rate limit. Alternatively, applications might want to run an Observer node [Run a Node](../references/run-and-secure/node-operation/observer-node.mdx).
+- `accessNode.api` key specifies the address of a Flow access node. There are publically available access nodes, but have to rate limit. Alternatively, applications might want to run an Observer node [Run a Node](../../references/run-and-secure/node-operation/observer-node.mdx).
 - `discovery.wallet` is an address that points to a service that lists FCL compatible wallets. Flow's FCL Discovery service is a service that FCL wallet providers can be added to, and be made 'discoverable' to any application that uses the `discovery.wallet` endpoint.
 
 Also, notice that `package.json` uses `NEXT_PUBLIC_FLOW_NETWORK=local` for `dev` command, this is used to set the network in `config/fcl.ts`.
 <Callout type="info">
-Learn more about [configuring Discovery](../tools/clients/fcl-js/discovery.mdx) or [setting configuration values](../tools/clients/fcl-js/api.md#setting-configuration-values).
+Learn more about [configuring Discovery](../../tools/clients/fcl-js/discovery.mdx) or [setting configuration values](../../tools/clients/fcl-js/api.md#setting-configuration-values).
 </Callout>
 
 The main Next.js app component is located in `pages/_app.tsx`. It should import the config file `config/fcl.ts` already and should look like this:
@@ -194,11 +194,11 @@ The web app will run, but there are no contracts deployed to local emulator. Thi
 
 Note: in the code above `useCurrentUser` is used to determine if there is a logged in user. 
 
-There are two methods to allow the user to login. `fcl.logIn()` or `fcl.authenticate()` [More Information on, authenticate](../tools/clients/fcl-js/api#authenticate)
+There are two methods to allow the user to login. `fcl.logIn()` or `fcl.authenticate()` [More Information on, authenticate](../../tools/clients/fcl-js/api#authenticate)
 
 In `components/Navbar.tsx` a button wires up the authentication method `fcl.authenticate()`. It is used to bring up the list of supported wallets. See below
 
-Once authenticated, FCL uses a hook `const user = useCurrentUser()` to get the user data, when user is signed in `user.loggedIn` flag is `true`. For more information on the `currentUser`, read more [here](../tools/clients/fcl-js/api.md#current-user).
+Once authenticated, FCL uses a hook `const user = useCurrentUser()` to get the user data, when user is signed in `user.loggedIn` flag is `true`. For more information on the `currentUser`, read more [here](../../tools/clients/fcl-js/api.md#current-user).
 
 ```jsx
 import Head from 'next/head'
@@ -304,7 +304,7 @@ Verify that `flow.json` updates with HelloWorld contract information, `contracts
 }
 ```
 
-For more information on deployments check [Flow CLI](../tools/flow-cli/flow.json/manage-configuration.md) documentation
+For more information on deployments check [Flow CLI](../../tools/flow-cli/flow.json/manage-configuration.md) documentation
 
 ## Query the Blockchain
 
@@ -383,11 +383,11 @@ That's it! You now have Flow app that uses auth, query and mutate the chain. Thi
 - [Beginner Example: CryptoDappy](https://github.com/bebner/crypto-dappy)
 
 **More FCL**
-- [FCL API Quick Reference](../tools/clients/fcl-js/api)
-- [More on Scripts](../tools/clients/fcl-js/scripts.mdx)
-- [More on Transactions](../tools/clients/fcl-js/transactions.mdx)
-- [User Signatures](../tools/clients/fcl-js/user-signatures.mdx)
-- [Proving Account Ownership](../tools/clients/fcl-js/proving-authentication.mdx)
+- [FCL API Quick Reference](../../tools/clients/fcl-js/api)
+- [More on Scripts](../../tools/clients/fcl-js/scripts.mdx)
+- [More on Transactions](../../tools/clients/fcl-js/transactions.mdx)
+- [User Signatures](../../tools/clients/fcl-js/user-signatures.mdx)
+- [Proving Account Ownership](../../tools/clients/fcl-js/proving-authentication.mdx)
 
 **Other**
-- [Flow Developer Onboarding Guide](/tutorials/intro.md)
+- [Flow Developer Onboarding Guide](../../tutorials/intro.md)

docs/guides/flow-cli.md → docs/build/guides/flow-cli.md

@@ -50,7 +50,7 @@ To install a specific version of Flow CLI newer than v0.42.0, append the version
 sh -ci "$(curl -fsSL https://raw.githubusercontent.com/onflow/flow-cli/master/install.sh)" -- v0.44.0
 ```
 
-To install a version older than v0.42.0, refer to [Installing versions before 0.42.0](../tools/flow-cli/install.md#installing-versions-before-0420) below.
+To install a version older than v0.42.0, refer to [Installing versions before 0.42.0](../../tools/flow-cli/install.md#installing-versions-before-0420) below.
 
 ## Windows
 
@@ -109,4 +109,4 @@ And then the flow dev:
 
 ### Next steps
 
-As part of the next steps you can read more about [flow dev command](../tools/flow-cli/super-commands.md).
+As part of the next steps you can read more about [flow dev command](../../tools/flow-cli/super-commands.md).

docs/guides/smart-contracts/deploying.mdx → docs/build/guides/smart-contracts/deploying.md

@@ -16,76 +16,76 @@ Make sure you handle your mainnet account keys appropriately. Using a Key Manage
 ### Creating an Account
 
 There are two simple methods of creating an account on testnet. **Interactive** and **Manual**, both use the Flow CLI. On mainnet you will have to fund your newly created account, there is no faucet.
-Make sure to install the Flow CLI. [Flow CLI](../../tools/flow-cli/accounts/create-accounts) has a interactive mode for generating keys.
+Make sure to install the Flow CLI. [Flow CLI](../../../tools/flow-cli/accounts/create-accounts) has a interactive mode for generating keys.
 
 <Callout type="success">
 Anyone can deploy and update contracts on mainnet. Audits are encouraged but not mandatory to deploying contracts to mainnet. Take every precauction to reduce issues and protect users. 
 </Callout>
 
 ### Create and deploy a mainnet project
-The tool of choice is Flow CLI, there are quickstarts and guides that use Flow CLI, [Getting Started](../../build/getting-started/quickstarts/flow-cli)
-- It is highly encouraged to test your contracts, transactions and scripts on Testnet, have strong smart contract test coverage and follow any additional guidelines set out here: [Smart Contract Testing Guidelines](./testing). 
-- Follow the Flow CLI instructions to [Create a Project](../../tools/flow-cli/). You have the Flow CLI installed and ran `flow init` or `flow setup` in your project folder and generating a `flow.json` file
+The tool of choice is Flow CLI, there are quickstarts and guides that use Flow CLI, [Getting Started](../../getting-started/quickstarts/flow-cli)
+- It is highly encouraged to test your contracts, transactions and scripts on Testnet, have strong smart contract test coverage and follow any additional guidelines set out here: [Smart Contract Testing Guidelines](./testing.md). 
+- Follow the Flow CLI instructions to [Create a Project](../../../tools/flow-cli/index.md). You have the Flow CLI installed and ran `flow init` or `flow setup` in your project folder and generating a `flow.json` file
 - Mainnet account: You completed the mainnet account setup, (see above) and have your key pair and mainnet address ready.
-- [Deploy your project](../../tools/flow-cli/deployment/deploy-project-contracts.md), notice that your account now has contracts deployed on mainnet.
-- [Deploy a contract](../../tools/flow-cli/accounts/account-add-contract.md) to mainnet. You can deploy contracts individually using the `account-add-contract` command.
+- [Deploy your project](../../../tools/flow-cli/deployment/deploy-project-contracts.md), notice that your account now has contracts deployed on mainnet.
+- [Deploy a contract](../../../tools/flow-cli/accounts/account-add-contract.md) to mainnet. You can deploy contracts individually using the `account-add-contract` command.
 
 <Callout type="info">
 All your contract deployment addresses are stored in `flow.json`. Mainnet, Testnet and local (emulator) are stored as well.
 </Callout>
 
 ### Deploy updated contracts on mainnet
 
-Contracts can be updated and retain the contract address. You can use the [Flow CLI contract update command](../../tools/flow-cli/accounts/account-update-contract.md) to re-deploy an updated version of your contract:
+Contracts can be updated and retain the contract address. You can use the [Flow CLI contract update command](../../../tools/flow-cli/accounts/account-update-contract.md) to re-deploy an updated version of your contract:
 
 <Callout type="warning">
 If you see `Error Code: 1103`, your new account does not have enough funds to complete the transaction. Make sure you have enough FLOW and your account is set up correctly, check [Flowdiver](https://flowdiver.io/) to verify.
 </Callout>
 
-Once all your contracts are deployed, you can visit [flow-view-source](https://flow-view-source.com/) or run the [Flow CLI get account command](../../tools/flow-cli/accounts/get-accounts.md) to confirm the deployment.
+Once all your contracts are deployed, you can visit [flow-view-source](https://flow-view-source.com/) or run the [Flow CLI get account command](../../../tools/flow-cli/accounts/get-accounts.md) to confirm the deployment.
 
 ### Sporks
 
-Currently, **historical event data is not migrated between sporks,** so you'll need to design your application with this in mind. We recognize the usefulness of historical event data and plan on adding a means of accessing it in the near future. Past spork transactional data is available, [See Previous Spork Access Node Info](../../references/run-and-secure/node-operation/past-sporks)
+Currently, **historical event data is not migrated between sporks,** so you'll need to design your application with this in mind. We recognize the usefulness of historical event data and plan on adding a means of accessing it in the near future. Past spork transactional data is available, [See Previous Spork Access Node Info](../../../references/run-and-secure/node-operation/past-sporks)
 
-More Information on [Sporks](../../references/run-and-secure/node-operation/spork)
+More Information on [Sporks](../../../references/run-and-secure/node-operation/spork)
 
 
 ### Testnet
 
 
 The Flow test network, known as Flow Testnet, exists to help developers test their software and smart contracts against a live network. It's also used as a means of releasing and testing new protocol and smart contract features before they are integrated into Flow's main network (Mainnet).
 
-When the Flow protocol is updated or a new version of Cadence is released, those updates will always be made available on the [Flow Emulator](../../tools/emulator) _before_ they're integrated into Flow Testnet or Flow Mainnet. 
+When the Flow protocol is updated or a new version of Cadence is released, those updates will always be made available on the [Flow Emulator](../../../tools/emulator) _before_ they're integrated into Flow Testnet or Flow Mainnet. 
 
 ## Getting Started on Testnet
 
 If you need to create a flow.json file to store information about accounts and contracts use the `flow init` command to create a project
 <Callout type="info">
-To create accounts and generate keys, make sure to install [Flow CLI](../../tools/flow-cli/install). Flow CLI provides convenient functions to simplifies interacting with the blockchain.
+To create accounts and generate keys, make sure to install [Flow CLI](../../../tools/flow-cli/install). Flow CLI provides convenient functions to simplifies interacting with the blockchain.
 </Callout>
 
 
 ### Creating an Account
 
 There is a simple Flow CLI command to run to create an account. `flow accounts create` command will create a new account and generate a key pair then add the account to your flow.json. The command will try and You can also use the [Testnet Faucet](https://testnet-faucet-v2.onflow.org/) to create and fund an account.
 
-More information about [Flow CLI](../../tools/flow-cli/accounts/create-accounts) and creating accounts. 
+More information about [Flow CLI](../../../tools/flow-cli/accounts/create-accounts) and creating accounts. 
 
 ### Creating and deploying a Project
 
-Flow CLI can be used to create a Cadence project and stay organized, [Flow CLI: Create a project](../../tools/flow-cli). This will make deployment much easiler and help with the iterative development process.
+Flow CLI can be used to create a Cadence project and stay organized, [Flow CLI: Create a project](../../../tools/flow-cli). This will make deployment much easiler and help with the iterative development process.
 
 After you have a project created and want to deploy your Cadence; contracts, transactions and scripts. 
 `flow accounts add-contract <CONTRACT_PATH> --signer <ACCOUNT_NAME> --network testnet` will deploy your contract to testnet.
-More information on how to use Flow CLI to [deploy](../../tools/flow-cli/deployment/deploy-project-contracts.md).
+More information on how to use Flow CLI to [deploy](../../../tools/flow-cli/deployment/deploy-project-contracts.md).
 
 Make sure Flow project was initialized in the previous step and the `flow.json` is present.
 
 
 ### Making Use of Core Contracts
 
-Flow Testnet comes with some useful contracts already deployed, called **core contracts.** More information and import addresses for the [core contracts](../../references/core-contracts/index.md).
+Flow Testnet comes with some useful contracts already deployed, called **core contracts.** More information and import addresses for the [core contracts](../../../references/core-contracts/index.md).
 
 Once your accounts are set up and you're ready to develop, you can look over [some code examples from the Flow Go SDK](https://github.com/onflow/flow-go-sdk/tree/master/examples).