diff --git a/assets/styles/themes/dark/kapacitor.scss b/assets/styles/themes/dark/kapacitor.scss
index f02befae3..8f5fdbf7e 100644
--- a/assets/styles/themes/dark/kapacitor.scss
+++ b/assets/styles/themes/dark/kapacitor.scss
@@ -8,11 +8,11 @@ $kapacitor-dropdown-gradient: $grad-GarageBand;
 $kapacitor-sidebar-search-highlight: $gr-rainforest;
 
 // Left Navigation
-$kapacitor-nav-category: $gr-rainforest;
-$kapacitor-nav-category-hover: $b-laser;
+$kapacitor-nav-category: $gr-viridian;
+$kapacitor-nav-category-hover: $br-chartreuse;
 $kapacitor-nav-item-hover: $b-laser;
-$kapacitor-nav-toggle-bg-hover: $gr-rainforest;
-$kapacitor-nav-active: $p-potassium;
+$kapacitor-nav-toggle-bg-hover: $gr-viridian;
+$kapacitor-nav-active: $br-chartreuse;
 
 // Article Content
 $kapacitor-article-heading: $g20-white;
diff --git a/assets/styles/themes/light/kapacitor.scss b/assets/styles/themes/light/kapacitor.scss
index 8e56f421a..ab3474f4f 100644
--- a/assets/styles/themes/light/kapacitor.scss
+++ b/assets/styles/themes/light/kapacitor.scss
@@ -9,9 +9,9 @@ $kapacitor-sidebar-search-highlight: $gr-viridian !default;
 
 // Left Navigation
 $kapacitor-nav-category: $gr-viridian !default;
-$kapacitor-nav-category-hover: $b-dodger !default;
+$kapacitor-nav-category-hover: $p-star !default;
 $kapacitor-nav-item-hover: $b-dodger !default;
-$kapacitor-nav-toggle-bg-hover: $gr-viridian !default;
+$kapacitor-nav-toggle-bg-hover: $p-star !default;
 $kapacitor-nav-active: $p-star !default;
 
 // Article Content
diff --git a/content/influxdb/v1.7/flux/guides/manipulate-timestamps.md b/content/influxdb/v1.7/flux/guides/manipulate-timestamps.md
index ffe71f39a..e087a4698 100644
--- a/content/influxdb/v1.7/flux/guides/manipulate-timestamps.md
+++ b/content/influxdb/v1.7/flux/guides/manipulate-timestamps.md
@@ -22,8 +22,8 @@ Use Flux to process and manipulate timestamps to suit your needs.
 {{% note %}}
 If you're just getting started with Flux queries, check out the following:
 
-- [Get started with Flux](/v2.0/query-data/get-started/) for a conceptual overview of Flux and parts of a Flux query.
-- [Execute queries](/v2.0/query-data/execute-queries/) to discover a variety of ways to run your queries.
+- [Get started with Flux](/influxdb/v1.7/flux/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v1.7/flux/guides/execute-queries/) to discover a variety of ways to run your queries.
 {{% /note %}}
 
 
@@ -34,8 +34,8 @@ If you're just getting started with Flux queries, check out the following:
 
 ### Unix nanosecond to RFC3339
 Use the [`time()` function](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/type-conversions/time/)
