[CORE-979] Cleanup old content (#866)

* Remove API reference pages

* Remove working with code pages

* Remove intro guide pages

* Remove core-concepts, environment-setup, first-deployment and tool-fundamentals pages

* Remove old reference architecture guide

* Fix link references

* Regenerate stay up to date guides and fix broken links

* Hide old guides

* Add back sidebar for compliance guide

* move production framework to footer

* Add production framework sidebar back

* fix issues after updating from master

* fix image link

* revert change to stay up to date

* fix broken link

* re-run docs-sourcer with new changes

---------

Co-authored-by: Maxwell Moon <[email protected]>

Author: oredavids

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

@@ -60,7 +60,7 @@ We’ll be using the `landingzone/account-baseline-root` module from [terraform-
 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](/intro/overview/intro-to-gruntwork) section
 for instructions on alternative options, such as how to
-[deploying how to use plain terraform](/intro/first-deployment/deploy#deploy-using-plain-terraform).
+[deploying how to use plain terraform](/library/getting-started/deploying-a-module).
 
 :::
 

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

@@ -2,7 +2,178 @@
 sidebar_label: Prepare your infrastructure-live repository
 ---
 
-# Prepare your `infrastructure-live` repository
+# Prepare your infrastructure-live repository
 
-We’ve previously described exactly how to prepare your repository in the
-[Gruntwork Landing Zone guide](../../landing-zone/deployment-walkthrough/prepare-your-infrastructure-live-repository.md). Follow the steps in that section to get your `infrastructure-live` repository set up for the next steps.
+:::info Terragrunt not required
+
+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](/intro/overview/intro-to-gruntwork)
+for instructions on alternative options, such as
+[deploying with plain Terraform](/library/getting-started/deploying-a-module).
+
+:::
+
+Now we’re going to make some HCL files that store variables to be used across your modules. _You won’t be able to fill
+everything out just yet._ Your AWS account IDs will be generated after applying the `account-baseline-root` to the root
+account. At that point you can update these files. Create them now to have them ready to use.
+
+For example, assuming `us-east-1` is your default region, your directory structure would look like the following, with
+`_global` and `<region>` directories in each account directory:
+
+```bash
+infrastructure-live
+  └ common.hcl
+  └ accounts.json
+  └ terragrunt.hcl
+  └ dev
+  └ logs
+  └ stage
+  └ security
+  └ shared
+  └ prod
+    └ _global
+      └ region.hcl
+    └ us-east-1
+      └ region.hcl
+```
+
+The Terraform modules in the [Service Catalog](https://github.com/gruntwork-io/terraform-aws-service-catalog/)
+do not define some blocks that are required for Terraform to operate (e.g., the `provider` and `terraform`
+state backend blocks). This is to allow the modules to be flexibly used in different contexts.
+We’ll define a root `terragrunt.hcl` that injects these these required blocks.
+
+Create a `terragrunt.hcl` at the root of your infrastructure-live repo and insert the following contents. As you can
+see, it references `common`, `account`, and `region` HCL files which we’ll create shortly.
+
+```hcl title=infrastructure-live/terragrunt.hcl
+# -----------------------------------------------------------------------------
+# TERRAGRUNT CONFIGURATION
+# -----------------------------------------------------------------------------
+
+locals {
+  common_vars  = read_terragrunt_config("${get_terragrunt_dir()}/common.hcl")
+  account_vars = read_terragrunt_config(find_in_parent_folders("account.hcl"))
+  region_vars  = read_terragrunt_config(find_in_parent_folders("region.hcl"))
+
+  name_prefix    = local.common_vars.locals.name_prefix
+  account_name   = local.account_vars.locals.account_name
+  account_id     = local.account_vars.locals.account_id
+  default_region = local.common_vars.locals.default_region
+  aws_region     = local.region_vars["aws_region"]
+}
+
+# -----------------------------------------------------------------------------
+# GENERATED PROVIDER BLOCK
+# -----------------------------------------------------------------------------
+
+generate "provider" {
+  path      = "provider.tf"
+  if_exists = "overwrite_terragrunt"
+  contents  = <<EOF
+provider "aws" {
+  region = "${local.aws_region}"
+  version = ">= 3.13.0"
+  # Only these AWS Account IDs may be operated on by this template
+  allowed_account_ids = ["${local.account_id}"]
+}
+EOF
+}
+
+# -----------------------------------------------------------------------------
+# GENERATED REMOTE STATE BLOCK
+# -----------------------------------------------------------------------------
+
+remote_state {
+  backend = "s3"
+  generate = {
+    path      = "backend.tf"
+    if_exists = "overwrite_terragrunt"
+  }
+  config = {
+    encrypt        = true
+    bucket         = "${local.name_prefix}-${local.account_name}-${local.aws_region}-terraform-state"
+    key            = "${path_relative_to_include()}/terraform.tfstate"
+    region         = local.default_region
+    dynamodb_table = "terraform-locks"
+  }
+}
+
+# -----------------------------------------------------------------------------
+# GLOBAL PARAMETERS
+# -----------------------------------------------------------------------------
+
+inputs = {
+  # Set commonly used inputs globally to keep child terragrunt.hcl files DRY
+  aws_account_id = local.account_id
+  aws_region     = local.aws_region
+  name_prefix    = local.name_prefix
+}
+```
+
+Also create a `common.hcl` file at the root of your `infrastructure-live` repo, with the following contents.
+
+```hcl title=infrastructure-live/common.hcl
+locals {
+  # TODO: Enter a unique name prefix to set for all resources created in your accounts, e.g., your org name.
+  name_prefix = ""
+  # TODO: Enter the default AWS region, the same as where the terraform state S3 bucket is currently provisioned.
+  default_region = ""
+
+  # TODO: Fill these in after applying the account-baseline-root to the root account.
+  config_s3_bucket_name      = ""
+  cloudtrail_s3_bucket_name  = ""
+  cloudtrail_kms_key_arn     = ""
+
+  # TODO: An accounts map to conveniently store all account IDs.
+  # Centrally define all the AWS account IDs. We use JSON so that it can be readily parsed outside of Terraform.
+  accounts = jsondecode(file("accounts.json"))
+}
+```
+
+This file references an `accounts.json`, which you should also create at the root of the repo. _You will fill out
+the account IDs after applying the account-baseline-root to the root account._
+
+```json title=infrastructure-live/accounts.json
+{
+  "dev": "",
+  "logs": "",
+  "prod": "",
+  "security": "",
+  "shared": "",
+  "stage": ""
+}
+```
+
+In each account folder (e.g., `infrastructure-live/dev`, `infrastructure-live/shared`, etc.), add a file named
+`account.hcl` with the following contents. _Leave `account_id` blank until after the `account-baseline-root` has been
+applied to the root account._
+
+```hcl
+locals {
+  # TODO: Update with the actual information of each account
+  # The user friendly name of the AWS account. Usually matches the folder name.
+  account_name = ""
+  # The 12 digit ID number of your AWS account.
+  account_id = ""
+}
+```
+
+Now in each `infrastructure-live/<account_name>/_global/` folder, create a `region.hcl` file.
+
+```hcl
+# Modules in the account _global folder don't live in any specific AWS region, but you still have to send the API calls
+# to _some_ AWS region, so here we use the default region for those API calls.
+locals {
+  aws_region = read_terragrunt_config(find_in_parent_folders("common.hcl")).locals.default_region
+}
+```
+
+Do the same in each region folder (e.g., `infrastructure-live/dev/us-east-1/`). This `region.hcl` file is a bit different.
+
+```hcl
+locals {
+# TODO: Enter the region to use for all resources in this subfolder.
+  aws_region = ""
+}
+```

_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](/intro/core-concepts/infrastructure-as-code).
+strongly discourage this approach. It precludes [the myriad benefits of using code to manage infrastructure](/library/overview).
 
 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/index.md

@@ -107,10 +107,7 @@ module "dns_mgmt_to_app" {
 ```
 
 At this point, you’ll want to test your code. See
-[Manual tests for Terraform code](/intro/first-deployment/testing#manual-tests-for-terraform-code)
-and
-[Automated tests for Terraform code](/intro/first-deployment/testing#automated-tests-for-terraform-code)
-for instructions.
+[Manual tests for Terraform code](/library/usage/using-the-library#testing-terraform-only) for instructions.
 
 Once your updated `vpc-app` wrapper module is working the way you want, submit a pull request, get your changes merged
 into the `master` branch, and create a new versioned release by using a Git tag. For example, to create a `v0.5.0`
@@ -128,7 +125,7 @@ structure to deploy Terraform modules. Please note that **Terragrunt is NOT requ
 the Gruntwork Infrastructure as Code Library.** Check out
 our [Introduction to Gruntwork](/intro/overview/intro-to-gruntwork) for instructions
 on alternative options, such as how to
-[Deploy using plain Terraform](/intro/first-deployment/deploy#deploy-using-plain-terraform).
+[Deploy using plain Terraform](/library/getting-started/deploying-a-module).
 
 :::
 

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

@@ -6,7 +6,7 @@ This guide uses [Terragrunt](https://github.com/gruntwork-io/terragrunt) and its
 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)
 for instructions on alternative options, such as
-[deploying with plain Terraform](/intro/first-deployment/deploy#deploy-using-plain-terraform).
+[deploying with plain Terraform](/library/getting-started/deploying-a-module).
 
 :::