Splitting up the "Set configuration parameters" page (#1170)

Author: rkoron007

content/terraform-docs-common/docs/cloud-docs/users-teams-organizations/permissions/workspace.mdx

@@ -121,7 +121,7 @@ Allows users to read, queue, and comment on Terraform plans in a workspace. Regu
 
 ### Apply <a id="run-apply"></a>
 
-Allows users to read, plan, approve, and apply Terraform plans. Granting this permission allows team members to change real infrastructure. 
+Allows users to read, plan, approve, and apply Terraform plans. Granting this permission allows team members to change real infrastructure.
 
 ## Variable access
 
@@ -142,7 +142,7 @@ Allows users to view the values of Terraform variables and environment variables
 
 ### Read and write <a id="variable-read-write"></a>
 
-Allows users to read and edit the values of variables in the workspace. 
+Allows users to read and edit the values of variables in the workspace.
 
 
 ## State access
@@ -162,13 +162,13 @@ No access is granted to the state file from the workspace.
 
 ### Read outputs only <a id="state-read-outputs"></a>
 
-Allows users to access values in the workspace's most recent Terraform state that have been explicitly marked as public outputs. Refer to [Define outputs to expose module data](/terraform/language/parameterize#define-outputs-to-expose-module-data) to learn more.
+Allows users to access values in the workspace's most recent Terraform state that have been explicitly marked as public outputs. Refer to [Define outputs to expose module data](/terraform/language/values/outputs#define-outputs-to-expose-module-data) to learn more.
 
 Configuration authors often use output values to interface with other workspaces that manage loosely-coupled collections of infrastructure. Making output values readable lets people who have no direct responsibility for the managed infrastructure in one workspace still indirectly use some of its functions in their workspaces.
 
 This permission is required to use the following features:
 
- - Call the [`/state-versions` API endpoint](/terraform/cloud-docs/api-docs/state-version-outputs) 
+ - Call the [`/state-versions` API endpoint](/terraform/cloud-docs/api-docs/state-version-outputs)
  - Run the [`terraform output` command](/terraform/cli/commands/output)
  - Use the [`terraform_remote_state` data source](/terraform/language/state/remote-state-data) against the workspace.
 
@@ -178,7 +178,7 @@ Allows users to read complete state files from the workspace. State files are us
 
 ### Read and write <a id="state-read-write"></a>
 
-Allows users to read and directly create new state versions in the workspace. This permission is required for performing local runs when the workspace's execution mode is set to **Local**. 
+Allows users to read and directly create new state versions in the workspace. This permission is required for performing local runs when the workspace's execution mode is set to **Local**.
 
 This permission is also required to use any of the [Terraform CLI's state manipulation and maintenance commands](/terraform/cli/state) against this workspace, including `terraform import`, `terraform taint`, and the various `terraform state` subcommands.
 

content/terraform-docs-common/redirects.jsonc

@@ -553,70 +553,6 @@
     "destination": "/terraform/language/v:version/checks",
     "permanent": true
   },
-  // values → parameterize
-  {
-    "source": "/terraform/language/values",
-    "destination": "/terraform/language/parameterize",
-    "permanent": true
-  },
-  {
-    "source": "/terraform/language/v:version(1\\.(?:[1-9]|1[01])\\.x)/parameterize",
-    "destination": "/terraform/language/v:version/values",
-    "permanent": true
-  },
-  {
-    "source": "/terraform/language/v:version((?:1\\.(?:1[2-9]|[2-9]\\d)|[2-9]\\d*\\.\\d+)\\.x)/values",
-    "destination": "/terraform/language/v:version/parameterize",
-    "permanent": true
-  },
-  // values/locals → block/locals
-  {
-    "source": "/terraform/language/values/locals",
-    "destination": "/terraform/language/block/locals",
-    "permanent": true
-  },
-  {
-    "source": "/terraform/language/v:version(1\\.(?:[1-9]|1[01])\\.x)/block/locals",
-    "destination": "/terraform/language/v:version/values/locals",
-    "permanent": true
-  },
-  {
-    "source": "/terraform/language/v:version((?:1\\.(?:1[2-9]|[2-9]\\d)|[2-9]\\d*\\.\\d+)\\.x)/values/locals",
-    "destination": "/terraform/language/v:version/block/locals",
-    "permanent": true
-  },
-  // values/variables → block/variable
-  {
-    "source": "/terraform/language/values/variables",
-    "destination": "/terraform/language/block/variable",
-    "permanent": true
-  },
-  {
-    "source": "/terraform/language/v:version(1\\.(?:[1-9]|1[01])\\.x)/block/variable",
-    "destination": "/terraform/language/v:version/values/variables",
-    "permanent": true
-  },
-  {
-    "source": "/terraform/language/v:version((?:1\\.(?:1[2-9]|[2-9]\\d)|[2-9]\\d*\\.\\d+)\\.x)/values/variables",
-    "destination": "/terraform/language/v:version/block/variable",
-    "permanent": true
-  },
-  // values/outputs → block/output
-  {
-    "source": "/terraform/language/values/outputs",
-    "destination": "/terraform/language/block/output",
-    "permanent": true
-  },
-  {
-    "source": "/terraform/language/v:version(1\\.(?:[1-9]|1[01])\\.x)/block/output",
-    "destination": "/terraform/language/v:version/values/outputs",
-    "permanent": true
-  },
-  {
-    "source": "/terraform/language/v:version((?:1\\.(?:1[2-9]|[2-9]\\d)|[2-9]\\d*\\.\\d+)\\.x)/values/outputs",
-    "destination": "/terraform/language/v:version/block/output",
-    "permanent": true
-  },
   // /terraform → block/terraform
   {
     "source": "/terraform/language/terraform",
@@ -650,19 +586,19 @@
     "permanent": true
   },
     // redir for /data block older than 1.11
-  {    
+  {
     "source": "/terraform/language/v:version(1\\.(?:[1-9]|1[01])\\.x)/block/data",
     "destination": "/terraform/language/v:version/data-sources",
     "permanent": true
   },
     // redir for /removed block older than 1.11
-  {    
+  {
     "source": "/terraform/language/v:version(1\\.(?:[1-9]|1[01])\\.x)/block/removed",
     "destination": "/terraform/language/v:version/resources/syntax#removing-resources",
     "permanent": true
   },
     // redir for /import block older than 1.11
-  {    
+  {
     "source": "/terraform/language/v:version(1\\.(?:[1-9]|1[01])\\.x)/block/import",
     "destination": "/terraform/language/v:version/import  ",
     "permanent": true

content/terraform-enterprise/1.1.x/docs/enterprise/users-teams-organizations/permissions/workspace.mdx

@@ -113,7 +113,7 @@ Allows users to read, queue, and comment on Terraform plans in a workspace. Regu
 
 ### Apply <a id="run-apply"></a>
 
-Allows users to read, plan, approve, and apply Terraform plans. Granting this permission allows team members to change real infrastructure. 
+Allows users to read, plan, approve, and apply Terraform plans. Granting this permission allows team members to change real infrastructure.
 
 ## Variable access
 
@@ -135,7 +135,7 @@ Allows users to view the values of Terraform variables and environment variables
 
 ### Read and write <a id="variable-read-write"></a>
 
-Allows users to read and edit the values of variables in the workspace. 
+Allows users to read and edit the values of variables in the workspace.
 
 ## State access
 
@@ -154,13 +154,13 @@ No access is granted to the state file from the workspace.
 
 ### Read outputs only <a id="state-read-outputs"></a>
 
-Allows users to access values in the workspace's most recent Terraform state that have been explicitly marked as public outputs. Refer to [Define outputs to expose module data](/terraform/language/parameterize#define-outputs-to-expose-module-data) to learn more.
+Allows users to access values in the workspace's most recent Terraform state that have been explicitly marked as public outputs. Refer to [Define outputs to expose module data](/terraform/language/values/outputs#define-outputs-to-expose-module-data) to learn more.
 
 Configuration authors often use output values to interface with other workspaces that manage loosely-coupled collections of infrastructure. Making output values readable lets people who have no direct responsibility for the managed infrastructure in one workspace still indirectly use some of its functions in their workspaces.
 
 This permission is required to use the following features:
 
--   Call the [`/state-versions` API endpoint](/terraform/enterprise/api-docs/state-version-outputs) 
+-   Call the [`/state-versions` API endpoint](/terraform/enterprise/api-docs/state-version-outputs)
 -   Run the [`terraform output` command](/terraform/cli/commands/output)
 -   Use the [`terraform_remote_state` data source](/terraform/language/state/remote-state-data) against the workspace.
 
@@ -170,7 +170,7 @@ Allows users to read complete state files from the workspace. State files are us
 
 ### Read and write <a id="state-read-write"></a>
 
-Allows users to read and directly create new state versions in the workspace. This permission is required for performing local runs when the workspace's execution mode is set to **Local**. 
+Allows users to read and directly create new state versions in the workspace. This permission is required for performing local runs when the workspace's execution mode is set to **Local**.
 
 This permission is also required to use any of the [Terraform CLI's state manipulation and maintenance commands](/terraform/cli/state) against this workspace, including `terraform import`, `terraform taint`, and the various `terraform state` subcommands.
 

content/terraform/v1.12.x/data/language-nav-data.json

@@ -56,9 +56,26 @@
     ]
   },
   {
-    "title": "Set configuration parameters",
-    "path": "parameterize",
-    "alias": "variables, outputs, locals"
+    "title": "Manage values in modules",
+    "alias": "variables, outputs, locals",
+    "routes": [
+      {
+        "title": "Overview",
+        "path": "values"
+      },
+      {
+        "title": "Use variables",
+        "path": "values/variables"
+      },
+      {
+        "title": "Use locals",
+        "path": "values/locals"
+      },
+      {
+        "title": "Use outputs",
+        "path": "values/outputs"
+      }
+    ]
   },
     {
     "title": "Manage sensitive data",

content/terraform/v1.12.x/docs/cli/commands/import.mdx

@@ -68,7 +68,7 @@ The command-line flags are all optional. The following flags are available:
   [literal expressions](/terraform/language/expressions/types) in the
   Terraform language, so list and map values can be specified via this flag.
 - `-var-file=foo` - Set variables in the Terraform configuration from
-  a [variable file](/terraform/language/parameterize#variable-definition-files). If
+  a [variable file](/terraform/language/values/variables#variable-definition-files). If
   `terraform.tfvars` or any `.auto.tfvars` files are present in the current
   directory, they are automatically loaded. Terraform loads `terraform.tfvars`
   first and the `.auto.tfvars` files after in alphabetical order. Any files

content/terraform/v1.12.x/docs/cli/commands/plan.mdx

@@ -145,11 +145,11 @@ In addition to alternate [planning modes](#planning-modes), there are several op
 - `-var-file=FILENAME` - Sets values for potentially many
   [input variables](/terraform/language/block/variable) declared in the
   root module of the configuration, using definitions from a
-  [`.tfvars` file](/terraform/language/parameterize#variable-definition-files).
+  [`.tfvars` file](/terraform/language/values/variables#variable-definition-files).
   Use this option multiple times to include values from more than one file.
 There are several other ways to set values for input variables in the root
 module, aside from the `-var` and `-var-file` options. Refer to
-[Assign values to input variables](/terraform/language/parameterize#assign-values-to-input-variables) for more information.
+[Assign values to input variables](/terraform/language/values/variables#assign-values-to-input-variables) for more information.
 
 ### Input Variables on the Command Line
 
@@ -223,7 +223,7 @@ terraform plan -var "name=[\"a\", \"b\", \"c\"]"
 Similar constraints apply when setting input variables using environment
 variables. For more information on the various methods for setting root module
 input variables, see
-[Assign values to input variables](/terraform/language/parameterize#assign-values-to-input-variables).
+[Assign values to input variables](/terraform/language/values/variables#assign-values-to-input-variables).
 
 ### Resource Targeting
 

content/terraform/v1.12.x/docs/cli/config/environment-variables.mdx

@@ -61,7 +61,7 @@ export TF_VAR_alist='[1,2,3]'
 export TF_VAR_amap='{ foo = "bar", baz = "qux" }'
 ```
 
-For more on how to use `TF_VAR_name` in context, refer to [Environment variables](/terraform/language/parameterize#environment-variables).
+For more on how to use `TF_VAR_name` in context, refer to [Environment variables](/terraform/language/values/variables#environment-variables).
 
 ## TF_CLI_ARGS and TF_CLI_ARGS_name
 

content/terraform/v1.12.x/docs/language/block/locals.mdx

@@ -15,7 +15,7 @@ The `locals` block is similar to function-scoped variables in other programming
 
 You can define local values in any module. Local values can be any valid Terraform expression, and can reference variables, resource attributes, function outputs, or other local values to transform or combine data.
 
-To learn more about using `locals` blocks in your configurations, refer to [Define locals to reuse expressions](/terraform/language/parameterize#define-locals-to-reuse-expressions).
+To learn more about using `locals` blocks in your configurations, refer to [Use locals to reuse expressions](/terraform/language/values/locals).
 
 ## Configuration model
 

content/terraform/v1.12.x/docs/language/block/output.mdx

@@ -20,7 +20,7 @@ The value of an `output` block is similar to a return value in other programming
 
 In HCP Terraform, your `output` block values appear in the UI after Terraform applies your configuration. You can [mark outputs as sensitive in HCP Terraform](/terraform/cloud-docs/workspaces/variables/managing-variables#sensitive-values) to hide their values in the UI and in API responses.
 
-To learn more about using `output` blocks, refer to [Define outputs to expose module data](/terraform/language/parameterize#define-outputs-to-expose-module-data).
+To learn more about using `output` blocks, refer to [Use outputs to expose module data](/terraform/language/values/outputs).
 
 ## Configuration model
 

content/terraform/v1.12.x/docs/language/block/variable.mdx

@@ -5,7 +5,7 @@ description: Use variables to parameterize your configuration, making your modul
 
 # `variable` block reference
 
-Use the `variable` block to parameterize your configuration, making your modules dynamic, reusable, and flexible by letting them customize behavior with different values at run time.
+Use the `variable` block to parameterize your configuration so that module consumers can pass custom values into the configuration at runtime.
 
 > **Hands-on:** Try the [Customize Terraform Configuration with Variables](/terraform/tutorials/configuration-language/variables) tutorial.
 
@@ -17,7 +17,7 @@ You can define variables in root modules, or in child modules:
 - In the root modules, you can set variable values using CLI options, environment variables, variable definition files, or through an HCP Terraform workspace.
 - In child modules, the parent module passes values to child modules as arguments to the `module` block.
 
-To learn more about the different ways to use and set values for variables, refer to [Define module input arguments with variables](/terraform/language/parameterize#define-module-input-arguments-with-variables).
+To learn more about the different ways to use and set values for variables, refer to [Use variables to input module arguments](/terraform/language/values/variables).
 
 ## Configuration model