+
+ If your page matches, then it means that the container is able to communicate with the AWS MemoryDB database.
+
+ You can play around with the application's features:
+
+ - Add a todo item
+ - Mark a todo item as complete
+ - Delete a todo item
+
+## Cleanup
+
+{{% alert title="Delete environment" color="warning" %}}
+If you're done with testing, you can use the rad CLI to [delete an environment]({{< ref rad_env_delete.md >}}) to delete all Radius resources running on the EKS Cluster.
+{{% /alert %}}
+
+{{% alert title="Cleanup AWS Resources" color="warning" %}}
+AWS resources are not deleted when deleting a Radius environment, so to prevent additional charges, make sure to delete all resources created in this quickstart. This includes the SubnetGroup and MemoryDB created in Step 3. You can delete these resources in the AWS Console or via the AWS CLI.
+{{% /alert %}}
diff --git a/docs/content/getting-started/quickstarts/quickstart-aws/snippets/app-existing.bicep b/docs/content/getting-started/quickstarts/quickstart-aws/snippets/app-existing.bicep
new file mode 100644
index 000000000..5537a4126
--- /dev/null
+++ b/docs/content/getting-started/quickstarts/quickstart-aws/snippets/app-existing.bicep
@@ -0,0 +1,43 @@
+import radius as radius
+
+param environment string
+
+resource app 'Applications.Core/applications@2022-03-15-privatepreview' = {
+ name: 'webapp'
+ properties: {
+ environment: environment
+ }
+}
+
+resource frontend 'Applications.Core/containers@2022-03-15-privatepreview' = {
+ name: 'frontend'
+ properties: {
+ application: app.id
+ container: {
+ image: 'radius.azurecr.io/tutorial/webapp:edge'
+ }
+ connections: {
+ redis: {
+ source: db.id
+ }
+ }
+ }
+}
+
+resource db 'Applications.Link/redisCaches@2022-03-15-privatepreview' = {
+ name: 'db'
+ properties: {
+ environment: environment
+ resourceProvisioning: 'manual'
+ host: memoryDB.outputs.memoryDBHost
+ port: memoryDB.outputs.memoryDBPort
+ secrets: {
+ connectionString: memoryDB.outputs.memoryDBConnectionString
+ }
+ }
+}
+
+module memoryDB 'aws-memorydb-existing.bicep' = {
+ name: 'memorydb-module'
+}
+
diff --git a/docs/content/getting-started/quickstarts/quickstart-aws/snippets/app.bicep b/docs/content/getting-started/quickstarts/quickstart-aws/snippets/app.bicep
new file mode 100644
index 000000000..7adb44015
--- /dev/null
+++ b/docs/content/getting-started/quickstarts/quickstart-aws/snippets/app.bicep
@@ -0,0 +1,48 @@
+import radius as radius
+
+param eksClusterName string
+
+param environment string
+resource app 'Applications.Core/applications@2022-03-15-privatepreview' = {
+ name: 'webapp'
+ properties: {
+ environment: environment
+ }
+}
+
+resource frontend 'Applications.Core/containers@2022-03-15-privatepreview' = {
+ name: 'frontend'
+ properties: {
+ application: app.id
+ container: {
+ image: 'radius.azurecr.io/tutorial/webapp:edge'
+ }
+ connections: {
+ redis: {
+ source: db.id
+ }
+ }
+ }
+}
+
+// Radius Redis cache link resource that enables connection to the underlying MmeoryDB cluster with outputs from the Bicep module below
+resource db 'Applications.Link/redisCaches@2022-03-15-privatepreview' = {
+ name: 'db'
+ properties: {
+ environment: environment
+ resourceProvisioning: 'manual'
+ host: memoryDB.outputs.memoryDBHost
+ port: memoryDB.outputs.memoryDBPort
+ secrets: {
+ connectionString: memoryDB.outputs.memoryDBConnectionString
+ }
+ }
+}
+
+// Invoke the memoryDB provisioning using Bicep module and pass in the name of the EKS cluster.
+module memoryDB 'aws-memorydb.bicep' = {
+ name: 'memorydb-module'
+ params: {
+ eksClusterName: eksClusterName
+ }
+}
diff --git a/docs/content/getting-started/quickstarts/quickstart-aws/snippets/aws-memorydb-existing.bicep b/docs/content/getting-started/quickstarts/quickstart-aws/snippets/aws-memorydb-existing.bicep
new file mode 100644
index 000000000..ca5b9cb29
--- /dev/null
+++ b/docs/content/getting-started/quickstarts/quickstart-aws/snippets/aws-memorydb-existing.bicep
@@ -0,0 +1,13 @@
+import aws as aws
+
+param memoryDBClusterName string = 'demo-memorydb-cluster'
+resource memoryDBCluster 'AWS.MemoryDB/Cluster@default' existing = {
+ alias: memoryDBClusterName
+ properties: {
+ ClusterName: memoryDBClusterName
+ }
+}
+
+output memoryDBConnectionString string = 'rediss://${memoryDBCluster.properties.ClusterEndpoint.Address}:${memoryDBCluster.properties.ClusterEndpoint.Port}'
+output memoryDBHost string = memoryDBCluster.properties.ClusterEndpoint.Address
+output memoryDBPort int = memoryDBCluster.properties.ClusterEndpoint.Port
diff --git a/docs/content/getting-started/quickstarts/quickstart-aws/snippets/aws-memorydb.bicep b/docs/content/getting-started/quickstarts/quickstart-aws/snippets/aws-memorydb.bicep
new file mode 100644
index 000000000..a6572f160
--- /dev/null
+++ b/docs/content/getting-started/quickstarts/quickstart-aws/snippets/aws-memorydb.bicep
@@ -0,0 +1,45 @@
+import aws as aws
+
+@description('Name of the EKS cluster used for app deployment')
+param eksClusterName string
+
+// Reference the existing EKS cluster using the 'existing' keyword to provision the MemoryDB cluster in the same VPC and subnet as the EKS cluster
+resource eksCluster 'AWS.EKS/Cluster@default' existing = {
+ alias: eksClusterName
+ properties: {
+ Name: eksClusterName
+ }
+}
+
+@description('Name of the subnet group for the MemoryDB cluster')
+param subnetGroupName string = 'demo-memorydb-subnet-group'
+
+// Create a subnetgroup with the VPC and subnet IDs from the EKS cluster.
+resource subnetGroup 'AWS.MemoryDB/SubnetGroup@default' = {
+ alias:subnetGroupName
+ properties: {
+ SubnetGroupName: subnetGroupName
+ SubnetIds: eksCluster.properties.ResourcesVpcConfig.SubnetIds
+ }
+}
+
+@description('Name of the MemoryDb cluster')
+param memoryDBClusterName string = 'demo-memorydb-cluster'
+
+// Create a MemoryDB clsuster with subnetgroupName that was created before and the EKS cluster security group ID to enable the cluster connect to MemoryDB .
+resource memoryDBCluster 'AWS.MemoryDB/Cluster@default' = {
+ alias: memoryDBClusterName
+ properties: {
+ ClusterName: memoryDBClusterName
+ NodeType: 'db.t4g.small'
+ ACLName: 'open-access'
+ SecurityGroupIds: [eksCluster.properties.ClusterSecurityGroupId]
+ SubnetGroupName: subnetGroup.name
+ NumReplicasPerShard: 0
+ }
+}
+
+// Use the output keyword to expose values to the parent module. This allows you to use the module in a nested fashion.
+output memoryDBConnectionString string = 'rediss://${memoryDBCluster.properties.ClusterEndpoint.Address}:${memoryDBCluster.properties.ClusterEndpoint.Port}'
+output memoryDBHost string = memoryDBCluster.properties.ClusterEndpoint.Address
+output memoryDBPort int = memoryDBCluster.properties.ClusterEndpoint.Port
diff --git a/docs/content/getting-started/quickstarts/quickstart-aws/todoapp-withdb.png b/docs/content/getting-started/quickstarts/quickstart-aws/todoapp-withdb.png
new file mode 100644
index 000000000..9939ae4ae
Binary files /dev/null and b/docs/content/getting-started/quickstarts/quickstart-aws/todoapp-withdb.png differ
diff --git a/docs/content/getting-started/quickstarts/quickstart-container-wi/index.md b/docs/content/getting-started/quickstarts/quickstart-container-wi/index.md
index eefd53eb1..4098613e2 100644
--- a/docs/content/getting-started/quickstarts/quickstart-container-wi/index.md
+++ b/docs/content/getting-started/quickstarts/quickstart-container-wi/index.md
@@ -33,7 +33,7 @@ rad init
## Step 2: Define a Radius environment
-Create a file named `app.bicep` and define a Radius environment with [identity property]({{< ref "operations/environments" >}}) set. This configures your environment to use your Azure AD workload identity installation with your cluster's OIDC endpoint:
+Create a file named `app.bicep` and define a Radius environment with [identity property]({{< ref "operations/environments/overview" >}}) set. This configures your environment to use your Azure AD workload identity installation with your cluster's OIDC endpoint:
{{< rad file="snippets/container-wi.bicep" embed=true marker="//ENVIRONMENT">}}
diff --git a/docs/content/getting-started/quickstarts/quickstart-environment-variables/index.md b/docs/content/getting-started/quickstarts/quickstart-environment-variables/index.md
index ebeba1094..e1c19b3bc 100644
--- a/docs/content/getting-started/quickstarts/quickstart-environment-variables/index.md
+++ b/docs/content/getting-started/quickstarts/quickstart-environment-variables/index.md
@@ -17,7 +17,7 @@ This quickstart will teach you:
## Prerequisites
- [Radius CLI]({{< ref "getting-started" >}})
-- [Radius environment]({{< ref "operations/environments" >}})
+- [Radius environment]({{< ref "operations/environments/overview" >}})
## Step 1: Model an app and container
diff --git a/docs/content/getting-started/quickstarts/quickstart-volumes/index.md b/docs/content/getting-started/quickstarts/quickstart-volumes/index.md
index 265a5700f..d442808f5 100644
--- a/docs/content/getting-started/quickstarts/quickstart-volumes/index.md
+++ b/docs/content/getting-started/quickstarts/quickstart-volumes/index.md
@@ -16,7 +16,7 @@ This quickstart will provide an overview of how to:
## Prerequisites
- [rad CLI]({{< ref getting-started >}})
-- [Radius environment]({{< ref "operations/environments" >}})
+- [Radius environment]({{< ref "operations/environments/overview" >}})
## Step 1: Define an app and a container
diff --git a/docs/content/getting-started/supported-languages/_index.md b/docs/content/getting-started/supported-languages/_index.md
index 1ac7a041d..3dfac0fc6 100644
--- a/docs/content/getting-started/supported-languages/_index.md
+++ b/docs/content/getting-started/supported-languages/_index.md
@@ -7,11 +7,3 @@ weight: 900
categories: "How-To"
tags: ["infrastructure-as-code"]
---
-
-Radius supports a variety of infrastructure-as-code (IaC) languages.
-
-{{% alert title="Other languages" color="info" %}}
-Currently, Radius supports Bicep. Terraform support is underway as our next priority IaC language.
-{{% /alert %}}
-
-## Languages
diff --git a/docs/content/operations/custom-recipes/_index.md b/docs/content/operations/custom-recipes/index.md
similarity index 100%
rename from docs/content/operations/custom-recipes/_index.md
rename to docs/content/operations/custom-recipes/index.md
diff --git a/docs/content/operations/environments/_index.md b/docs/content/operations/environments/_index.md
index c484ecea5..28681e981 100644
--- a/docs/content/operations/environments/_index.md
+++ b/docs/content/operations/environments/_index.md
@@ -4,152 +4,6 @@ title: "Radius environments"
linkTitle: "Environments"
description: "Learn about Radius environments and how to interact with them"
weight: 200
-categories: "How-To"
tags: ["environments"]
---
-Radius environments are prepared "landing zones" for Radius applications. Applications deployed to an environment will inherit the container runtime, configuration, and other settings from the environment. Stay tuned for additional environment capabilities coming soon.
-
-## Configuration
-
-The following configuration options are available for environments:
-
-### Container runtime
-
-Radius environments can be configured with a container runtime, where Radius [containers]({{< ref container >}}) will be run, along with [gateways and routes]({{< ref networking >}}).
-
-A Kubernetes namespace is specified on the environment to tell Radius where to render application resources at deploy time.
-
-
-
-### Cloud Provider
-
-You can optionally configure cloud providers allow you to deploy and connect to cloud resources across various cloud platforms. For example, you can use the Radius Azure provider to run your application's services in your Kubernetes cluster, while deploying Azure resources to a specified Azure subscription and resource group. More information on setting up a cloud provider can be found in the [providers]({{< ref providers >}}) section.
-
-#### Supported cloud providers
-
-| Provider | Description |
-|----------|-------------|
-| [Microsoft Azure]({{< ref "providers#azure-provider" >}}) | Deploy and connect to Azure resources |
-| [Amazon Web Services]({{< ref "providers#aws-provider" >}}) | Deploy and connect to AWS resources |
-
-### External identity provider
-
-You can optionally specify an external identity provider for your environment. This allows you to add to a Radius container an external identity such as an Azure user-assigned managed identity, and then specify role-based access control (RBAC) policies for that identity on Azure resources.
-
-Supported identity providers:
-
-- [Azure AD workload identity](https://azure.github.io/azure-workload-identity/docs/introduction.html)
-
-Visit the Azure direct connection quickstart for more information. (coming soon)
-
-## CLI commands
-
-The following commands let you interact with Radius environments:
-
-{{< tabs init list show delete switch >}}
-
-{{% codetab %}}
-`rad init` initializes a new Kubernetes environment:
-
-```bash
-rad init
-```
-{{% /codetab %}}
-
-{{% codetab %}}
-[rad env list]({{< ref rad_env_list >}}) lists all of the environments in your [workspace]({{< ref workspaces >}}):
-
-```bash
-rad env list
-```
-{{% /codetab %}}
-
-{{% codetab %}}
-[rad env show]({{< ref rad_env_show >}}) prints information on the default or specified environment:
-
-```bash
-rad env show
-```
-{{% /codetab %}}
-
-{{% codetab %}}
-[rad env delete]({{< ref rad_env_delete >}}) deletes the specified environment:
-
-```bash
-rad env delete -e myenv
-```
-{{% /codetab %}}
-
-{{% codetab %}}
-[rad env switch]({{< ref rad_env_switch >}}) switches the default environment:
-
-```bash
-rad env switch -e myenv
-```
-{{% /codetab %}}
-
-{{< /tabs >}}
-
-## Schema
-
-Visit the [environment schema page]({{< ref environment-schema >}}) to learn more about environment properties and values.
-
-{{< button page="environment-schema" text="Schema" >}}
-
-## Example
-
-The following example shows an environment configured with Kubernetes as the target runtime. The `default` namespace designates where to render application resources.
-
-{{< rad file="snippets/environment.bicep" embed=true marker="//ENV" >}}
-
-## How-to: Initialize a new environment
-
-1. Begin by deploying a compatible [Kubernetes cluster]({{< ref "/operations/platforms/kubernetes" >}})
-
- *Visit the [Kubernetes platform docs]({{< ref "/operations/platforms/kubernetes" >}}) for a list of supported clusters and specific cluster requirements.*
-
-1. Ensure your target kubectl context is set as the default:
- ```bash
- kubectl config current-context
- ```
-1. Initialize a new environment with `rad init` command:
- ```bash
- rad init
- ```
-1. Follow the prompts, specifying:
- - **Namespace** - The Kubernetes namespace where your application containers and networking resources will be deployed (different than the Radius control-plane namespace, `radius-system`)
- - **Azure provider** (optional) - Allows you to [deploy and manage Azure resources]({{< ref "providers#azure-provider" >}})
- - **AWS provider** (optional) - Allows you to [deploy and manage AWS resources]({{< ref "providers#aws-provider" >}})
- - **Environment name** - The name of the environment to create
-1. Let the rad CLI run the following tasks:
- 1. **Install Radius** - Radius installs the [control plane services]({{< ref architecture-concept >}}) in the `radius-system` namespace
- 2. **Create the environment** - An environment resource is created in the Radius control plane. It maps to a Kubernetes namespace.
- 3. **Add the Azure Cloud Provider** - The Azure cloud provider configuration is saved in the Radius control plane
- 4. **Add the AWS Cloud Provider** - The AWS cloud provider configuration is saved in the Radius control plane
- 5. **Create a workspace** - [Workspaces]({{< ref workspaces >}}) are local pointers to a cluster running Radius, and an environment. Workspaces are saved to the Radius config file (`~/.rad/config.yaml` on Linux and macOS, `%USERPROFILE%\.rad\config.yaml` on Windows)
-2. Verify the initialization by running:
- ```bash
- kubectl get deployments -n radius-system
- ```
-
- You should see:
-
- ```
- NAME READY UP-TO-DATE AVAILABLE AGE
- ucp 1/1 1 1 53s
- appcore-rp 1/1 1 1 53s
- bicep-de 1/1 1 1 53s
- contour-contour 1/1 1 1 46s
- dapr-dashboard 1/1 1 1 35s
- dapr-sidecar-injector 1/1 1 1 35s
- dapr-sentry 1/1 1 1 35s
- dapr-operator 1/1 1 1 35s
- ```
-
- You can also use [`rad env list`]({{< ref rad_env_list.md >}}) to see if the created environment gets listed:
-
- ```bash
- rad env list
- ```
-
diff --git a/docs/content/operations/environments/environments.png b/docs/content/operations/environments/overview/environments.png
similarity index 100%
rename from docs/content/operations/environments/environments.png
rename to docs/content/operations/environments/overview/environments.png
diff --git a/docs/content/operations/environments/overview/index.md b/docs/content/operations/environments/overview/index.md
new file mode 100644
index 000000000..b488a477b
--- /dev/null
+++ b/docs/content/operations/environments/overview/index.md
@@ -0,0 +1,155 @@
+---
+type: docs
+title: "Overview: Radius environments"
+linkTitle: "Overview"
+description: "Learn about Radius environments and how to interact with them"
+weight: 100
+categories: "Overview"
+tags: ["environments"]
+---
+
+Radius environments are prepared "landing zones" for Radius applications. Applications deployed to an environment will inherit the container runtime, configuration, and other settings from the environment. Stay tuned for additional environment capabilities coming soon.
+
+## Configuration
+
+The following configuration options are available for environments:
+
+### Container runtime
+
+Radius environments can be configured with a container runtime, where Radius [containers]({{< ref container >}}) will be run, along with [gateways and routes]({{< ref networking >}}).
+
+A Kubernetes namespace is specified on the environment to tell Radius where to render application resources at deploy time.
+
+
+
+### Cloud Provider
+
+You can optionally configure cloud providers allow you to deploy and connect to cloud resources across various cloud platforms. For example, you can use the Radius Azure provider to run your application's services in your Kubernetes cluster, while deploying Azure resources to a specified Azure subscription and resource group. More information on setting up a cloud provider can be found in the [providers]({{< ref providers >}}) section.
+
+#### Supported cloud providers
+
+| Provider | Description |
+|----------|-------------|
+| [Microsoft Azure]({{< ref "providers#azure-provider" >}}) | Deploy and connect to Azure resources |
+| [Amazon Web Services]({{< ref "providers#aws-provider" >}}) | Deploy and connect to AWS resources |
+
+### External identity provider
+
+You can optionally specify an external identity provider for your environment. This allows you to add to a Radius container an external identity such as an Azure user-assigned managed identity, and then specify role-based access control (RBAC) policies for that identity on Azure resources.
+
+Supported identity providers:
+
+- [Azure AD workload identity](https://azure.github.io/azure-workload-identity/docs/introduction.html)
+
+Visit the Azure direct connection quickstart for more information. (coming soon)
+
+## CLI commands
+
+The following commands let you interact with Radius environments:
+
+{{< tabs init list show delete switch >}}
+
+{{% codetab %}}
+`rad init` initializes a new Kubernetes environment:
+
+```bash
+rad init
+```
+{{% /codetab %}}
+
+{{% codetab %}}
+[rad env list]({{< ref rad_env_list >}}) lists all of the environments in your [workspace]({{< ref workspaces >}}):
+
+```bash
+rad env list
+```
+{{% /codetab %}}
+
+{{% codetab %}}
+[rad env show]({{< ref rad_env_show >}}) prints information on the default or specified environment:
+
+```bash
+rad env show
+```
+{{% /codetab %}}
+
+{{% codetab %}}
+[rad env delete]({{< ref rad_env_delete >}}) deletes the specified environment:
+
+```bash
+rad env delete -e myenv
+```
+{{% /codetab %}}
+
+{{% codetab %}}
+[rad env switch]({{< ref rad_env_switch >}}) switches the default environment:
+
+```bash
+rad env switch -e myenv
+```
+{{% /codetab %}}
+
+{{< /tabs >}}
+
+## Schema
+
+Visit the [environment schema page]({{< ref environment-schema >}}) to learn more about environment properties and values.
+
+{{< button page="environment-schema" text="Schema" >}}
+
+## Example
+
+The following example shows an environment configured with Kubernetes as the target runtime. The `default` namespace designates where to render application resources.
+
+{{< rad file="snippets/environment.bicep" embed=true marker="//ENV" >}}
+
+## How-to: Initialize a new environment
+
+1. Begin by deploying a compatible [Kubernetes cluster]({{< ref "/operations/platforms/kubernetes" >}})
+
+ *Visit the [Kubernetes platform docs]({{< ref "/operations/platforms/kubernetes" >}}) for a list of supported clusters and specific cluster requirements.*
+
+1. Ensure your target kubectl context is set as the default:
+ ```bash
+ kubectl config current-context
+ ```
+1. Initialize a new environment with `rad init` command:
+ ```bash
+ rad init
+ ```
+1. Follow the prompts, specifying:
+ - **Namespace** - The Kubernetes namespace where your application containers and networking resources will be deployed (different than the Radius control-plane namespace, `radius-system`)
+ - **Azure provider** (optional) - Allows you to [deploy and manage Azure resources]({{< ref "providers#azure-provider" >}})
+ - **AWS provider** (optional) - Allows you to [deploy and manage AWS resources]({{< ref "providers#aws-provider" >}})
+ - **Environment name** - The name of the environment to create
+1. Let the rad CLI run the following tasks:
+ 1. **Install Radius** - Radius installs the [control plane services]({{< ref architecture-concept >}}) in the `radius-system` namespace
+ 2. **Create the environment** - An environment resource is created in the Radius control plane. It maps to a Kubernetes namespace.
+ 3. **Add the Azure Cloud Provider** - The Azure cloud provider configuration is saved in the Radius control plane
+ 4. **Add the AWS Cloud Provider** - The AWS cloud provider configuration is saved in the Radius control plane
+ 5. **Create a workspace** - [Workspaces]({{< ref workspaces >}}) are local pointers to a cluster running Radius, and an environment. Workspaces are saved to the Radius config file (`~/.rad/config.yaml` on Linux and macOS, `%USERPROFILE%\.rad\config.yaml` on Windows)
+2. Verify the initialization by running:
+ ```bash
+ kubectl get deployments -n radius-system
+ ```
+
+ You should see:
+
+ ```
+ NAME READY UP-TO-DATE AVAILABLE AGE
+ ucp 1/1 1 1 53s
+ appcore-rp 1/1 1 1 53s
+ bicep-de 1/1 1 1 53s
+ contour-contour 1/1 1 1 46s
+ dapr-dashboard 1/1 1 1 35s
+ dapr-sidecar-injector 1/1 1 1 35s
+ dapr-sentry 1/1 1 1 35s
+ dapr-operator 1/1 1 1 35s
+ ```
+
+ You can also use [`rad env list`]({{< ref rad_env_list.md >}}) to see if the created environment gets listed:
+
+ ```bash
+ rad env list
+ ```
+
diff --git a/docs/content/operations/environments/providers-overview.png b/docs/content/operations/environments/overview/providers-overview.png
similarity index 100%
rename from docs/content/operations/environments/providers-overview.png
rename to docs/content/operations/environments/overview/providers-overview.png
diff --git a/docs/content/operations/environments/snippets/environment.bicep b/docs/content/operations/environments/overview/snippets/environment.bicep
similarity index 100%
rename from docs/content/operations/environments/snippets/environment.bicep
rename to docs/content/operations/environments/overview/snippets/environment.bicep
diff --git a/docs/content/operations/environments/workspaces/_index.md b/docs/content/operations/environments/workspaces/index.md
similarity index 98%
rename from docs/content/operations/environments/workspaces/_index.md
rename to docs/content/operations/environments/workspaces/index.md
index 2606bf3c3..91306ee93 100644
--- a/docs/content/operations/environments/workspaces/_index.md
+++ b/docs/content/operations/environments/workspaces/index.md
@@ -1,10 +1,10 @@
---
type: docs
-title: "Radius workspaces"
+title: "Overview: Radius workspaces"
linkTitle: "Workspaces"
description: "Learn how to handle multiple Radius platforms and environments with workspaces"
-weight: 100
-categories: "How-To"
+weight: 200
+categories: "Overview"
---
Workspaces allow you to manage multiple Radius platforms and environments using a local configuration file. You can easily define and switch between workspaces to deploy and manage applications across local, test, and production environments.
diff --git a/docs/content/operations/providers/_index.md b/docs/content/operations/providers/index.md
similarity index 98%
rename from docs/content/operations/providers/_index.md
rename to docs/content/operations/providers/index.md
index 4cdf15942..a1f8325f0 100644
--- a/docs/content/operations/providers/_index.md
+++ b/docs/content/operations/providers/index.md
@@ -38,7 +38,7 @@ The Azure provider allows you to deploy and connect to Azure resources from a se
#### Add a cloud provider when initializing an environment
-1. Initialize a new [environment]({{< ref "operations/environments" >}}) with `rad init`
+1. Initialize a new [environment]({{< ref "operations/environments/overview" >}}) with `rad init`
1. Select the Kubernetes cluster to install Radius into. Enter an environment name and base Kubernetes namespace to deploy the apps into.
1. Select "yes" to add a cloud provider and select Azure as the cloud provider
1. Specify your Azure subscription and resource group
@@ -83,7 +83,7 @@ The AWS provider allows you to deploy and connect to AWS resources from a Radius
#### Add a cloud provider when initializing an environment
-1. Initialize a new [environment]({{< ref "operations/environments" >}}) with `rad init`
+1. Initialize a new [environment]({{< ref "operations/environments/overview" >}}) with `rad init`
1. Select the Kubernetes cluster to install Radius into. Enter an environment name and base Kubernetes namespace to deploy the apps into.
1. Select "yes" to add a cloud provider and select AWS as the cloud provider
diff --git a/docs/content/reference/resource-schema/core-schema/environment-schema/index.md b/docs/content/reference/resource-schema/core-schema/environment-schema/index.md
index 045238f7e..e49a7e058 100644
--- a/docs/content/reference/resource-schema/core-schema/environment-schema/index.md
+++ b/docs/content/reference/resource-schema/core-schema/environment-schema/index.md
@@ -89,4 +89,4 @@ The [Kubernetes Metadata extension]({{< ref "/operations/platforms/kubernetes/ku
## Further reading
-- [Radius environments]({{< ref "operations/environments" >}})
+- [Radius environments]({{< ref "operations/environments/overview" >}})
diff --git a/docs/content/reference/resource-schema/core-schema/volumes/volume-azure-keyvault/_index.md b/docs/content/reference/resource-schema/core-schema/volumes/volume-azure-keyvault/index.md
similarity index 98%
rename from docs/content/reference/resource-schema/core-schema/volumes/volume-azure-keyvault/_index.md
rename to docs/content/reference/resource-schema/core-schema/volumes/volume-azure-keyvault/index.md
index 801bf28c8..f07cc2812 100644
--- a/docs/content/reference/resource-schema/core-schema/volumes/volume-azure-keyvault/_index.md
+++ b/docs/content/reference/resource-schema/core-schema/volumes/volume-azure-keyvault/index.md
@@ -12,7 +12,7 @@ Radius supports mounting an Azure Key Vault as a persistent volume to the contai
- [Azure Key Vault CSI Driver](https://azure.github.io/secrets-store-csi-driver-provider-azure/demos/standard-walkthrough/) installed on your cluster
- [Azure AD Workload Identity](https://azure.github.io/azure-workload-identity/docs/installation.html) installed on your cluster
-- `azure.com.workload` identity configured on your [environment]({{< ref "operations/environments" >}})
+- `azure.com.workload` identity configured on your [environment]({{< ref "operations/environments/overview" >}})
- Your Azure Key Vault access policy should be set to [Azure role-based access control](https://learn.microsoft.com/azure/key-vault/general/rbac-guide?tabs=azure-cli)
## Resource format
diff --git a/docs/layouts/partials/page-meta-links.html b/docs/layouts/partials/page-meta-links.html
index 06b57245d..2e117191d 100644
--- a/docs/layouts/partials/page-meta-links.html
+++ b/docs/layouts/partials/page-meta-links.html
@@ -19,7 +19,7 @@
{{ end }}
{{ $editURL := printf "%s/edit/%s" $gh_repo $gh_repo_path }}
{{ $createURL := printf "%s/edit/%s" $gh_repo $gh_repo_path }}
- {{ $issuesURL := printf "%s/issues/new?title=%s" $gh_repo (safeURL $.Title )}}
+ {{ $issuesURL := printf "%s/issues/new/choose" $gh_repo }}
{{ $newPageStub := resources.Get "stubs/new-page-template.md" }}
{{ $newPageQS := querify "value" $newPageStub.Content "filename" "change-me.md" | safeURL }}
{{ $newPageURL := printf "%s/new/%s?%s" $gh_repo $gh_repo_path $newPageQS }}
@@ -27,7 +27,7 @@
Edit this page
New docs issue
{{ if $gh_project_repo }}
- {{ $project_issueURL := printf "%s/issues/new" $gh_project_repo }}
+ {{ $project_issueURL := printf "%s/issues/new/choose" $gh_project_repo }}
New project issue
{{ end }}
diff --git a/docs/layouts/partials/sidebar-tree.html b/docs/layouts/partials/sidebar-tree.html
index 3b33f9059..1a63da336 100644
--- a/docs/layouts/partials/sidebar-tree.html
+++ b/docs/layouts/partials/sidebar-tree.html
@@ -5,14 +5,14 @@
{{ if not .Site.Params.ui.sidebar_search_disable -}}
{{ else -}}
+ {{ with $title }}
+
+ {{ end }}
+{{ end }}
\ No newline at end of file
{{ . }}
+ {{ end }} +-
+ {{ range $taxonomy }}
+
- {{ .Page.Title }}{{ .Count }} + {{ end }} +