diff --git a/content/cloud/advanced-features/index.md b/content/cloud/advanced-features/index.md
index 8cf560d9a0b76fa617e768c80906beaf9ce3fa3d..8cba8b07c42855d7491b9a038ff3e9beda35508b 100644
--- a/content/cloud/advanced-features/index.md
+++ b/content/cloud/advanced-features/index.md
@@ -6,7 +6,7 @@ draft: false
 
 
 The following guide will introduce you to advanced features available in MetaCentrum Cloud.
-For basic instructions on how to start a virtual machine instance, see [Quick Start](/cloud/quick-start).
+For basic instructions on how to start a virtual machine instance, see [Quick Start](/documentation/cloud/quick-start).
 
 
 ## Orchestration
@@ -27,7 +27,7 @@ Instructions for uploading custom image:
 
 1. Upload only images in RAW format (not qcow2, vmdk, etc.).
 
-2. Upload is supported only through OpenStack [CLI](/cloud/cli/) with Application Credentials.
+2. Upload is supported only through OpenStack [CLI](/documentation/cloud/cli/) with Application Credentials.
 
 3. Each image needs to contain metadata:
 ```
@@ -290,7 +290,7 @@ In both cases you will need application credentials to be able to manage your da
 
 ### Swift credentials
 
-The easiest way to generate **Swift** storage credentials is through [MetaCentrum cloud dashboard](https://dashboard.cloud.muni.cz). You can generate application credentials as described [here](/cloud/cli/#getting-credentials). You must have role **heat_stack_owner**.
+The easiest way to generate **Swift** storage credentials is through [MetaCentrum cloud dashboard](https://dashboard.cloud.muni.cz). You can generate application credentials as described [here](/documentation/cloud/cli/#getting-credentials). You must have role **heat_stack_owner**.
 
 ### S3 credentials
 
diff --git a/content/cloud/best-practices/index.md b/content/cloud/best-practices/index.md
index 25ac142141e65da8a62eadf0f9b589a91919892c..f6c647e5dc9acec75db8fb206ce6ed6bfca4cd84 100644
--- a/content/cloud/best-practices/index.md
+++ b/content/cloud/best-practices/index.md
@@ -7,12 +7,12 @@ draft: false
 Following article summarizes effective approaches how to use our cloud.
 
 ## How many public IP addresses I need?
-There are [two pools of public IPv4 addresses available](/cloud/network/#group-project).
-**Unfortunately the amount of available public IPv4 addresses is limited.** Read the details on [how to set-up your project networking](/cloud/network/).
+There are [two pools of public IPv4 addresses available](/documentation/cloud/network/#group-project).
+**Unfortunately the amount of available public IPv4 addresses is limited.** Read the details on [how to set-up your project networking](/documentation/cloud/network/).
 
 In most cases even when you build huge cloud infrastructure you should be able to access it via few (up-to two) public IP addresses.
 
-![](/cloud/best-practices/images/accessing-vms-through-jump-host-6-mod.png)
+![](/documentation/cloud/best-practices/images/accessing-vms-through-jump-host-6-mod.png)
 
 There are following project VMs in the cloud architecture:
 
@@ -105,7 +105,7 @@ There are several options how to transfer project to cloud resources:
  * automatically with `terraform`
  * indirectly in a project container (example: [releasing a project container image](https://gitlab.ics.muni.cz/cloud/cloud-estimate-pi/-/blob/de673766b832c48142c6ad1be73f5bce046b02a2/.gitlab-ci.yml#L17-80), [pulling and running a project image](https://gitlab.ics.muni.cz/cloud/cloud-estimate-pi/-/blob/de673766b832c48142c6ad1be73f5bce046b02a2/ansible/roles/cloud-project-container/tasks/deploy.yml#L16-28))
  * indirectly in OpenStack (glance) image (you need to obtain image-uploader role)
-   * OpenStack Glance images may be [public, private, community or shared](/cloud/gui/#image-visibility).
+   * OpenStack Glance images may be [public, private, community or shared](/documentation//cloud/gui/#image-visibility).
 
 ### ssh to cloud VM resources and manual update
 
diff --git a/content/cloud/cli/index.md b/content/cloud/cli/index.md
index d32a577ba244e0eaea73661ebb5310803a1873a7..7bdf5cc9c4c5bdbbef3228881578aaabda1760af 100644
--- a/content/cloud/cli/index.md
+++ b/content/cloud/cli/index.md
@@ -275,7 +275,7 @@ $ openstack floating ip delete 147.251.124.248
 
 
 ## Cloud tools
-You can inspect cloud tools [here](/cloud/tools)
+You can inspect cloud tools [here](/documentation/cloud/tools)
 
 ## Full Reference
 See [OpenStack CLI Documentation](https://docs.openstack.org/python-openstackclient/train/).
\ No newline at end of file
diff --git a/content/cloud/faq/index.md b/content/cloud/faq/index.md
index 985e8f0691a4107b2c0b2926f149057281ebe771..0a86bea8c4c3cf88b28f38e8b33491647eb0ade2 100644
--- a/content/cloud/faq/index.md
+++ b/content/cloud/faq/index.md
@@ -6,7 +6,7 @@ draft: false
 
 
 ## Where I can find how to use MetaCentrum Cloud effectively?
-Read our [cloud best-practice tips](/cloud/register).
+Read our [cloud best-practice tips](/documentation/cloud/register).
 
 ## What to expect from the cloud and cloud computing
 
@@ -23,10 +23,10 @@ The most visible [cloud computing](https://en.wikipedia.org/wiki/Cloud_computing
  * encouraged cloud project agility
 
 ## How do I register?
-Follow instructions for registering in [MetaCentrum Cloud](/cloud/register).
+Follow instructions for registering in [MetaCentrum Cloud](/documentation/cloud/register).
 
 ## How do I migrate from legacy platforms?
-Follow instructions for [migrating from CESNET-MetaCloud or OStack ICS MUNI](/cloud/migrate).
+Follow instructions for [migrating from CESNET-MetaCloud or OStack ICS MUNI](/documentation/cloud/migrate).
 
 ## Where do I report a problem?
 First, try searching the documentation for an answer to your problem. If that does not yield results, open a
@@ -40,7 +40,7 @@ Personal projects can allocate floating IPs from *public-muni-147-251-124* and *
 Group projects can currently allocate floating IPs from *public-cesnet-78-128-251* and *private-muni-10-16-116*.
 IP addresses from *public-muni-147-251-124* allocated by users to group projects are released daily, so we encourage
 using only *public-cesnet-78-128-251* and *private-muni-10-16-116* for group projects.
-Follow instructions at [changing the external network](/cloud/network) in order to change your public network.
+Follow instructions at [changing the external network](/documentation/cloud/network) in order to change your public network.
 
 ## Issues with network stability in Docker
 OpenStack instances use 1442 bytes MTU (maximum transmission unit) instead of standard 1500 bytes MTU. Instance itself is
@@ -66,7 +66,7 @@ To access internet from an instance, or access instance from the internet, you c
    2. Associate floating IP with this instance.
    3. Install [sshuttle](https://github.com/sshuttle/sshuttle) on your client.
    4. `sshuttle -r root@jump_host_fip 192.168.0.1/24`. All your traffic to internal OpenStack network *192.168.0.1/24* is now tunneled through jump host.
- * **I need to serve content (e.g. webservice) to other users** - public and private clouds provide LBaaS (Load-Balancer-as-a-Service) service, which proxies users traffic to instances. MetaCentrum Cloud provides this service in experimental mode - [documentation](/cloud/gui#lbaas)
+ * **I need to serve content (e.g. webservice) to other users** - public and private clouds provide LBaaS (Load-Balancer-as-a-Service) service, which proxies users traffic to instances. MetaCentrum Cloud provides this service in experimental mode - [documentation](/documentation/cloud/gui#lbaas)
 
 In case, that these options are not suitable for you usecase, you can still request multiple floating IPs.
 
diff --git a/content/cloud/network/index.md b/content/cloud/network/index.md
index bf7437c8347050c8fc289345ba8e853816ef13b3..d33641846dfc81a5e87631626ad6fbd94f76bdf9 100644
--- a/content/cloud/network/index.md
+++ b/content/cloud/network/index.md
@@ -15,8 +15,8 @@ For the networking in Cloud2 metacentrum we need to distinguish following scenar
 **WARNING:**
      Please read the following rules:
 
-   1. If you are using a [PERSONAL](/cloud/register/#personal-project)  project you have to use the `78-128-250-pers-proj-net` network to make your instance accesible from external network (e.g. Internet). Use `public-cesnet-78-128-250-PERSONAL` for FIP allocation, FIPs from this pool will be periodically released.
-   2. If you are using a [GROUP](/cloud/register/#group-project)  project you may choose from the `public-cesnet-78-128-251-GROUP`, `public-muni-147-251-124-GROUP` or any other [GROUP](/cloud/register/#group-project)  network for FIP allocation to make your instance accesible from external network (e.g. Internet).
+   1. If you are using a [PERSONAL](cloud/register/#personal-project)  project you have to use the `78-128-250-pers-proj-net` network to make your instance accesible from external network (e.g. Internet). Use `public-cesnet-78-128-250-PERSONAL` for FIP allocation, FIPs from this pool will be periodically released.
+   2. If you are using a [GROUP](cloud/register/#group-project)  project you may choose from the `public-cesnet-78-128-251-GROUP`, `public-muni-147-251-124-GROUP` or any other [GROUP](cloud/register/#group-project)  network for FIP allocation to make your instance accesible from external network (e.g. Internet).
    3. Violation of the network usage may lead into resource removal and reducing of the quotas assigned.
 {{< /hint >}}
 
@@ -35,7 +35,7 @@ In group project situation is rather different. You cannot use the same approach
 **NOTICE**
 
 If you use MUNI account, you can use private-muni-10-16-116 and log into the network via MUNI VPN or you can set up Proxy networking, which is described
-[here](/cloud/network/#proxy-networking)
+[here](cloud/network/#proxy-networking)
 {{< /hint  >}}
 
 #### Virtual Networks
@@ -68,17 +68,17 @@ Inside the interactive dialog:
 {{< hint danger >}}
 **NOTICE**
 
-If you want to use CLI to create network, please go [here](/cloud/cli/#create-network)
+If you want to use CLI to create network, please go [here](cloud/cli/#create-network)
 {{< /hint >}}
 
 
 #### Proxy networking
 In your OpenStack instances you can you private or public networks. If you use private network and you need to access to the internet for updates etc.,
-you can visit following [link](/cloud/faq/#issues-with-proxy-in-private-networks), where it is explained, how to set up Proxy connection.
+you can visit following [link](cloud/faq/#issues-with-proxy-in-private-networks), where it is explained, how to set up Proxy connection.
 
 
 #### Setup Router gateway (Required for Group projects)
-Completing [Create Virtual Machine Instance](/cloud/quick-start/#create-virtual-machine-instance) created instance connected
+Completing [Create Virtual Machine Instance](cloud/quick-start/#create-virtual-machine-instance) created instance connected
 to software defined network represented by internal network, subnet and router. Router has by default gateway address
 from External Network chosen by cloud administrators. You can change it to any External Network with [GROUP](/cloud/register/#group-project) suffix, that
 is visible to you (e.g. **public-muni-147-251-124-GROUP** or **public-cesnet-78-128-251-GROUP**). Usage of External Networks
@@ -90,7 +90,7 @@ For changing gateway IP address follow these steps:
 If router exists with another settings, then use button Clear Gateway, confirm Clear Gateway.
 If router isn't set then use button Create router and choose network.
 
-2. From list of External Network choose **public-cesnet-78-128-251-GROUP**, **public-muni-147-251-124-GROUP** or any other [GROUP](/cloud/register/#group-project)  network you see.
+2. From list of External Network choose **public-cesnet-78-128-251-GROUP**, **public-muni-147-251-124-GROUP** or any other [GROUP](cloud/register/#group-project)  network you see.
 
  ![](images/network_routers-group.png)
 
@@ -114,7 +114,7 @@ Now you need to attach your internal network to the router.
 {{< hint info >}}
 **NOTICE**
 
-If you want to use CLI to manage routers, please go [here](/cloud/cli/#router-management)
+If you want to use CLI to manage routers, please go [here](cloud/cli/#router-management)
 {{< /hint >}}
 
 
@@ -131,7 +131,7 @@ Routers can also be used to route traffic between internal networks. This is an
 {{< hint danger >}}
 **WARNING**
 
-There is a limited number of Floating IP adresses. So please before you ask for more Floating IP address, visit and read [FAQ](/cloud/faq/#how-many-floating-ips-does-my-group-project-need)
+There is a limited number of Floating IP adresses. So please before you ask for more Floating IP address, visit and read [FAQ](cloud/faq/#how-many-floating-ips-does-my-group-project-need)
 {{< /hint  >}}
 
 
@@ -172,7 +172,7 @@ and the IP in question will remain allocated to you and consume your Floating IP
 {{< hint info >}}
 **NOTICE**
 
-If you want to use CLI to manage FIP, please go [here](/cloud/cli/#floating-ip-address-management).
+If you want to use CLI to manage FIP, please go [here](cloud/cli/#floating-ip-address-management).
 {{< /hint >}}
 
 
diff --git a/content/cloud/news/index.md b/content/cloud/news/index.md
index 78911e59e24d2080fc7bffd19e8e2b25e3176ec2..fd1323b1279e6543118d81a74cc2cabaad5d6ed3 100644
--- a/content/cloud/news/index.md
+++ b/content/cloud/news/index.md
@@ -22,7 +22,7 @@ draft: false
 * hpc.ics-gladosag-full
 * csirtmu.tiny1x2
 
-None of the parameters were decreased but increased. Updated parameters were Net througput, IOPS and Disk througput. Existing instances will have the previous parameters so if you want to get new parameters, **make a data backup** and rebuild your instance  You can check list of flavors [here](/cloud/flavors).
+None of the parameters were decreased but increased. Updated parameters were Net througput, IOPS and Disk througput. Existing instances will have the previous parameters so if you want to get new parameters, **make a data backup** and rebuild your instance  You can check list of flavors [here](/documentation/cloud/flavors).
 
 **2021-04-13** OpenStack image `centos-8-1-1911-x86_64_gpu` deprecation in favor of `centos-8-x86_64_gpu`. Deprecated image will be still available for existing VM instances, but will be moved from public to community images in about 2 months.
 
diff --git a/content/cloud/putty/index.md b/content/cloud/putty/index.md
index 77123a1e262f165b79dbcf2b980277c5ccc18df7..ebfe342770fb6e5d71368689d69c2f2e0ef64a95 100644
--- a/content/cloud/putty/index.md
+++ b/content/cloud/putty/index.md
@@ -15,7 +15,7 @@ We recommend to download [Windows Installer](https://www.chiark.greenend.org.uk/
 
 ## PuTTY - Connect to the Instance
 
-* Run PuTTY and enter Host name in format "login@Floating IP address" where [login](/cloud/quick-start#create-virtual-machine-instance) is for example debian for Debian OS and Floating IP is [IP address](/cloud/quick-start/#associate-floating-ip) to access instance from internet.
+* Run PuTTY and enter Host name in format "login@Floating IP address" where [login](/documentation/cloud/quick-start#create-virtual-machine-instance) is for example debian for Debian OS and Floating IP is [IP address](/cloud/quick-start/#associate-floating-ip) to access instance from internet.
 * In Category -> Connection -> SSH -> Auth:
   *  Select **Attempt authentication using Pageant**
   *  Select **Allow agent forwarding**
diff --git a/content/cloud/quick-start/index.md b/content/cloud/quick-start/index.md
index 77a1423d77fbdbad8c19ae3ea1c393e2f01e958f..0bce9f48f410e6f08a2d941a8867100a6668e2cc 100644
--- a/content/cloud/quick-start/index.md
+++ b/content/cloud/quick-start/index.md
@@ -147,7 +147,7 @@ For details, refer to [the official documentation](https://docs.openstack.org/ho
 
       * For personal project select personal-project-network-subnet from network 78-128-250-pers-proj-net
         ![](images/instance_launch_network-user.png)
-      * For group project select group-project-network-subnet from network group-project-network (check if [Router gateway](/network#associate-floating-ip") is set)
+      * For group project select group-project-network-subnet from network group-project-network (check if [Router gateway](/documentation//network#associate-floating-ip") is set)
         ![](images/instance_launch_network-group.png)
 6. Key pair
       * **If public key was imported already**, add existing key to the instance and continue using button **Next**
@@ -158,24 +158,24 @@ For details, refer to [the official documentation](https://docs.openstack.org/ho
         * Use button **Create Key Pair**
         * Continue steps in section [Create Key Pair](#create-key-pair) -> Create Key Pair
         * Add key and continue using button **Next**
-    ![Select Key pair](/cloud/quick-start/images/instance_launch_key_pair.png)
+    ![Select Key pair](cloud/quick-start/images/instance_launch_key_pair.png)
 
 7. __(optional)__ On the Configuration tab, you can use `user_data` to customize your instance at boot.
-    ![](/cloud/quick-start/images/instance_launch_configuration.png)
+    ![](/documentation/cloud/quick-start/images/instance_launch_configuration.png)
    See [cloud-init](https://cloud-init.io/) for details.
 
 8. Use button Launch Instance to initialize new instance
 
-9. Wait until instance initialization finishes and [Associate Floating IP](/cloud/network/#associate-floating-ip). For group project always select the same network as used in [Router gateway](/network/#setup-router-gateway-required-for-group-projects)
+9. Wait until instance initialization finishes and [Associate Floating IP](/documentation/cloud/network/#associate-floating-ip). For group project always select the same network as used in [Router gateway](cloud/network/#setup-router-gateway-required-for-group-projects)
     ![](images/instance_associate_ip.png)
 
 10. Login using your SSH key as selected in Key pair above
-Connect to the instance using **ssh image login**, [id_rsa key registered in Openstack](#create-key-pair) and [Floating IP](/network/#associate-floating-ip).
+Connect to the instance using **ssh image login**, [id_rsa key registered in Openstack](#create-key-pair) and [Floating IP](/documentation/network/#associate-floating-ip).
 
 
 {{< hint info >}}
 **NOTICE**
-On Linux and Mac you can use already present SSH client. On Windows there are other possibilities how to connect via SSH. One of the most common is [PuTTy](https://en.wikipedia.org/wiki/PuTTY) SSH client. How to configure and use PuTTy you can visit our tutorial [here](/cloud/putty/#putty).
+On Linux and Mac you can use already present SSH client. On Windows there are other possibilities how to connect via SSH. One of the most common is [PuTTy](https://en.wikipedia.org/wiki/PuTTY) SSH client. How to configure and use PuTTy you can visit our tutorial [here](/documentation/cloud/putty/#putty).
 {{</hint>}}
 
 
@@ -216,8 +216,8 @@ For details, refer to [the official documentation](https://docs.openstack.org/ho
 
 {{< hint danger >}}
 **WARNING**
-If you have [GROUP](/cloud/register/#group-project) project, you need to configure
-Router gateway for your network. [Here](/cloud/network/#setup-router-gateway-required-for-group-projects) you can find the manual.
+If you have [GROUP](/documentation/cloud/register/#group-project) project, you need to configure
+Router gateway for your network. [Here](cloud/network/#setup-router-gateway-required-for-group-projects) you can find the manual.
 {{</hint>}}
 
 
@@ -227,7 +227,7 @@ Router gateway for your network. [Here](/cloud/network/#setup-router-gateway-req
 {{< hint danger >}}
 **WARNING**
 To make an instance accessible from external networks (e.g., The Internet), a so-called Floating IP Address has to be
-associated with it. [Here](/cloud/network/#associate-floating-ip) you can find the manual.
+associated with it. [Here](/documentation/cloud/network/#associate-floating-ip) you can find the manual.
 {{</hint>}}
 
 ## Create Volume
diff --git a/content/cloud/register/index.md b/content/cloud/register/index.md
index ff9dfd2f74c335809925c00b818e9e83b84fbf53..70dfa83a91e158a34f14414e2d51417571c35ccd 100644
--- a/content/cloud/register/index.md
+++ b/content/cloud/register/index.md
@@ -64,7 +64,7 @@ request a group project from User Support and provide the following basic inform
 * __name of the project__,
 * __purpose of the project__,
 * __contact information__,
-* __amount and type of requested resources__ _[(please read first)](/cloud/faq/#how-many-floating-ips-does-my-group-project-need)_,
+* __amount and type of requested resources__ _[(please read first)](/documentation/cloud/faq/#how-many-floating-ips-does-my-group-project-need)_,
 * __impact would the service have on unavailability for 1h, 1d, 1w__,
 * __estimated length of the project__,
 * __access control information__ _[(info)](#get-access-control-information)_.
diff --git a/content/cloud/tools/index.md b/content/cloud/tools/index.md
index 2cfe2e41ed82c154850baeeef3345ff719c2f9ea..2eb35d074ffe38bb1fbb18a1ffc0b165fb05c6f9 100644
--- a/content/cloud/tools/index.md
+++ b/content/cloud/tools/index.md
@@ -4,4 +4,4 @@ date: 2021-05-18T11:22:35+02:00
 draft: false
 ---
 
-On this address [https://gitlab.ics.muni.cz/cloud/cloud-tools](https://gitlab.ics.muni.cz/cloud/cloud-tools) you can find a docker container with all modules required for cloud management, if you are interested in managing your cloud platform via CLI. If so, you can check our guide how to use CLI cloud interface [here](/cloud/cli/).
\ No newline at end of file
+On this address [https://gitlab.ics.muni.cz/cloud/cloud-tools](https://gitlab.ics.muni.cz/cloud/cloud-tools) you can find a docker container with all modules required for cloud management, if you are interested in managing your cloud platform via CLI. If so, you can check our guide how to use CLI cloud interface [here](/documentation/cloud/cli/).
\ No newline at end of file