website: Version notes: Add new -> old links to 0.12 language docs (except function pages)

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

@@ -8,6 +8,10 @@ description: |-
 
 # Data Sources
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Data Sources](../configuration-0-11/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 make use of information defined outside of Terraform,

website/docs/configuration/expressions.html.md

@@ -9,6 +9,10 @@ description: |-
 
 # Expressions
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Interpolation Syntax](../configuration-0-11/interpolation.html).
+
 _Expressions_ are used to refer to or compute values within a configuration.
 The simplest expressions are just literal values, like `"hello"` or `5`,
 but the Terraform language also allows more complex expressions such as

website/docs/configuration/functions.html.md

@@ -9,6 +9,10 @@ description: |-
 
 # Built-in Functions
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Interpolation Syntax](../configuration-0-11/interpolation.html).
+
 The Terraform language includes a number of built-in functions that you can
 call from within expressions to transform and combine values. The general
 syntax for function calls is a function name followed by comma-separated

website/docs/configuration/index.html.md

@@ -10,6 +10,10 @@ description: |-
 
 # Configuration Language
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language](../configuration-0-11/index.html).
+
 Terraform uses its own configuration language, designed to allow concise
 descriptions of infrastructure. The Terraform language is declarative,
 describing an intended goal rather than the steps to reach that goal.

website/docs/configuration/locals.html.md

@@ -9,6 +9,10 @@ description: |-
 
 # Local Values
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Local Values](../configuration-0-11/locals.html).
+
 A local value assigns a name to an [expression](./expressions.html),
 allowing it to be used multiple times within a module without repeating
 it.

website/docs/configuration/modules.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Modules
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Modules](../configuration-0-11/modules.html).
+
 A _module_ is a container for multiple resources that are used together.
 
 Every Terraform configuration has at least one module, known as its

website/docs/configuration/outputs.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Output Values
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Output Values](../configuration-0-11/outputs.html).
+
 Output values are like the return values of a Terraform module, and have several
 uses:
 

website/docs/configuration/override.html.md

@@ -9,6 +9,10 @@ description: |-
 
 # Override Files
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Override Files](../configuration-0-11/override.html).
+
 Terraform normally loads all of the `.tf` and `.tf.json` files within a
 directory and expects each one to define a distinct set of configuration
 objects. If two files attempt to define the same object, Terraform returns

website/docs/configuration/providers.html.md

@@ -8,6 +8,10 @@ description: |-
 
 # Providers
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Providers](../configuration-0-11/providers.html).
+
 While [resources](./resources.html) are the primary construct
 in the Terraform language, the _behaviors_ of resources rely on their
 associated resource types, and these types are defined by _providers_.

website/docs/configuration/resources.html.md

@@ -10,6 +10,10 @@ description: |-
 
 # Resources
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Resources](../configuration-0-11/resources.html).
+
 _Resources_ are the most important element in the Terraform language.
 Each resource block describes one or more infrastructure objects, such
 as virtual networks, compute instances, or higher-level components such

website/docs/configuration/style.html.md

@@ -10,6 +10,10 @@ description: |-
 
 # Style Conventions
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language](../configuration-0-11/index.html).
+
 The Terraform parser allows you some flexibility in how you lay out the
 elements in your configuration files, but the Terraform language also has some
 idiomatic style conventions which we recommend users always follow

website/docs/configuration/syntax-json.html.md

@@ -9,6 +9,11 @@ description: |-
 
 # JSON Configuration Syntax
 
+-> **Note:** This page is about Terraform 0.12 and later. The JSON configuration
+syntax in 0.11 and earlier was never formally documented. For other information
+about Terraform 0.11 and earlier, see
+[0.11 Configuration Language](../configuration-0-11/index.html).
+
 Most Terraform configurations are written in
 [the native Terraform language syntax](./syntax.html), which is designed to be
 easy for humans to read and update.

website/docs/configuration/syntax.html.md

@@ -10,6 +10,10 @@ description: |-
 
 # Configuration Syntax
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Syntax](../configuration-0-11/syntax.html).
+
 Other pages in this section have described various configuration constructs
 that can appear in the Terraform language. This page describes the lower-level
 syntax of the language in more detail, revealing the building blocks that

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

@@ -8,6 +8,10 @@ description: |-
 
 # Terraform Push Configuration
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Configuring Terraform Push](../configuration-0-11/terraform-enterprise.html).
+
 Prior to v0.12, Terraform included mechanisms to interact with a legacy version
 of Terraform Enterprise, formerly known as "Atlas".
 

website/docs/configuration/terraform.html.md

@@ -9,6 +9,10 @@ description: |-
 
 # Terraform Settings
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Terraform Settings](../configuration-0-11/terraform.html).
+
 The special `terraform` configuration block type is used to configure some
 behaviors of Terraform itself, such as requiring a minimum Terraform version to
 apply your configuration.

website/docs/configuration/types.html.md

@@ -9,6 +9,11 @@ description: |-
 
 # Type Constraints
 
+-> **Note:** This page is about Terraform 0.12 and later, and documents a
+feature that did not exist in older versions. For other information about
+Terraform 0.11 and earlier, see
+[0.11 Configuration Language](../configuration-0-11/index.html).
+
 Terraform module authors and provider developers can use detailed type
 constraints to validate user-provided values for their input variables and
 resource arguments. This requires some additional knowledge about Terraform's

website/docs/configuration/variables.html.md

@@ -9,6 +9,10 @@ description: |-
 
 # Input Variables
 
+-> **Note:** This page is about Terraform 0.12 and later. For Terraform 0.11 and
+earlier, see
+[0.11 Configuration Language: Input Variables](../configuration-0-11/variables.html).
+
 Input variables serve as parameters for a Terraform module, allowing aspects
 of the module to be customized without altering the module's own source code,
 and allowing modules to be shared between different configurations.