-to convert a [Unix **nanosecond** timestamp](/v2.0/reference/glossary/#unix-timestamp)
-to an [RFC3339 timestamp](/v2.0/reference/glossary/#rfc3339-timestamp).
+to convert a [Unix **nanosecond** timestamp](/{{< latest "influxdb" "v2" >}}/reference/glossary/#unix-timestamp)
+to an [RFC3339 timestamp](/{{< latest "influxdb" "v2" >}}/reference/glossary/#rfc3339-timestamp).
 
 ```js
 time(v: 1568808000000000000)
diff --git a/content/influxdb/v1.8/flux/guides/manipulate-timestamps.md b/content/influxdb/v1.8/flux/guides/manipulate-timestamps.md
index 84486f326..896ac7658 100644
--- a/content/influxdb/v1.8/flux/guides/manipulate-timestamps.md
+++ b/content/influxdb/v1.8/flux/guides/manipulate-timestamps.md
@@ -22,8 +22,8 @@ Use Flux to process and manipulate timestamps to suit your needs.
 {{% note %}}
 If you're just getting started with Flux queries, check out the following:
 
-- [Get started with Flux](/v2.0/query-data/get-started/) for a conceptual overview of Flux and parts of a Flux query.
-- [Execute queries](/v2.0/query-data/execute-queries/) to discover a variety of ways to run your queries.
+- [Get started with Flux](/influxdb/v1.8/flux/get-started/) for a conceptual overview of Flux and parts of a Flux query.
+- [Execute queries](/influxdb/v1.8/flux/guides/execute-queries/) to discover a variety of ways to run your queries.
 {{% /note %}}
 
 
@@ -34,8 +34,8 @@ If you're just getting started with Flux queries, check out the following:
 
 ### Unix nanosecond to RFC3339
 Use the [`time()` function](/{{< latest "influxdb" "v2" >}}/reference/flux/stdlib/built-in/transformations/type-conversions/time/)
-to convert a [Unix **nanosecond** timestamp](/v2.0/reference/glossary/#unix-timestamp)
-to an [RFC3339 timestamp](/v2.0/reference/glossary/#rfc3339-timestamp).
+to convert a [Unix **nanosecond** timestamp](/{{< latest "influxdb" "v2" >}}/reference/glossary/#unix-timestamp)
+to an [RFC3339 timestamp](/{{< latest "influxdb" "v2" >}}/reference/glossary/#rfc3339-timestamp).
 
 ```js
 time(v: 1568808000000000000)
diff --git a/content/influxdb/v2.0/_index.md b/content/influxdb/v2.0/_index.md
index ac791e27c..0c89d3667 100644
--- a/content/influxdb/v2.0/_index.md
+++ b/content/influxdb/v2.0/_index.md
@@ -5,10 +5,11 @@ description: >
   Learn how to use and leverage InfluxDB in use cases such as monitoring metrics, IoT data, and events.
 layout: landing-influxdb
 menu:
-  versions:
-    name: v2.0
+  influxdb_2_0:
+    name: InfluxDB v2.0
 aliases:
   - /v2.0/
+weight: 1
 ---
 
 #### Welcome
diff --git a/content/influxdb/v2.0/get-started.md b/content/influxdb/v2.0/get-started.md
index 68165d942..b29ce6091 100644
--- a/content/influxdb/v2.0/get-started.md
+++ b/content/influxdb/v2.0/get-started.md
@@ -4,7 +4,7 @@ description: Download, install, and setup InfluxDB, creating a default organizat
 menu:
   influxdb_2_0:
     name: Get started
-weight: 1
+weight: 2
 influxdb/v2.0/tags: [get-started, install]
 aliases:
   - /v2.0/cloud/get-started
@@ -146,7 +146,7 @@ If you're running `influx` on macOS Catalina, you must [manually authorize the I
 To avoid having to pass your InfluxDB [authentication token](/influxdb/v2.0/security/tokens/) with each `influx` command, set up a configuration profile that stores your credentials.
 
 In a terminal, run the following command:
-   
+
 ```sh
    # Set up a configuration profile
    influx config create -n default \
@@ -206,7 +206,7 @@ If you rename the binary, all references to `influx` in this documentation refer
 To avoid having to pass your InfluxDB [authentication token](/influxdb/v2.0/security/tokens/) with each `influx` command, set up a configuration profile that stores your credentials.
 
 In a terminal, run the following command:
-   
+
 ```sh
    # Set up a configuration profile
    influx config create -n default \
@@ -542,8 +542,8 @@ You are ready to [write or collect data](/influxdb/v2.0/write-data).
 
 If you set up InfluxDB through the UI and want to use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx), we recommend setting up a configuration profile. This lets you avoid having to pass your InfluxDB [authentication token](/influxdb/v2.0/security/tokens/) with each `influx` command. Complete the following steps to set up a configuration profile that stores your credentials.
 
-1. In a terminal, run the following command: 
-      
+1. In a terminal, run the following command:
+
     ```sh
       # Set up a configuration profile
       influx config create -n default \
diff --git a/content/v2.0/monitor-alert/send-email.md b/content/influxdb/v2.0/monitor-alert/send-email.md
similarity index 94%
rename from content/v2.0/monitor-alert/send-email.md
rename to content/influxdb/v2.0/monitor-alert/send-email.md
index ad4ef9a18..d7affc43b 100644
--- a/content/v2.0/monitor-alert/send-email.md
+++ b/content/influxdb/v2.0/monitor-alert/send-email.md
@@ -3,17 +3,17 @@ title: Send alert email
 description: >
   Send an alert email.
 menu:
-  v2_0:
+  influxdb_2_0:
     parent: Monitor & alert
 weight: 104
-v2.0/tags: [alert, email, notifications, check]
+influxdb/v2.0/tags: [alert, email, notifications, check]
 related:
-  - /v2.0/monitor-alert/checks/
+  - /influxdb/v2.0/monitor-alert/checks/
 ---
 
 Send an alert email using a third party service, such as [SendGrid](https://sendgrid.com/), [Amazon Simple Email Service (SES)](https://aws.amazon.com/ses/), [Mailjet](https://www.mailjet.com/), or [Mailgun](https://www.mailgun.com/). To send an alert email, complete the following steps:
 
-1. [Create a check](/v2.0/monitor-alert/checks/create/#create-a-check-in-the-influxdb-ui) to identify the data to monitor and the status to alert on.
+1. [Create a check](/influxdb/v2.0/monitor-alert/checks/create/#create-a-check-in-the-influxdb-ui) to identify the data to monitor and the status to alert on.
 2. Set up your preferred email service (sign up, retrieve API credentials, and send test email):
    - **SendGrid**: See [Getting Started With the SendGrid API](https://sendgrid.com/docs/API_Reference/api_getting_started.html)
    - **AWS Simple Email Service (SES)**: See [Using the Amazon SES API](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email.html). Your AWS SES request, including the `url` (endpoint), authentication, and the structure of the request may vary. For more information, see [Amazon SES API requests](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/using-ses-api-requests.html) and [Authenticating requests to the Amazon SES API](https://docs.aws.amazon.com/ses/latest/DeveloperGuide/using-ses-api-authentication.html).
@@ -22,7 +22,7 @@ Send an alert email using a third party service, such as [SendGrid](https://send
 3. [Create an alert email task](#create-an-alert-email-task) to call your email service and send an alert email.
 
   {{% note %}}
-  In the procedure below, we use the **Task** page in the InfluxDB UI (user interface) to create a task. Explore other ways to [create a task](/v2.0/process-data/manage-tasks/create-task/).
+  In the procedure below, we use the **Task** page in the InfluxDB UI (user interface) to create a task. Explore other ways to [create a task](/influxdb/v2.0/process-data/manage-tasks/create-task/).
   {{% /note %}}
 
 ### Create an alert email task
@@ -32,11 +32,11 @@ Send an alert email using a third party service, such as [SendGrid](https://send
     {{< nav-icon "tasks" >}}
 
 2. Click **{{< icon "plus" >}} Create Task**, and then select **New Task**.
-3. In the **Name** field, enter a descriptive name, for example, **Send alert email**, and then enter how often to run the task in the **Every** field, for example, `10m`. For more detail, such as using cron syntax or including an offset, see [Task configuration options](/v2.0/process-data/task-options/).
+3. In the **Name** field, enter a descriptive name, for example, **Send alert email**, and then enter how often to run the task in the **Every** field, for example, `10m`. For more detail, such as using cron syntax or including an offset, see [Task configuration options](/influxdb/v2.0/process-data/task-options/).
 
 4. In the right panel, enter the following detail in your **task script** (see [examples below](#examples)):
-   - Import the [Flux HTTP package](/v2.0/reference/flux/stdlib/http/).
-   - (Optional) Store your API key as a secret for reuse. First, [add your API key as a secret](/v2.0/security/secrets/manage-secrets/add/), and then import the [Flux InfluxDB Secrets package](/v2.0/reference/flux/stdlib/secrets/).
+   - Import the [Flux HTTP package](/influxdb/v2.0/reference/flux/stdlib/http/).
+   - (Optional) Store your API key as a secret for reuse. First, [add your API key as a secret](/influxdb/v2.0/security/secrets/manage-secrets/add/), and then import the [Flux InfluxDB Secrets package](/influxdb/v2.0/reference/flux/stdlib/secrets/).
    - Query the `statuses` measurement in the `_monitoring` bucket to retrieve all statuses generated by your check.
    - Set the time range to monitor; use the same interval that the task is scheduled to run. For example, `range (start: -task.every)`.
    - Set the `_level` to alert on, for example, `crit`, `warn`, `info`, or `ok`.
diff --git a/content/v2.0/monitor-alert/task-failure.md b/content/influxdb/v2.0/monitor-alert/task-failure.md
similarity index 87%
rename from content/v2.0/monitor-alert/task-failure.md
rename to content/influxdb/v2.0/monitor-alert/task-failure.md
index 0f6eb62c2..b88630dca 100644
--- a/content/v2.0/monitor-alert/task-failure.md
+++ b/content/influxdb/v2.0/monitor-alert/task-failure.md
@@ -4,10 +4,10 @@ seotitle: Alert on failed tasks.
 description: >
   Create an alert when a task fails.
 menu:
-  v2_0:
+  influxdb_2_0:
     parent: Monitor & alert
 weight: 201
-v2.0/tags: [tasks]
+influxdb/v2.0/tags: [tasks]
 ---
 
 Use a task to receive alerts when a task fails.
@@ -64,6 +64,6 @@ Once your task is ready, see [Create a task](/influxdb/v2.0/process-data/manage-
 {{% note %}}
 This script does not send an email alert.
 For information on how to create notification emails, see
-[Create notification endpoints](/v2.0/monitor-alert/notification-endpoints/create)
-and [Create notification rules](/v2.0/monitor-alert/notification-rules/create).
+[Create notification endpoints](/influxdb/v2.0/monitor-alert/notification-endpoints/create)
+and [Create notification rules](/influxdb/v2.0/monitor-alert/notification-rules/create).
 {{% /note %}}
diff --git a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md~master b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md~master
index fa5cfbe23..6fb53b0a5 100644
--- a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md~master
+++ b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/aws.md~master
@@ -13,23 +13,23 @@ Use the [AWS CloudWatch Monitoring template](https://github.com/influxdata/commu
 
 The AWS CloudWatch Monitoring template includes the following:
 
-- two [dashboards](/v2.0/reference/glossary/#dashboard):
+- two [dashboards](/influxdb/v2.0/reference/glossary/#dashboard):
   - **AWS CloudWatch NLB (Network Load Balancers) Monitoring**: Displays data from the `cloudwatch_aws_network_elb measurement`
   - **AWS CloudWatch Instance Monitoring**: Displays data from the `cloudwatch_aws_ec2` measurement
-- two [buckets](/v2.0/reference/glossary/#bucket): `kubernetes` and `cloudwatch`
+- two [buckets](/influxdb/v2.0/reference/glossary/#bucket): `kubernetes` and `cloudwatch`
 - two labels: `inputs.cloudwatch`, `AWS`
 - one variable: `v.bucket`
-- one [Telegraf configuration](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): [AWS CloudWatch input plugin](/v2.0/reference/telegraf-plugins/#cloudwatch)
+- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): [AWS CloudWatch input plugin](/influxdb/v2.0/reference/telegraf-plugins/#cloudwatch)
 
 ## Apply the template
 
-1. Use the [`influx` CLI](/v2.0/reference/cli/influx/) to run the following command:
+1. Use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to run the following command:
 
     ```sh
     influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/aws_cloudwatch/aws_cloudwatch.yml
     ```
-    For more information, see [influx apply](/v2.0/reference/cli/influx/apply/).
-2. [Install Telegraf](/telegraf/latest/introduction/installation/) on a server with network access to both the CloudWatch API and [InfluxDB v2 API](/v2.0/reference/api/).
+    For more information, see [influx apply](/influxdb/v2.0/reference/cli/influx/apply/).
+2. [Install Telegraf](/telegraf/latest/introduction/installation/) on a server with network access to both the CloudWatch API and [InfluxDB v2 API](/influxdb/v2.0/reference/api/).
 3. In your Telegraf configuration file (`telegraf.conf`), find the following example `influxdb_v2` output plugins, and then **replace** the `urls` to specify the servers to monitor:
 
    ```sh
@@ -47,7 +47,7 @@ The AWS CloudWatch Monitoring template includes the following:
      organization = "$INFLUX_ORG"
      bucket = “cloudwatch"
    ```
-4. [Start Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
+4. [Start Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
 
 ## View the incoming data
 
diff --git a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md~master b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md~master
index 8bb882870..5dcc3db03 100644
--- a/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md~master
+++ b/content/influxdb/v2.0/monitor-alert/templates/infrastructure/docker.md~master
@@ -10,41 +10,41 @@ weight: 202
 ---
 
 Use the [Docker Monitoring template](https://github.com/influxdata/community-templates/tree/master/docker) to monitor your Docker containers. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data).
-This template uses the [Docker input plugin](/v2.0/reference/telegraf-plugins/#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard.
+This template uses the [Docker input plugin](/influxdb/v2.0/reference/telegraf-plugins/#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard.
 
 The Docker Monitoring template includes the following:
 
-- one [dashboard](/v2.0/reference/glossary/#dashboard): **Docker**
-- one [bucket](/v2.0/reference/glossary/#bucket): `docker, 7d retention`
+- one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **Docker**
+- one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `docker, 7d retention`
 - labels: Docker input plugin labels
-- one [Telegraf configuration](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): Docker input plugin
+- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): Docker input plugin
 - one variable: `bucket`
-- four [checks](/v2.0/reference/glossary/#check): `Container cpu`, `mem`, `disk`, `non-zero exit`
-- one [notification endpoint](/v2.0/reference/glossary/#notification-endpoint): `Http Post`
-- one [notification rule](/v2.0/reference/glossary/#notification-rule): `Crit Alert`
+- four [checks](/influxdb/v2.0/reference/glossary/#check): `Container cpu`, `mem`, `disk`, `non-zero exit`
+- one [notification endpoint](/influxdb/v2.0/reference/glossary/#notification-endpoint): `Http Post`
+- one [notification rule](/influxdb/v2.0/reference/glossary/#notification-rule): `Crit Alert`
 
-For more information about how checks, notification endpoints, and notifications rules work together, see [monitor data and send alerts](/v2.0/monitor-alert/).
+For more information about how checks, notification endpoints, and notifications rules work together, see [monitor data and send alerts](/influxdb/v2.0/monitor-alert/).
 
 ## Apply the template
 
-1. Use the [`influx` CLI](/v2.0/reference/cli/influx/) to run the following command:
+1. Use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to run the following command:
 
     ```sh
     influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/docker/docker.yml
     ```
-    For more information, see [influx apply](/v2.0/reference/cli/influx/apply/).
+    For more information, see [influx apply](/influxdb/v2.0/reference/cli/influx/apply/).
 
     > **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](https://v2.docs.influxdata.com/v2.0/reference/cli/influx/config/).
 
-2. [Install Telegraf](/telegraf/latest/introduction/installation/) on a server with network access to both the Docker containers and [InfluxDB v2 API](/v2.0/reference/api/).
-3. In your [Telegraf configuration file (`telegraf.conf`)](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following:
-    - Depending on how you run Docker, you may need to customize the [Docker input plugin](/v2.0/reference/telegraf-plugins/#docker) configuration, for example, you may need to specify the `endpoint` value.
+2. [Install Telegraf](/telegraf/latest/introduction/installation/) on a server with network access to both the Docker containers and [InfluxDB v2 API](/influxdb/v2.0/reference/api/).
+3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following:
+    - Depending on how you run Docker, you may need to customize the [Docker input plugin](/influxdb/v2.0/reference/telegraf-plugins/#docker) configuration, for example, you may need to specify the `endpoint` value.
     - Set the following environment variables:
-      - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/v2.0/security/tokens/view-tokens/).
-      - INFLUX_ORG: Name of your organization. See how to [view your organization](/v2.0/organizations/view-orgs/).
+      - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/).
+      - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.0/organizations/view-orgs/).
       - INFLUX_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud.
 
-4. [Start Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
+4. [Start Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
 
 ## View incoming data
 
diff --git a/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md~master b/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md~master
index 1d4ac217f..061f03a4c 100644
--- a/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md~master
+++ b/content/influxdb/v2.0/monitor-alert/templates/networks/haproxy.md~master
@@ -10,35 +10,35 @@ weight: 201
 ---
 
 Use the [HAProxy for InfluxDB v2 template](https://github.com/influxdata/community-templates/tree/master/haproxy) to monitor your HAProxy instances. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data).
-This template uses the [HAProxy input plugin](/v2.0/reference/telegraf-plugins/#haproxy) to collect metrics stored in an HAProxy instance and display these metrics in a dashboard.
+This template uses the [HAProxy input plugin](/influxdb/v2.0/reference/telegraf-plugins/#haproxy) to collect metrics stored in an HAProxy instance and display these metrics in a dashboard.
 
 The HAProxy for InfluxDB v2 template includes the following:
 
-- one [dashboard](/v2.0/reference/glossary/#dashboard): **HAProxy**
-- one [bucket](/v2.0/reference/glossary/#bucket): `haproxy`
+- one [dashboard](/influxdb/v2.0/reference/glossary/#dashboard): **HAProxy**
+- one [bucket](/influxdb/v2.0/reference/glossary/#bucket): `haproxy`
 - label: `haproxy`
-- one [Telegraf configuration](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): HAProxy input plugin, InfluxDB v2 output plugin
+- one [Telegraf configuration](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/): HAProxy input plugin, InfluxDB v2 output plugin
 - one variable: `bucket`
 
 ## Apply the template
 
-1. Use the [`influx` CLI](/v2.0/reference/cli/influx/) to run the following command:
+1. Use the [`influx` CLI](/influxdb/v2.0/reference/cli/influx/) to run the following command:
 
     ```sh
     influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/haproxy/haproxy.yml
     ```
-    For more information, see [influx apply](/v2.0/reference/cli/influx/apply/).
+    For more information, see [influx apply](/influxdb/v2.0/reference/cli/influx/apply/).
 
     > **Note:** Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](https://v2.docs.influxdata.com/v2.0/reference/cli/influx/config/).
 
-2. [Install Telegraf](/telegraf/latest/introduction/installation/) on a server with network access to both the HAProxy instances and [InfluxDB v2 API](/v2.0/reference/api/).
-3. In your [Telegraf configuration file (`telegraf.conf`)](/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following:
+2. [Install Telegraf](/telegraf/latest/introduction/installation/) on a server with network access to both the HAProxy instances and [InfluxDB v2 API](/influxdb/v2.0/reference/api/).
+3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/view-telegraf-config/), do the following:
     - Set the following environment variables:
-      - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `haproxy` bucket. See how to [view tokens](/v2.0/security/tokens/view-tokens/).
-      - INFLUX_ORG: Name of your organization. See how to [view your organization](/v2.0/organizations/view-orgs/).
+      - INFLUX_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `haproxy` bucket. See how to [view tokens](/influxdb/v2.0/security/tokens/view-tokens/).
+      - INFLUX_ORG: Name of your organization. See how to [view your organization](/influxdb/v2.0/organizations/view-orgs/).
       - INFLUX_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud.
 
-4. [Start Telegraf](/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
+4. [Start Telegraf](/influxdb/v2.0/write-data/no-code/use-telegraf/auto-config/#start-telegraf).
 
 ## View incoming data
 
diff --git a/content/influxdb/v2.0/reference/cli/influx/_index.md b/content/influxdb/v2.0/reference/cli/influx/_index.md
index 8f205a398..17403da2d 100644
--- a/content/influxdb/v2.0/reference/cli/influx/_index.md
+++ b/content/influxdb/v2.0/reference/cli/influx/_index.md
@@ -27,7 +27,7 @@ influx [command]
 {{% note %}}
 #### Set your credentials
 
-1. To avoid having to pass your InfluxDB [authentication token](/v2.0/users/tokens/) with each `influx` command, set up a configuration profile if you haven't already.
+1. To avoid having to pass your InfluxDB [authentication token](/influxdb/v2.0/users/tokens/) with each `influx` command, set up a configuration profile if you haven't already.
 2. To see if you have a configuration profile, run `influx config`. If nothing is displayed, you don't have a configuration profile.
 3. To configure a profile, use the following command: `influx config create -n default -u $INFLUX_URL -o $INFLUX_ORG -t $INFLUX_TOKEN -a`.
    This configures a new profile named `default` and makes the profile active so commands run against this instance.
diff --git a/content/influxdb/v2.0/reference/sample-data.md b/content/influxdb/v2.0/reference/sample-data.md
index 779a22e48..f55dc3296 100644
--- a/content/influxdb/v2.0/reference/sample-data.md
+++ b/content/influxdb/v2.0/reference/sample-data.md
@@ -15,7 +15,7 @@ Use sample data to familiarize yourself with time series data and InfluxDB.
 InfluxData provides many sample time series datasets to use with **InfluxDB Cloud** and **InfluxDB**.
 
 ## InfluxDB Cloud demo data
-Use [InfluxDB Cloud demo data buckets](/v2.0/reference/sample-data/#influxdb-cloud-demo-data) for quick,
+Use [InfluxDB Cloud demo data buckets](/influxdb/v2.0/reference/sample-data/#influxdb-cloud-demo-data) for quick,
 free access to different types of sample data.
 
 {{< youtube GSaByPC1Bdc >}}
diff --git a/content/influxdb/v2.0/write-data/_index.md b/content/influxdb/v2.0/write-data/_index.md
index 4d6328bc5..965dcdb1b 100644
--- a/content/influxdb/v2.0/write-data/_index.md
+++ b/content/influxdb/v2.0/write-data/_index.md
@@ -160,7 +160,7 @@ The scraper stores the scraped metrics in the bucket created during the
 
 {{% note %}}
 Quick Start is only available in the last step of the setup process.
-If you missed the Quick Start option, you can [manually create a scraper](/v2.0/write-data/no-code/scrape-data/)
+If you missed the Quick Start option, you can [manually create a scraper](/influxdb/v2.0/write-data/no-code/scrape-data/)
 that scrapes data from the `/metrics` endpoint.
 {{% /note %}}
 
diff --git a/content/v2.0/write-data/bulk-ingest-cloud.md b/content/influxdb/v2.0/write-data/bulk-ingest-cloud.md
similarity index 83%
rename from content/v2.0/write-data/bulk-ingest-cloud.md
rename to content/influxdb/v2.0/write-data/bulk-ingest-cloud.md
index f720d8a99..c1409223c 100644
--- a/content/v2.0/write-data/bulk-ingest-cloud.md
+++ b/content/influxdb/v2.0/write-data/bulk-ingest-cloud.md
@@ -6,13 +6,13 @@ weight: 105
 description: >
   Write existing data to InfluxDB Cloud in bulk.
 menu:
-  v2_0:
+  influxdb_2_0:
     name: Bulk ingest
     parent: Write data
 products: [cloud]
 ---
 
 To upload a large amount of previously existing *historical* data into InfluxDB Cloud, contact Support for assistance.
-We’ll review your ingest rate limits, volume, and existing [data schema](/v2.0/reference/key-concepts/data-schema) to ensure the most efficient migration.
+We’ll review your ingest rate limits, volume, and existing [data schema](/influxdb/v2.0/reference/key-concepts/data-schema) to ensure the most efficient migration.
 
 Given our usage-based pricing and because the API is optimized for batched writing, we do not recommend using the API to ingest bulk data.
diff --git a/content/telegraf/v1.15/introduction/installation.md b/content/telegraf/v1.15/introduction/installation.md
index 31bb47c91..ae5b2b294 100644
--- a/content/telegraf/v1.15/introduction/installation.md
+++ b/content/telegraf/v1.15/introduction/installation.md
@@ -371,7 +371,7 @@ by placing a `#` in front of `[[outputs.influxdb]]`.
 Then remove the `#` in front of `[[outputs.influxdb_v2]]`.
 
 For detailed instructions on configuring Telegraf to write to InfluxDB 2.0, see
-[Enable and configure the InfluxDB v2 output plugin](/v2.0/write-data/use-telegraf/manual-config/#enable-and-configure-the-influxdb-v2-output-plugin).
+[Enable and configure the InfluxDB v2 output plugin](/{{< latest "influxdb" "v2" >}}/write-data/use-telegraf/manual-config/#enable-and-configure-the-influxdb-v2-output-plugin).
 
 ### Start the agent