manual set urls for external collection

collections/system_administrators/advanced/cancel_contracts.md

@@ -15,7 +15,7 @@ We present different methods to delete contracts on the TFGrid.
 
 ## Using the Dashboard
 
-To cancel contracts with the Dashboard, consult the [Contracts List](../../dashboard/deploy/your_contracts.md) documentation.
+To cancel contracts with the Dashboard, consult the [Contracts List](dashboard@@your_contracts) documentation.
 
 ## Using GraphQL and Polkadot UI
 
@@ -31,7 +31,7 @@ query MyQuery {
 
 ```
 
-replace `TWIN_ID` with your twin id. The information should be available on the [Dashboard](../../dashboard/dashboard.md).
+replace `TWIN_ID` with your twin id. The information should be available on the [Dashboard](dashboard@@dashboard).
 
 Then from [polkadot UI](https://polkadot.js.org/apps/), add the tfchain endpoint to development.
 

collections/system_administrators/advanced/grid3_stellar_tfchain_bridge.md

@@ -13,13 +13,13 @@
 
 This document will explain how you can transfer TFT from Tfchain to Stellar and back.
 
-For more information on TFT bridges, read [this documentation](../threefold_token/tft_bridges/tft_bridges.md).
+For more information on TFT bridges, read [this documentation](threefold_token@@tft_bridges).
 
 ## Prerequisites
 
-- [Stellar wallet](../threefold_token/storing_tft/storing_tft.md)
+- [Stellar wallet](threefold_token@@storing_tft)
 
-- [Account on TFChain (use TF Dashboard to create one)](../dashboard/wallet_connector.md)
+- [Account on TFChain (use TF Dashboard to create one)](dashboard@@wallet_connector)
 
 ![](./img/bridge.png)
 

collections/system_administrators/getstarted/tfgrid3_getstarted.md

@@ -4,10 +4,10 @@
 
 It's easy to get started on the TFGrid and deploy applications.
 
-- [Create a TFChain Account](../../dashboard/wallet_connector.md)
-- [Get TFT](../../threefold_token/buy_sell_tft/buy_sell_tft.md)
-- [Bridge TFT to TChain](../../threefold_token/tft_bridges/tft_bridges.md)
-- [Deploy an Application](../../dashboard/deploy/deploy.md)
+- [Create a TFChain Account](dashboard@@wallet_connector)
+- [Get TFT](threefold_token@@buy_sell_tft)
+- [Bridge TFT to TChain](threefold_token@@tft_bridges)
+- [Deploy an Application](dashboard@@deploy)
 - [SSH Remote Connection](./ssh_guide/ssh_guide.md)
   - [SSH with OpenSSH](./ssh_guide/ssh_openssh.md)
   - [SSH with PuTTY](./ssh_guide/ssh_putty.md)
@@ -16,8 +16,8 @@ It's easy to get started on the TFGrid and deploy applications.
 
 ## Grid Platforms
 
-- [TF Dashboard](../../dashboard/dashboard.md)
-- [TF Flist Hub](../../developers/flist/flist_hub/zos_hub.md)
+- [TF Dashboard](dashboard/dashboard@@)
+- [TF Flist Hub](developers@@zos_hub)
 
 ## TFGrid Services and Resources
 

collections/system_administrators/getstarted/tfgrid3_what_to_know.md

@@ -50,7 +50,7 @@ We leverage the VM primitive to allow provisioning kubernetes clusters across mu
 
 
 ## Exploring the capacity
-You can easily check using [explorer-ui](dashboard/explorer/explorer_home.md) , also to plan your deployment you can use these [example queries](dashboard/explorer/explorer_graphql_examples.md)
+You can easily check using [explorer-ui](dashboard@@explorer_home) , also to plan your deployment you can use these [example queries](dashboard@@explorer_graphql_examples)
 
 ## Getting started
 

collections/system_administrators/gpu/gpu.md

@@ -25,7 +25,7 @@ To use a GPU on the TFGrid, users need to rent a dedicated node. Once they have
 
 ## Filter and Reserve a GPU Node
 
-You can filter and reserve a GPU node using the [Dedicated Nodes section](../../dashboard/deploy/dedicated_machines.md) of the **ThreeFold Dashboard**.
+You can filter and reserve a GPU node using the [Dedicated Nodes section](dashboard@@dedicated_machines) of the **ThreeFold Dashboard**.
 
 ### Filter Nodes
 
@@ -52,7 +52,7 @@ When you have decided which node to reserve, click on **Reserve** under the colu
   
 ## Deploy a VM with GPU
 
-Now that you've reserverd a dedicated GPU node, it's time to deploy a VM to make use of the GPU! There are many ways to proceed. You can use the [Dashboard](../../dashboard/solutions/fullVm.md), [Go](../../developers/go/grid3_go_gpu.md), [Terraform](../terraform/terraform_gpu_support.md), etc.
+Now that you've reserverd a dedicated GPU node, it's time to deploy a VM to make use of the GPU! There are many ways to proceed. You can use the [Dashboard](../../dashboard/solutions/fullVm.md), [Go](developers@@grid3_go_gpu), [Terraform](../terraform/terraform_gpu_support.md), etc.
 
 For example, deploying a VM with GPU on the Dashboard is easy. Simply set the GPU option and make sure to select your dedicated node, as show here:
 ![image](./img/gpu_3.png)

collections/system_administrators/gpu/gpu_toc.md

@@ -7,13 +7,13 @@ Feel free to explore the different possibilities!
 <h2>Table of Contents</h2>
 
 - [GPU Support](./gpu.md)
-- [Node Finder and GPU](../../dashboard/deploy/node_finder.md#gpu-support)
-- [Javascript Client and GPU](../../developers/javascript/grid3_javascript_gpu_support.md)
-- [GPU and Go](../../developers/go/grid3_go_gpu.md)
-  - [GPU Support](../../developers/go/grid3_go_gpu_support.md)
-  - [Deploy a VM with GPU](../../developers/go/grid3_go_vm_with_gpu.md)
-- [TFCMD and GPU](../../developers/tfcmd/tfcmd_vm.md#deploy-a-vm-with-gpu)
+- [Node Finder and GPU](dashboard@@node_finder)
+- [Javascript Client and GPU](developers@@grid3_javascript_gpu_support)
+- [GPU and Go](developers@@grid3_go_gpu)
+  - [GPU Support](developers@@grid3_go_gpu_support)
+  - [Deploy a VM with GPU](developers@@grid3_go_vm_with_gpu)
+- [TFCMD and GPU](developers@@tfcmd_vm)
 - [Terraform and GPU](../terraform/terraform_gpu_support.md)
-- [Full VM and GPU](../../dashboard/solutions/fullVm.md)
-- [Zero-OS API and GPU](../../developers/internals/zos/manual/api.md#gpus)
-- [GPU Farming](../../farmers/3node_building/gpu_farming.md)
+- [Full VM and GPU](dashboard@@fullvm)
+- [Zero-OS API and GPU](developers@@api)
+- [GPU Farming](farmers@@gpu_farming)

collections/system_administrators/terraform/advanced/terraform_nextcloud_vpn.md

@@ -263,9 +263,9 @@ Note that, at any moment, if you want to see the information on your Terraform d
 # Nextcloud Setup
 
 * Access Nextcloud Setup
-  * Once you've deployed Nextcloud, you can access the Nextcloud Setup page by pasting on a browser the URL displayed on the line `fqdn = "..."` of the `terraform show` output. For more information on this, [read this documentation](../../../dashboard/solutions/nextcloud.md#nextcloud-setup).
+  * Once you've deployed Nextcloud, you can access the Nextcloud Setup page by pasting on a browser the URL displayed on the line `fqdn = "..."` of the `terraform show` output. For more information on this, [read this documentation](dashboard@@nextcloud).
 * Create a backup and set a daily backup and update
-  * Make sure to create a backup with `/mnt/backup` as the mount point, and set a daily update and backup for your Nextcloud VM. For more information, [read this documentation](../../../dashboard/solutions/nextcloud.md#backups-and-updates).
+  * Make sure to create a backup with `/mnt/backup` as the mount point, and set a daily update and backup for your Nextcloud VM. For more information, [read this documentation](dashboard@@nextcloud).
 
 > Note: By default, the daily Borgbackup is set at 4:00 UTC. If you change this parameter, make sure to adjust the moment the [Rsync backup](#create-a-cron-job-for-the-rsync-daily-backup) is done.
 

collections/system_administrators/terraform/resources/terraform_vm.md

@@ -163,7 +163,7 @@ It's bit long for sure but let's try to dissect it a bit
   ip_range = lookup(grid_network.net1.nodes_ip_range, 2, "")
 ```
 
-- `node = grid_scheduler.sched.nodes["node1"]` means this deployment will happen on node returned from the scheduler. Otherwise the user can specify the node as `node = 2` and in this case the choice of the node is completely up to the user at this point. They need to do the capacity planning. Check the [Node Finder](../../../dashboard/deploy/node_finder.md) to know which nodes fits your deployment criteria.
+- `node = grid_scheduler.sched.nodes["node1"]` means this deployment will happen on node returned from the scheduler. Otherwise the user can specify the node as `node = 2` and in this case the choice of the node is completely up to the user at this point. They need to do the capacity planning. Check the [Node Finder](dashboard@@node_finder) to know which nodes fits your deployment criteria.
 - `network_name` which network to deploy our project on, and here we choose the `name` of network `net1`
 - `ip_range` here we [lookup](https://www.terraform.io/docs/language/functions/lookup.html) the iprange of node `2` and initially load it with `""`
 

collections/system_administrators/terraform/terraform_basics.md

@@ -51,7 +51,7 @@ There are two options when it comes to finding a node to deploy on. You can use
 - Use the [scheduler](resources/terraform_scheduler.md)
   - Scheduler will help you find a node that matches your criteria
 - Use the Nodes Explorer
-  - You can check the [Node Finder](../../dashboard/deploy/node_finder.md) to know which nodes fits your deployment criteria.
+  - You can check the [Node Finder](dashboard@@node_finder) to know which nodes fits your deployment criteria.
   - Make sure you choose a node which has enough capacity and is available (up and running).
 
 ## Preparation
@@ -160,7 +160,7 @@ terraform destroy
 
 ## Available Flists
 
-You can consult the [list of Flists](../../developers/flist/flist.md)  to learn more about the available Flist to use with a virtual machine.
+You can consult the [list of Flists](developers@@flist)  to learn more about the available Flist to use with a virtual machine.
 
 ## Full and Micro Virtual Machines