website: Version notes: Add old -> new links to 0.11 docs

website/docs/configuration-0-11/data-sources.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Data Sources
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language: Configuring Data Sources](../configuration/data-sources.html).
+
 *Data sources* allow data to be fetched or computed for use elsewhere
 in Terraform configuration. Use of data sources allows a Terraform
 configuration to build on information defined outside of Terraform,

website/docs/configuration-0-11/environment-variables.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Environment Variables
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Commands: Environment Variables](../commands/environment-variables.html).
+
 ## TF_LOG
 
 If set to any value, enables detailed logs to appear on stderr which is useful for debugging. For example:

website/docs/configuration-0-11/index.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Configuration Language
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language](../configuration/index.html).
+
 Terraform uses text files to describe infrastructure and to set variables.
 These text files are called Terraform _configurations_ and end in
 `.tf`. This section talks about the format of these files as well as

website/docs/configuration-0-11/interpolation.html.md

@@ -8,6 +8,11 @@ description: |-
 
 # Interpolation Syntax
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language: Expressions](../configuration/expressions.html) and
+[Configuration Language: Functions](../configuration/functions.html).
+
 Embedded within strings in Terraform, whether you're using the
 Terraform syntax or JSON syntax, you can interpolate other values. These
 interpolations are wrapped in `${}`, such as `${var.foo}`.

website/docs/configuration-0-11/load.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Load Order and Semantics
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language](../configuration/index.html).
+
 When invoking any command that loads the Terraform configuration,
 Terraform loads all configuration files within the directory
 specified in alphabetical order.

website/docs/configuration-0-11/locals.html.md

@@ -9,6 +9,10 @@ description: |-
 
 # Local Values
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language: Configuring Local Values](../configuration/locals.html).
+
 Local values assign a name to an expression, that can then be used multiple
 times within a module.
 

website/docs/configuration-0-11/modules.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Module
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language: Modules](../configuration/modules.html).
+
 Modules are used in Terraform to modularize and encapsulate groups of
 resources in your infrastructure. For more information on modules, see
 the dedicated

website/docs/configuration-0-11/outputs.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Output Values
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language: Output Values](../configuration/outputs.html).
+
 Outputs define values that will be highlighted to the user
 when Terraform applies, and can be queried easily using the
 [output command](/docs/commands/output.html). Output usage

website/docs/configuration-0-11/override.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Override Files
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language: Override Files](../configuration/override.html).
+
 Terraform loads all configuration files within a directory and
 appends them together. Terraform also has a concept of _overrides_,
 a way to create files that are loaded last and _merged_ into your

website/docs/configuration-0-11/providers.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Providers
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language: Providers](../configuration/providers.html).
+
 Providers are responsible in Terraform for managing the lifecycle
 of a [resource](/docs/configuration/resources.html): create,
 read, update, delete.

website/docs/configuration-0-11/resources.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Resources
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language: Resources](../configuration/resources.html).
+
 The most important thing you'll configure with Terraform are
 resources. Resources are a component of your infrastructure.
 It might be some low level component such as a physical server,

website/docs/configuration-0-11/syntax.html.md

@@ -12,6 +12,10 @@ description: |-
 
 # Configuration Syntax
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language: Syntax](../configuration/syntax.html).
+
 The syntax of Terraform configurations is called [HashiCorp Configuration
 Language (HCL)](https://github.com/hashicorp/hcl). It is meant to strike a
 balance between human readable and editable as well as being machine-friendly.

website/docs/configuration-0-11/terraform-enterprise.html.md

@@ -8,6 +8,9 @@ description: |-
 
 # Terraform Push Configuration
 
+-> **Note:** This page is about Terraform 0.11 and earlier, and documents a
+feature that was removed in Terraform 0.12.
+
 ~> **Important:** The `terraform push` command is deprecated, and only works with [the legacy version of Terraform Enterprise](/docs/enterprise-legacy/index.html). In the current version of Terraform Enterprise, you can upload configurations using the API. See [the docs about API-driven runs](/docs/enterprise/run/api.html) for more details.
 
 The [`terraform push` command](/docs/commands/push.html) uploads a configuration to a Terraform Enterprise (legacy) environment. The name of the environment (and the organization it's in) can be specified on the command line, or as part of the Terraform configuration in an `atlas` block.

website/docs/configuration-0-11/terraform.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Terraform Settings
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language: Terraform Settings](../configuration/terraform.html).
+
 The `terraform` configuration section is used to configure Terraform itself,
 such as requiring a minimum Terraform version to execute a configuration.
 

website/docs/configuration-0-11/variables.html.md

@@ -9,6 +9,10 @@ description: |-
 
 # Input Variables
 
+-> **Note:** This page is about Terraform 0.11 and earlier. For Terraform 0.12
+and later, see
+[Configuration Language: Input Variables](../configuration/variables.html).
+
 Input variables serve as parameters for a Terraform module.
 
 When used in the root module of a configuration, variables can be set from CLI