Docusaurus v3 (#1884)

* mdxv3 compatibility

* chore: update versions of things

* chore: fix the caption plugin for v3

* chore: checkin the new caption file

* bump from 3.0.0 to 3.5.2

* fix: card imports

* chore: fix the root

* chore: fix broken links

* chore: revert accident to stay up to date

* chore: hash updates

* chore: regenerate discussions

Author: ZachGoldberg

Diff for: _docs-sources/foundations/landing-zone/index.md

@@ -33,7 +33,7 @@ Gruntwork Landing Zone directly addresses these limitations by extending Control
 1. Request new AWS accounts using a simple YAML file, GitHub Actions, or any system that can trigger a GitHub Action (e.g. ServiceNow)
 1. Review and customize all new AWS account requests using GitHub Pull Request functionality
 1. Define a customized account baseline unique to your organization
-1. Enable AWS account baselines to stay up to date automatically using [Patcher](./patcher)
+1. Enable AWS account baselines to stay up to date automatically using [Patcher](/patcher)
 
 ## Greenfield vs. brownfield
 

Diff for: _docs-sources/guides/build-it-yourself/achieve-compliance/deployment-walkthrough/create-the-root-account.md

@@ -2,7 +2,7 @@
 
 The first step is to create your root account. This account will be the parent of all of your other AWS accounts and the central place where you manage billing. You create this initial account manually, via a web browser:
 
-- Go to <https://aws.amazon.com>.
+- Go to [https://aws.amazon.com](https://aws.amazon.com).
 - Click Create an AWS Account.
 - Go through the sign up flow, entering contact and billing details as requested.
 - You will be asked to enter an email address and password to use as the credentials for the root user of this root account.

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

@@ -4,6 +4,7 @@ pagination_label: Achieve Compliance with the CIS AWS Foundations Benchmark
 ---
 
 import { CardList } from "/src/components/CardGroup"
+import { Card } from "/src/components/Card"
 
 # Achieve Compliance with the CIS AWS Foundations Benchmark
 

Diff for: _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/aws-account.md

@@ -1,11 +1,7 @@
 # AWS account
 
-To use AWS, you must create an AWS account. You do this by signing up at <https://aws.amazon.com>. Once you’ve created
+To use AWS, you must create an AWS account. You do this by signing up at [https://aws.amazon.com](https://aws.amazon.com). Once you’ve created
 an account, it will get a unique, 12-digit
 _[AWS account ID](https://docs.aws.amazon.com/IAM/latest/UserGuide/console_account-alias.html)_ (note: the account ID is
 not in and of itself a secret, so it’s OK to share it with trusted 3rd parties, but you might not want to go so far as
 to share it publicly on the Internet), and you will be logged into your new AWS account as the root user.
-
-
-
-

Diff for: _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/iam-users.md

@@ -22,7 +22,7 @@ IAM user to your AWS account in a web browser by using the IAM user sign-in URL.
 
 Every AWS account has a unique
 _[IAM user sign-in URL](https://docs.aws.amazon.com/IAM/latest/UserGuide/getting-started_how-users-sign-in.html)_. Note
-that to login as an IAM user, you do NOT go to <https://console.aws.amazon.com>, as that’s solely the sign-in URL for
+that to login as an IAM user, you do NOT go to [https://console.aws.amazon.com](https://console.aws.amazon.com), as that’s solely the sign-in URL for
 root users. Instead, IAM users will need to use a sign-in URL of the form
 `\https://<ID_OR_ALIAS>.signin.aws.amazon.com/console`, where `ID_OR_ALIAS` is either your AWS account ID (e.g.,
 `\https://111122223333.signin.aws.amazon.com/console`) or a
@@ -63,7 +63,3 @@ user permissions, you will need to use IAM policies, which are the topic of the
 
 
 </div>
-
-
-
-

Diff for: _docs-sources/guides/build-it-yourself/landing-zone/core-concepts/root-user.md

@@ -20,7 +20,7 @@ you can use to login to the AWS console.
 #### Logging into the AWS console
 
 After the initial sign up, if you wish to login as the root user, you have to go to
-<https://console.aws.amazon.com> and login using the root user’s email address and password.
+[https://console.aws.amazon.com](https://console.aws.amazon.com) and login using the root user’s email address and password.
 
 #### Access keys
 
@@ -53,7 +53,3 @@ more limited permissions, and then you’ll likely never touch the root user acc
 
 
 </div>
-
-
-
-

Diff for: _docs-sources/guides/build-it-yourself/landing-zone/deployment-walkthrough/create-the-root-account.md

@@ -3,7 +3,7 @@
 Now let’s create your root AWS account. This account will be the parent of all of your other AWS accounts and
 the central place where you manage billing. You create this initial account manually, via a web browser:
 
-1. Go to <https://aws.amazon.com>.
+1. Go to [https://aws.amazon.com](https://aws.amazon.com).
 
 2. Click Create an AWS Account.
 

Diff for: _docs-sources/guides/build-it-yourself/vpc/production-grade-design/defense-in-depth.md

@@ -4,7 +4,7 @@
 
 People make mistakes all the time: forgetting to remove accounts, keeping ports open, including test credentials in
 production code, etc. Rather than living in an idealized model where you assume people won’t make mistakes, you can
-employ a [Defense in Depth](<https://en.wikipedia.org/wiki/Defense_in_depth_(computing)>) strategy of setting up multiple
+employ a [Defense in Depth](https://en.wikipedia.org/wiki/Defense_in_depth_(computing)) strategy of setting up multiple
 layers of protection so that a failure in any single layer doesn’t immediately lead to disaster. You never want to be
 one typo away from a security incident.
 

Diff for: _docs-sources/guides/stay-up-to-date/cis/cis-1.5.0/deployment-walkthrough/step-4-verify-the-code-changes.md

@@ -29,14 +29,14 @@ The output of the diff will contain messages similar to these:
     Terraform will perform the following actions:
 
     # module.rds.module.rds_alarms.aws_cloudwatch_metric_alarm.rds_disk_space_available[0] will be updated in-place
-    ~ resource "aws_cloudwatch_metric_alarm" "rds_disk_space_available" {
+    ~ resource "aws_cloudwatch_metric_alarm" "rds_disk_space_available" \{
         ...
-        }
+        \}
 
     # module.rds.module.rds_alarms.aws_cloudwatch_metric_alarm.rds_high_cpu_utilization[0] will be updated in-place
-    ~ resource "aws_cloudwatch_metric_alarm" "rds_high_cpu_utilization" {
+    ~ resource "aws_cloudwatch_metric_alarm" "rds_high_cpu_utilization" \{
         ...
-        }
+        \}
 
     ...
 
@@ -58,27 +58,27 @@ The output `plan` will contain messages similar to these:
 
     # module.database.aws_db_instance.primary[0] will be destroyed
     # (because aws_db_instance.primary is not in configuration)
-    - resource "aws_db_instance" "primary" {
+    - resource "aws_db_instance" "primary" \{
         ...
-        }
+        \}
 
     # module.database.aws_db_subnet_group.db[0] will be destroyed
     # (because aws_db_subnet_group.db is not in configuration)
-    - resource "aws_db_subnet_group" "db" {
+    - resource "aws_db_subnet_group" "db" \{
         ...
-        }
+        \}
 
     ...
 
     # module.rds.module.database.aws_db_instance.primary[0] will be created
-    + resource "aws_db_instance" "primary" {
+    + resource "aws_db_instance" "primary" \{
         ...
-        }
+        \}
 
     # module.rds.module.database.aws_db_subnet_group.db[0] will be created
-    + resource "aws_db_subnet_group" "db" {
+    + resource "aws_db_subnet_group" "db" \{
         ...
-        }
+        \}
 
     ...
 

Diff for: _docs-sources/guides/stay-up-to-date/terraform/how-to-dry-your-reference-architecture/deployment-walkthrough/refactoring-common-configurations-for-a-component.md

@@ -4,10 +4,13 @@ The rest of this guide will cover how to identify and extract the common configu
 in your Reference Architecture. These steps can be used to refactor any component that is deployed in multiple
 accounts or environments in your Reference Architecture.
 
-- [Step 1: Identify the component](#step-identify-the-component)
-- [Step 2: Identify common configurations](#step-identify-common-configurations)
-- [Step 3: Extract common configurations](#step-extract-common-configurations)
-- [Step 4: Update child configurations](#step-1-update-child-configurations)
+- [Refactoring common configurations for a component](#refactoring-common-configurations-for-a-component)
+  - [Step 1: Identify the component](#step-1-identify-the-component)
+  - [Step 2: Identify common configurations](#step-2-identify-common-configurations)
+    - [Using `diff` to identify raw differences](#using-diff-to-identify-raw-differences)
+    - [Using JSON rendering to identify semantic differences](#using-json-rendering-to-identify-semantic-differences)
+  - [Step 3: Extract common configurations](#step-3-extract-common-configurations)
+  - [Step 4: Update child configurations](#step-4-update-child-configurations)
 
 ## Step 1: Identify the component
 
@@ -89,9 +92,13 @@ identified as different across environments.
 There are a couple ways to go about this depending on how complex the underlying configuration files are, and how much
 customization has been made since the deployment of the Reference Architecture.
 
-- [Using `diff` to identify raw differences](#using-diff-to-identify-raw-differences)
-
-- [Using JSON rendering to identify semantic differences](#using-json-rendering-to-identify-semantic-differences)
+- [Refactoring common configurations for a component](#refactoring-common-configurations-for-a-component)
+  - [Step 1: Identify the component](#step-1-identify-the-component)
+  - [Step 2: Identify common configurations](#step-2-identify-common-configurations)
+    - [Using `diff` to identify raw differences](#using-diff-to-identify-raw-differences)
+    - [Using JSON rendering to identify semantic differences](#using-json-rendering-to-identify-semantic-differences)
+  - [Step 3: Extract common configurations](#step-3-extract-common-configurations)
+  - [Step 4: Update child configurations](#step-4-update-child-configurations)
 
 ### Using `diff` to identify raw differences
 
@@ -148,7 +155,7 @@ first diff represents a difference in the `Title` attribute of the movie object
     - "Peter Sellers"
     + "Mike Myers"
     @ ["Movies",102]
-    + {"Title":"Austin Powers","Actors":{"Austin Powers":"Mike Myers"}}
+    + \{"Title":"Austin Powers","Actors":\{"Austin Powers":"Mike Myers"\}\}
 
 Like with `diff`, cross off any blocks, attributes, and input keys from the initial list that are different based
 on the output, except for `locals`. In the `jd` output, this would be the first element in each `@` entry, or the second

Diff for: _docs-sources/guides/stay-up-to-date/terraform/terraform-12/deployment-walkthrough.md

@@ -1,6 +1,6 @@
 # Deployment Walkthrough
 
-The following sections outline the steps you need to take in order to migrate from Terraform <= 0.11.X and Terragrunt <=
+The following sections outline the steps you need to take in order to migrate from Terraform &lt;= 0.11.X and Terragrunt &lt;=
 v0.18.x to Terraform 0.12.x and newer and Terragrunt 0.19.x and newer:
 
 1. [Upgrade modules for compatibility with Terraform 0.12.x](#upgrade-modules-for-compatibility-with-terraform-012x)
@@ -139,7 +139,7 @@ it is very easy to "start over", such as a sandbox or dev environment!**
    - Duplicated comment blocks. Sometimes, the upgrade tool will duplicate comment blocks in the middle of the code.
      This was most common when there is a comment on a resource attribute.
    - Reorganized comment blocks. The tool sometimes moves the comment block somewhere you don't expect. This is
-     especially problematic for comments within blocks (e.g., in the middle of a vars = { … }) block.
+     especially problematic for comments within blocks (e.g., in the middle of a vars = \{ … \}) block.
    - `bool` no longer converts to `1` and `0` automatically. If you had the pattern of doing `count = bool`, this no
      longer works. You have to explicitly add a conditional: `count = bool ? 1 : 0`.
    - In tf11 and under, sometimes you had to do `attr = ["${list}"]` when passing in a `list` to an attribute. In tf12,
@@ -202,8 +202,8 @@ instead of the equivalent one for Terraform.
 #### <a id="using-mise-to-manage-multiple-terragrunt-versions"></a>Using mise to manage multiple terragrunt versions
 
 As with Homebrew, you can also use `mise` to manage multiple `terragrunt` versions, using the same method described above in
-[Using mise to manage multiple terraform versions](#using-mise-to-manage-multiple-terraform-versions). To use 
-the method for Terragrunt, replace the references for `terraform` with `terragrunt`. 
+[Using mise to manage multiple terraform versions](#using-mise-to-manage-multiple-terraform-versions). To use
+the method for Terragrunt, replace the references for `terraform` with `terragrunt`.
 
 For example, to install and use `terragrunt` version `0.18.7`, you would run:
 ```