migrate docs to mdx

website/docs/cli/workspaces/index.mdx

@@ -1,28 +1,29 @@
 ---
-layout: "docs"
-page_title: "Managing Workspaces - Terraform CLI"
-description: "Commands to list, select, create, and output workspaces. Workspaces help manage different groups of resources with one configuration."
+page_title: Managing Workspaces - Terraform CLI
+description: >-
+  Commands to list, select, create, and output workspaces. Workspaces help
+  manage different groups of resources with one configuration.
 ---
 
 # Managing Workspaces
 
 In Terraform CLI, _workspaces_ are separate instances of
-[state data](/docs/language/state/index.html) that can be used from the same working
+[state data](/language/state) that can be used from the same working
 directory. You can use workspaces to manage multiple non-overlapping groups of
 resources with the same configuration.
 
-- Every [initialized working directory](/docs/cli/init/index.html) has at least
+- Every [initialized working directory](/cli/init) has at least
   one workspace. (If you haven't created other workspaces, it is a workspace
   named `default`.)
 - For a given working directory, only one workspace can be _selected_ at a time.
-- Most Terraform commands (including [provisioning](/docs/cli/run/index.html)
-  and [state manipulation](/docs/cli/state/index.html) commands) only interact
+- Most Terraform commands (including [provisioning](/cli/run)
+  and [state manipulation](/cli/state) commands) only interact
   with the currently selected workspace.
-- Use [the `terraform workspace select` command](/docs/cli/commands/workspace/select.html)
+- Use [the `terraform workspace select` command](/cli/commands/workspace/select)
   to change the currently selected workspace.
-- Use the [`terraform workspace list`](/docs/cli/commands/workspace/list.html),
-  [`terraform workspace new`](/docs/cli/commands/workspace/new.html), and
-  [`terraform workspace delete`](/docs/cli/commands/workspace/delete.html) commands
+- Use the [`terraform workspace list`](/cli/commands/workspace/list),
+  [`terraform workspace new`](/cli/commands/workspace/new), and
+  [`terraform workspace delete`](/cli/commands/workspace/delete) commands
   to manage the available workspaces in the current working directory.
 
 -> **Note:** Terraform Cloud and Terraform CLI both have features called
@@ -35,19 +36,19 @@ Since most of the resources you can manage with Terraform don't include a unique
 name as part of their configuration, it's common to use the same Terraform
 configuration to provision multiple groups of similar resources.
 
-Terraform relies on [state](/docs/language/state/index.html) to associate resources with
+Terraform relies on [state](/language/state) to associate resources with
 real-world objects, so if you run the same configuration multiple times with
 completely separate state data, Terraform can manage many non-overlapping groups
 of resources. In some cases you'll want to change
-[variable values](/docs/language/values/variables.html) for these different
+[variable values](/language/values/variables) for these different
 resource collections (like when specifying differences between staging and
 production deployments), and in other cases you might just want many instances
 of a particular infrastructure pattern.
 
 The simplest way to maintain multiple instances of a configuration with
 completely separate state data is to use multiple
-[working directories](/docs/cli/init/index.html) (with different
-[backend](/docs/language/settings/backends/configuration.html) configurations per directory, if you
+[working directories](/cli/init) (with different
+[backend](/language/settings/backends/configuration) configurations per directory, if you
 aren't using the default `local` backend).
 
 However, this isn't always the most _convenient_ way to handle separate states.
@@ -69,9 +70,9 @@ workspace has its own Terraform configuration, set of variable values, state
 data, run history, and settings.
 
 These two kinds of workspaces are different, but related. When [using Terraform
-CLI as a frontend for Terraform Cloud](/docs/cli/cloud/index.html), you can associate the current working
+CLI as a frontend for Terraform Cloud](/cli/cloud), you can associate the current working
 directory with one or more remote workspaces. If you associate the
 directory with multiple workspaces (using workspace tags), you can use the
 `terraform workspace` commands to select which remote workspace to use.
 
-Refer to [CLI-driven Runs](/docs/cloud/run/cli.html) in the Terraform Cloud documentation for more details about using Terraform CLI with Terraform Cloud.
+Refer to [CLI-driven Runs](/cloud-docs/run/cli) in the Terraform Cloud documentation for more details about using Terraform CLI with Terraform Cloud.