[APT-1692] Strip /docs/ prefix from all site URLs

_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/deploy-landing-zone-solution/apply-account-baseline-root-to-root-account.md

@@ -58,9 +58,9 @@ We’ll be using the `landingzone/account-baseline-root` module from [terraform-
 :::info
 
 This guide will use [Terragrunt](https://github.com/gruntwork-io/terragrunt) and its associated file and folder
-structure to deploy Terraform modules. Please note that **Terragrunt is NOT required for using Terraform modules from the Gruntwork Infrastructure as Code Library.** Check out our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork) section
+structure to deploy Terraform modules. Please note that **Terragrunt is NOT required for using Terraform modules from the Gruntwork Infrastructure as Code Library.** Check out our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork) section
 for instructions on alternative options, such as how to
-[deploying how to use plain terraform](/docs/intro/first-deployment/deploy#deploy-using-plain-terraform).
+[deploying how to use plain terraform](/intro/first-deployment/deploy#deploy-using-plain-terraform).
 
 :::
 

_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites.md

@@ -13,7 +13,7 @@ This walkthrough has the following pre-requisites:
 
 This guide uses code from the [Gruntwork Infrastructure as Code Library](https://gruntwork.io/infrastructure-as-code-library/), as it
 implements most of the production-grade design for you out of the box. Make sure to read
-our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork).
+our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork).
 
 ## Gruntwork Compliance for CIS AWS Foundations Benchmark
 
@@ -37,7 +37,7 @@ This guide uses [Terraform](https://www.terraform.io/) to define and manage all
 you’re not familiar with Terraform, check out
 [A Comprehensive Guide to Terraform](https://blog.gruntwork.io/a-comprehensive-guide-to-terraform-b3d32832baca),
 [A Crash Course on Terraform](https://training.gruntwork.io/p/terraform), and
-our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork).
+our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork).
 
 ## Terragrunt
 

_docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/the-gruntwork-solution.md

@@ -55,4 +55,4 @@ You can use this approach on each AWS account. In many cases, you’ll only need
 same methodology can be applied to pre-production accounts as well.
 
 If you need to brush up on how the IaC Library works, read the
-our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork) section.
+our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork) section.

_docs-sources/guides/build-it-yourself/achieve-compliance/index.md

@@ -11,7 +11,7 @@ import { CardList } from "/src/components/CardGroup"
 
 This guide was last updated on 6th September 2021, and it covers CIS 1.4.0 Benchmark recommendations. We aim to keep
 it up to date with our infrastructure-as-code modules with the latest CIS Benchmark that has been released.
-If you need to access older versions, please [get in touch](/docs/guides/support) with us.
+If you need to access older versions, please [get in touch](/guides/support) with us.
 
 :::
 
@@ -24,8 +24,8 @@ compliant state over time because all of the infrastructure is defined as code.
 
 Previously, we supported versions 1.3.0 and 1.2.0 of the Benchmark. If you are looking to upgrade from an older version please follow these in order:
 
-- To upgrade from v1.2.0 to v1.3.0, please follow [this upgrade guide](/docs/guides/stay-up-to-date/cis/cis-1.3.0).
-- To upgrade from v1.3.0 to v1.4.0, please follow [this upgrade guide](/docs/guides/stay-up-to-date/cis/cis-1.4.0).
+- To upgrade from v1.2.0 to v1.3.0, please follow [this upgrade guide](/guides/stay-up-to-date/cis/cis-1.3.0).
+- To upgrade from v1.3.0 to v1.4.0, please follow [this upgrade guide](/guides/stay-up-to-date/cis/cis-1.4.0).
 
 ![CIS Benchmark Architecture](/img/guides/build-it-yourself/achieve-compliance/cis-account-architecture.png)
 
@@ -36,31 +36,31 @@ Feel free to read this guide from start to finish or skip around to whatever sec
 <CardList>
   <Card
     title="Core Concepts"
