Move documentation to separate domain

Author: voatsap

README.md

@@ -19,7 +19,7 @@
 
 Cluster.dev is an open-source tool designed to manage cloud native infrastructures with simple declarative manifests - infrastructure templates. The infrastructure templates could be based on Terraform modules, Kubernetes manifests, Shell scripts, Helm charts, Kustomize and ArgoCD/Flux applications, OPA policies etc. Cluster.dev sticks those components together so that you could deploy, test and distribute a whole set of components with pinned versions.
 
-For more information on cluster.dev and its functionality please visit [cluster.dev](https://cluster.dev/). 
+For more information on cluster.dev and its functionality please visit [cluster.dev](https://docs.cluster.dev/). 
 
 ### Principle Diagram
 

docs/aws-cloud-provider.md

@@ -12,7 +12,7 @@ Cdev uses stack templates to generate projects in a desired cloud. This section
 
 4. kubectl installed.
 
-5. [Cdev installed](https://cluster.dev/getting-started/#cdev-install).
+5. [Cdev installed](https://docs.cluster.dev/getting-started/#cdev-install).
 
 ### Authentication
 
@@ -116,11 +116,11 @@ In AWS-EKS stack template example you need to define a Route 53 hosted zone. Opt
 
 3. Edit variables in the example's files, if necessary:
 
-    * project.yaml - main project config. Sets common global variables for current project such as organization, region, state bucket name etc. See [project configuration docs](https://cluster.dev/project-configuration/#project).
+    * project.yaml - main project config. Sets common global variables for current project such as organization, region, state bucket name etc. See [project configuration docs](https://docs.cluster.dev/project-configuration/#project).
 
-    * backend.yaml - configures backend for cdev states (including Terraform states). Uses variables from project.yaml. See [backend docs](https://cluster.dev/project-configuration/#backends).
+    * backend.yaml - configures backend for cdev states (including Terraform states). Uses variables from project.yaml. See [backend docs](https://docs.cluster.dev/project-configuration/#backends).
 
-    * infra.yaml - describes stack configuration. See [stack docs](https://cluster.dev/project-configuration/#stack).
+    * infra.yaml - describes stack configuration. See [stack docs](https://docs.cluster.dev/project-configuration/#stack).
 
 4. Run `cdev plan` to build the project. In the output you will see an infrastructure that is going to be created after running `cdev apply`.
 

docs/digital-ocean-cloud-provider.md

@@ -10,7 +10,7 @@ Cdev uses stack templates to generate projects in a desired cloud. This section
 
 3. [doctl installed](https://docs.digitalocean.com/reference/doctl/how-to/install/).
 
-4. [Cdev installed](https://cluster.dev/getting-started/#cdev-install).
+4. [Cdev installed](https://docs.cluster.dev/getting-started/#cdev-install).
 
 ### Authentication
 
@@ -87,11 +87,11 @@ For details on using DO spaces bucket as a backend, see [here](https://www.digit
 
 3. Edit variables in the example's files, if necessary:
 
-    * project.yaml - main project config. Sets common global variables for current project such as organization, region, state bucket name etc. See [project configuration docs](https://cluster.dev/project-configuration/#project).
+    * project.yaml - main project config. Sets common global variables for current project such as organization, region, state bucket name etc. See [project configuration docs](https://docs.cluster.dev/project-configuration/#project).
 
-    * backend.yaml - configures backend for cdev states (including Terraform states). Uses variables from project.yaml. See [backend docs](https://cluster.dev/project-configuration/#backends).
+    * backend.yaml - configures backend for cdev states (including Terraform states). Uses variables from project.yaml. See [backend docs](https://docs.cluster.dev/project-configuration/#backends).
 
-    * infra.yaml - describes stack configuration. See [stack docs](https://cluster.dev/project-configuration/#stack).
+    * infra.yaml - describes stack configuration. See [stack docs](https://docs.cluster.dev/project-configuration/#stack).
 
 4. Run `cdev plan` to build the project. In the output you will see an infrastructure that is going to be created after running `cdev apply`.
 

docs/getting-started.md

@@ -40,5 +40,5 @@ curl -fsSL https://raw.githubusercontent.com/shalb/cluster.dev/master/scripts/ge
 
 !!! tip
 
-    We recommend installation from script as the easiest and the quickest way to have cdev installed. For other options, please see [Cdev Install Reference](https://cluster.dev/cdev-installation-reference/) section.
+    We recommend installation from script as the easiest and the quickest way to have cdev installed. For other options, please see [Cdev Install Reference](https://docs.cluster.dev/cdev-installation-reference/) section.
 

docs/project-configuration.md

@@ -74,7 +74,7 @@ variables:
 
 * `variables`: data set for a stack template rendering.
 
-*  <a name="infra_options_template">`template`</a>: it's either a path to a local directory containing the stack template's configuration files, or a remote Git repository as the stack template source. For more details on stack templates please see the [Stack Template Development](https://cluster.dev/stack-template-development/) section. A local path must begin with either `/` for absolute path, `./` or `../` for relative path. For Git source, use this format: `<GIT_URL>//<PATH_TO_TEMPLATE_DIR>?ref=<BRANCH_OR_TAG>`:
+*  <a name="infra_options_template">`template`</a>: it's either a path to a local directory containing the stack template's configuration files, or a remote Git repository as the stack template source. For more details on stack templates please see the [Stack Template Development](https://docs.cluster.dev/stack-template-development/) section. A local path must begin with either `/` for absolute path, `./` or `../` for relative path. For Git source, use this format: `<GIT_URL>//<PATH_TO_TEMPLATE_DIR>?ref=<BRANCH_OR_TAG>`:
     * `<GIT_URL>` - *required*. Standard Git repo url. See details on [official Git page](https://git-scm.com/docs/git-clone#_git_urls).
     * `<PATH_TO_TEMPLATE_DIR>` - *optional*, use it if the stack template's configuration is not in repo root.
     * `<BRANCH_OR_TAG>`- Git branch or tag.
@@ -212,4 +212,4 @@ Currently there are 3 types of stack templates available:
   * [aws-eks](https://github.com/shalb/cdev-aws-eks)
   * [do-k8s](https://github.com/shalb/cdev-do-k8s)
 
-For the detailed information on templates, please see the section [Stack Template Development](https://cluster.dev/stack-template-development/).
+For the detailed information on templates, please see the section [Stack Template Development](https://docs.cluster.dev/stack-template-development/).

mkdocs.yml

@@ -2,7 +2,7 @@ site_name: Cluster.dev
 # Page tree
 repo_name: 'shalb/cluster.dev'
 repo_url: 'https://github.com/shalb/cluster.dev'
-site_url: 'https://cluster.dev'
+site_url: 'https://docs.cluster.dev'
 
 
 nav:
@@ -17,7 +17,7 @@ nav:
     - Deploying to GCE: google-cloud-provider.md
     - Deploying to Azure: azure-cloud-provider.md
     - Cdev Install Reference: cdev-installation-reference.md
-  - Developer Mode: 
+  - Developer Mode:
     - Stack Template Development: stack-template-development.md
     - Workflow: template-development-workflow.md
   - Reference:

pkg/cmd/cdev/main.go

@@ -11,7 +11,7 @@ import (
 // rootCmd represents the base command when called without any subcommands
 var rootCmd = &cobra.Command{
 	Use:   "cdev",
-	Short: "See https://cluster.dev/ for details.",
+	Short: "See https://docs.cluster.dev/ for details.",
 }
 var ll string