-    href="/docs/guides/build-it-yourself/achieve-compliance/core-concepts/intro"
+    href="/guides/build-it-yourself/achieve-compliance/core-concepts/intro"
   >
     An overview of the AWS Foundations Benchmark, including its control sections and structure.
   </Card>
   <Card
     title="Production-grade Design"
-    href="/docs/guides/build-it-yourself/achieve-compliance/production-grade-design/intro"
+    href="/guides/build-it-yourself/achieve-compliance/production-grade-design/intro"
   >
     How to use infrastructure as code to achieve compliance with minimal redundancy and maximum flexibility.
   </Card>
   <Card
     title="Deployment Walkthrough"
-    href="/docs/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites"
+    href="/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/pre-requisites"
   >
     A step-by-step guide to achieving compliance using the Gruntwork Infrastructure as Code Library and the Gruntwork CIS AWS Foundations Benchmark wrapper modules.
   </Card>
   <Card
     title="Next Steps"
-    href="/docs/guides/build-it-yourself/achieve-compliance/next-steps"
+    href="/guides/build-it-yourself/achieve-compliance/next-steps"
   >
     How to measure and maintain compliance.
   </Card>
   <Card
     title="Traceability Matrix"
-    href="/docs/guides/build-it-yourself/achieve-compliance/traceability-matrix"
+    href="/guides/build-it-yourself/achieve-compliance/traceability-matrix"
   >
     A reference table that maps each Benchmark recommendation to the corresponding section in the deployment
 walkthrough.

_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/intro.md

@@ -6,7 +6,7 @@ pagination_label: Production-grade Design
 
 In [core concepts](../core-concepts/intro.md) we discussed the basics of the AWS Foundations Benchmark. Although it's possible to achieve
 compliance with the Benchmark by manually configuring each setting in the web console or entering the CLI commands, we
-strongly discourage this approach. It precludes [the myriad benefits of using code to manage infrastructure](/docs/intro/core-concepts/infrastructure-as-code).
+strongly discourage this approach. It precludes [the myriad benefits of using code to manage infrastructure](/intro/core-concepts/infrastructure-as-code).
 
 Instead, we advise using [Terraform](https://www.terraform.io) (or similar tools, such as
 [CloudFormation](https://aws.amazon.com/cloudformation/) or [Pulumi](https://www.pulumi.com/) to configure cloud

_docs-sources/guides/build-it-yourself/achieve-compliance/production-grade-design/storage.md

@@ -65,7 +65,7 @@ The CIS 1.4.0 Benchmark recommends a few additional steps to ensure your data is
 
 :::info
 
-The steps below are not the full list of actions needed to configure MFA Delete or Amazon Macie for your account. To follow the steps necessary to configure it according to the CIS 1.4.0 Benchmark, please follow the MFA Delete and Macie section in the [the migration guide to CIS 1.4.0](/docs/guides/stay-up-to-date/cis/cis-1.4.0), or the deployment guide section in this guide.
+The steps below are not the full list of actions needed to configure MFA Delete or Amazon Macie for your account. To follow the steps necessary to configure it according to the CIS 1.4.0 Benchmark, please follow the MFA Delete and Macie section in the [the migration guide to CIS 1.4.0](/guides/stay-up-to-date/cis/cis-1.4.0), or the deployment guide section in this guide.
 :::
 
 ### Enable MFA Delete (recommendation 2.1.3)

_docs-sources/guides/build-it-yourself/index.md

@@ -3,39 +3,39 @@ import Grid from "/src/components/Grid"
 
 # Build Your Own Architecture
 
-The Gruntwork IaC library empowers you to construct your own bespoke architecture in record time. By mix-and-matching our modules and services you can quickly define a custom architecture to suit your needs, all with the confidence of having world-class, battle-tested code running under the hood. This series of guides aims to teach you how to configure and deploy some of our most popular services. Additional guides will be added over time, but the principles covered extend to the rest of the IaC library. If you have trouble, don’t hesitate to ask questions via our [support channels](/docs/guides/support).
+The Gruntwork IaC library empowers you to construct your own bespoke architecture in record time. By mix-and-matching our modules and services you can quickly define a custom architecture to suit your needs, all with the confidence of having world-class, battle-tested code running under the hood. This series of guides aims to teach you how to configure and deploy some of our most popular services. Additional guides will be added over time, but the principles covered extend to the rest of the IaC library. If you have trouble, don’t hesitate to ask questions via our [support channels](/guides/support).
 
 ## Follow Our Deployment Guides
 
 <Grid cols={2}>
   <Card
     title="Set Up Your AWS Accounts"
-    href="/docs/guides/build-it-yourself/landing-zone"
+    href="/guides/build-it-yourself/landing-zone"
   >
     Set up a multi-account structure using Gruntwork Landing Zone.
   </Card>
   <Card
     title="Configure a CI/CD Pipeline"
-    href="/docs/guides/build-it-yourself/pipelines"
+    href="/guides/build-it-yourself/pipelines"
   >
     Implement continuous deployment for your infrastructure code with Gruntwork
     Pipelines.
   </Card>
   <Card
     title="Deploy a VPC"
-    href="/docs/guides/build-it-yourself/vpc"
+    href="/guides/build-it-yourself/vpc"
   >
     Set up your network according to industry best practices using our VPC service.
   </Card>
   <Card
     title="Deploy a Kubernetes Cluster"
-    href="/docs/guides/build-it-yourself/kubernetes-cluster"
+    href="/guides/build-it-yourself/kubernetes-cluster"
   >
     Deploy a Kubernetes Cluster to host all of your apps and services.
   </Card>
   <Card
     title="Acheive Compliance"
-    href="/docs/guides/build-it-yourself/achieve-compliance"
+    href="/guides/build-it-yourself/achieve-compliance"
   >
     Make your infrastructure compliant with the CIS AWS Foundations Benchmark.
   </Card>
@@ -44,7 +44,7 @@ The Gruntwork IaC library empowers you to construct your own bespoke architectur
 ## Dig Into the Code
 
 <Grid cols={2}>
-  <Card title="Browse Services" href="/docs/reference/services/intro">
+  <Card title="Browse Services" href="/reference/services/intro">
     View the API reference for our entire service catalog to learn what’s
     available.
   </Card>

_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/deploy-the-vpc.md

@@ -1,7 +1,7 @@
 # Deploy the VPC
 
 The first step is to deploy a VPC. Follow the instructions in
-[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) to use
+[How to deploy a production-grade VPC on AWS](/guides/build-it-yourself/vpc/) to use
 `module-vpc` to create a VPC setup that looks like this:
 
 ![A production-grade VPC setup deployed using module-vpc from the Gruntwork Infrastructure as Code Library](/img/guides/build-it-yourself/vpc/vpc-diagram.png)
@@ -107,9 +107,9 @@ module "dns_mgmt_to_app" {
 ```
 
 At this point, you’ll want to test your code. See
-[Manual tests for Terraform code](/docs/intro/first-deployment/testing#manual-tests-for-terraform-code)
+[Manual tests for Terraform code](/intro/first-deployment/testing#manual-tests-for-terraform-code)
 and
-[Automated tests for Terraform code](/docs/intro/first-deployment/testing#automated-tests-for-terraform-code)
+[Automated tests for Terraform code](/intro/first-deployment/testing#automated-tests-for-terraform-code)
 for instructions.
 
 Once your updated `vpc-app` wrapper module is working the way you want, submit a pull request, get your changes merged
@@ -126,9 +126,9 @@ git push --follow-tags
 This guide will use [Terragrunt](https://github.com/gruntwork-io/terragrunt) and its associated file and folder
 structure to deploy Terraform modules. Please note that **Terragrunt is NOT required for using Terraform modules from
 the Gruntwork Infrastructure as Code Library.** Check out
-our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork) for instructions
+our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork) for instructions
 on alternative options, such as how to
-[Deploy using plain Terraform](/docs/intro/first-deployment/deploy#deploy-using-plain-terraform).
+[Deploy using plain Terraform](/intro/first-deployment/deploy#deploy-using-plain-terraform).
 
 :::
 

_docs-sources/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites.md

@@ -14,7 +14,7 @@ This walkthrough has the following pre-requisites:
 
 This guide uses code from the [Gruntwork Infrastructure as Code Library](https://gruntwork.io/infrastructure-as-code-library/), as it
 implements most of the production-grade design for you out of the box. Make sure to read
-our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork).
+our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork).
 
 </div>
 
@@ -31,7 +31,7 @@ You must be a <span className="js-subscribe-cta">Gruntwork subscriber</span> to
 This guide uses [Terraform](https://www.terraform.io/) to define and manage all the infrastructure as code. If you’re
 not familiar with Terraform, check out [A
 Comprehensive Guide to Terraform](https://blog.gruntwork.io/a-comprehensive-guide-to-terraform-b3d32832baca), [A Crash Course on Terraform](https://training.gruntwork.io/p/terraform), and
-our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork).
+our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork).
 
 #### Python and Kubergrunt
 
@@ -44,12 +44,12 @@ Python and `kubergrunt` installed on any computer where you will be running Terr
 This guide assumes you are deploying a Kubernetes cluster for use with [Docker](https://www.docker.com). The guide also
 uses [Packer](https://www.packer.io) to build VM images. If you’re not familiar with Docker or Packer, check out
 [A Crash Course on Docker and Packer](https://training.gruntwork.io/p/a-crash-course-on-docker-packer) and
-our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork).
+our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork).
 
 #### AWS accounts
 
 This guide deploys infrastructure into one or more AWS accounts. Check out the
-[How to configure a production-grade AWS account structure](/docs/guides/build-it-yourself/landing-zone/)
+[How to configure a production-grade AWS account structure](/guides/build-it-yourself/landing-zone/)
 guide for instructions. You will also need to be able to authenticate to these accounts on the CLI: check out
 [A Comprehensive Guide to Authenticating to AWS on the Command Line](https://blog.gruntwork.io/a-comprehensive-guide-to-authenticating-to-aws-on-the-command-line-63656a686799)
 for instructions.

_docs-sources/guides/build-it-yourself/kubernetes-cluster/index.md

@@ -20,29 +20,29 @@ This guide will walk you through the process of configuring a production-grade K
 <CardList>
   <Card
     title="Core Concepts"
-    href="/docs/guides/build-it-yourself/kubernetes-cluster/core-concepts/why-kubernetes"
+    href="/guides/build-it-yourself/kubernetes-cluster/core-concepts/why-kubernetes"
   >
     An overview of the core concepts you need to understand to use Kubernetes, including why you may want to use
     ubernetes, Kubernetes architecture, the control plane, worker nodes, different ways to run Kubernetes, services,
     deployments, auto scaling, auto healing, RBAC, and more.
   </Card>
   <Card
     title="Production-grade Design"
-    href="/docs/guides/build-it-yourself/kubernetes-cluster/production-grade-design/intro"
+    href="/guides/build-it-yourself/kubernetes-cluster/production-grade-design/intro"
   >
     An overview of how to configure a secure, scalable, highly available Kubernetes cluster that you can rely on in
     production.
   </Card>
   <Card
     title="Deployment Walkthrough"
-    href="/docs/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites"
+    href="/guides/build-it-yourself/kubernetes-cluster/deployment-walkthrough/pre-requisites"
   >
     A step-by-step guide to deploying a production-grade Kubernetes cluster in AWS using code from the Gruntwork
     Infrastructure as Code Library.
   </Card>
   <Card
     title="Next Steps"
-    href="/docs/guides/build-it-yourself/kubernetes-cluster/next-steps"
+    href="/guides/build-it-yourself/kubernetes-cluster/next-steps"
   >
     What to do once you’ve got your Kubernetes cluster deployed.
   </Card>

_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/control-plane.md

@@ -19,7 +19,7 @@ minor version.
 
 Your EKS cluster will run in the subnets you specify. We strongly recommend running solely in private subnets that
 are NOT directly accessible from the public Internet. See
-[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more
+[How to deploy a production-grade VPC on AWS](/guides/build-it-yourself/vpc/) for more
 info.
 
 #### Endpoint access
@@ -28,7 +28,7 @@ You can configure whether the [API endpoint for your EKS cluster](https://docs.a
 is accessible from (a) within the same VPC and/or (b) from the public Internet. We recommend allowing access from
 within the VPC, but not from the public Internet. If you need to talk to your Kubernetes cluster from your own
 computer (e.g., to issue commands via `kubectl`), use a bastion host or VPN server. See
-[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more
+[How to deploy a production-grade VPC on AWS](/guides/build-it-yourself/vpc/) for more
 info.
 
 #### Cluster IAM Role

_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/vpc-configuration.md

@@ -2,7 +2,7 @@
 
 EKS relies on a _[Virtual Private Cloud (VPC)](https://aws.amazon.com/vpc/)_ to provide the basic network topology and
 to manage communication across the nodes (see
-[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more
+[How to deploy a production-grade VPC on AWS](/guides/build-it-yourself/vpc/) for more
 information on VPCs). Here are the key VPC considerations for your EKS cluster:
 
 <div className="dlist">

_docs-sources/guides/build-it-yourself/kubernetes-cluster/production-grade-design/worker-nodes.md

@@ -20,7 +20,7 @@ value `owned`.
 
 We strongly recommend running the Auto Scaling Group for your worker nodes in private subnets that are NOT directly
 accessible from the public Internet. See
-[How to deploy a production-grade VPC on AWS](/docs/guides/build-it-yourself/vpc/) for more
+[How to deploy a production-grade VPC on AWS](/guides/build-it-yourself/vpc/) for more
 info.
 
 #### AMI

_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/pre-requisites.md

@@ -14,7 +14,7 @@ This walkthrough has the following pre-requisites:
 
 This guide uses code from the [Gruntwork Infrastructure as Code Library](https://gruntwork.io/infrastructure-as-code-library/), as it
 implements most of the production-grade design for you out of the box. Make sure to read
-our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork).
+our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork).
 
 </div>
 
@@ -31,7 +31,7 @@ You must be a <span className="js-subscribe-cta">Gruntwork subscriber</span> to
 This guide uses [Terraform](https://www.terraform.io/) to define and manage all the infrastructure as code. If you’re
 not familiar with Terraform, check out [A
 Comprehensive Guide to Terraform](https://blog.gruntwork.io/a-comprehensive-guide-to-terraform-b3d32832baca), [A Crash Course on Terraform](https://training.gruntwork.io/p/terraform), and
-our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork).
+our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork).
 
 #### Terragrunt
 

_docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md

@@ -4,9 +4,9 @@
 
 This guide uses [Terragrunt](https://github.com/gruntwork-io/terragrunt) and its associated file and folder
 structure to deploy Terraform modules. Please note that **Terragrunt is NOT required for using Terraform modules from
-the Gruntwork Infrastructure as Code Library.** Check out our [Introduction to Gruntwork](/docs/intro/overview/intro-to-gruntwork)
+the Gruntwork Infrastructure as Code Library.** Check out our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork)
 for instructions on alternative options, such as
-[deploying with plain Terraform](/docs/intro/first-deployment/deploy#deploy-using-plain-terraform).
+[deploying with plain Terraform](/intro/first-deployment/deploy#deploy-using-plain-terraform).
 
 :::