Fix Broken Links (#629)

* fix broken links

* fix broken links

* fix broken links

Author: osterman

docs/best-practices/developer/semver.mdx

@@ -34,4 +34,4 @@ As soon as our code reaches `1.X.Y`, the interface should be relatively stable -
 
 ## Implementation
 
-Managing semantic versions should be automated just like everything else in our infrastructure. The [`build-harness`](/reference/tools.mdx#build-harness) is used by our CI/CD process to automatically generate versions based on git history.
+Managing semantic versions should be automated just like everything else in our infrastructure. The [`build-harness`](/learn/toolchain/#build-harness) is used by our CI/CD process to automatically generate versions based on git history.

docs/best-practices/github/github-feature-branches.mdx

@@ -71,4 +71,4 @@ Now, go to town hacking away. When you're ready, push the changes up to the orig
 git push origin newfeature
 ```
 
-Now check out how to create [Pull Requests](/reference/best-practices/github-pull-requests.md)!
+Now check out how to create [Pull Requests](/best-practices/github/github-pull-requests)!

docs/best-practices/terraform.mdx

@@ -80,7 +80,7 @@ Optional functionality should be toggled in either of 2 ways:
    input variable, with an empty input disabling the option and non-empty
    input providing configuration. In this case, only use a separate feature
    flag if the list or map input may still cause problems due to relying on
-   computed problems during the plan phase. See [Count vs. For Each](/reference/terraform-in-depth/terraform-count-vs-for-each)
+   computed problems during the plan phase. See [Count vs. For Each](/learn/component-development/terraform-in-depth/terraform-count-vs-for-each)
    and [Terraform Errors When Planning](reference/terraform-in-depth/terraform-unknown-at-plan-time)
    for more information.
 3. It is never acceptable for an optional feature of the _module_ to be

docs/community/contribute/code-reviews.mdx

@@ -7,7 +7,7 @@ tags:
 ---
 import Steps from '@site/src/components/Steps';
 
-Here are some of our tips for conducting *Code Reviews* the SweetOps way. If you haven't already, become familiar with our [Best Practices](/category/best-practices/) and [Terraform Best Practices](/best-practices/terraform).
+Here are some of our tips for conducting *Code Reviews* the SweetOps way. If you haven't already, become familiar with our [Best Practices](/best-practices) and [Terraform Best Practices](/best-practices/terraform).
 
 <Steps>
   1. Use the ["Suggest"](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) feature as much as possible. This makes it quick and easy for the contributor to accept or dismiss the recommendations.

docs/community/contribute/our-github.mdx

@@ -16,7 +16,7 @@ From time to time, we might decide we can no longer maintain a repository. If th
 
 ## Getting Involved
 
-The best way to get involved is to checkout our "[getting started](intro.md)" guide.
+The best way to get involved is to checkout our "[getting started](/intro)" guide.
 
 Then join us in our Slack [`#community`](https://cloudposse.com/slack/) channel to get support or talk with others in the community.
 

docs/community/support.mdx

@@ -8,7 +8,7 @@ tags:
 ---
 
 # FAQ
-Here are some quick answers to frequently asked questions. See also our [Troubleshooting](/reference-architecture/reference/troubleshooting).
+Here are some quick answers to frequently asked questions. See also our [Troubleshooting](/resources/legacy/troubleshooting).
 
 ## How can we support you?
 

docs/intro/intro.mdx

@@ -69,7 +69,7 @@ This documentation site breaks down SweetOps into the following sections to help
     - [**Setup**](/tags/setup): show how to step up a specific layer or resource in easy-to-follow steps.
     - [**How-To Guides & Tutorials**](/tags/tutorial): show how to solve specific problems with SweetOps via a series of easy-to-follow steps.
 
-    Then we include some of our [Best Practices](/best-practices) and [Architectural Design Decisions](/adrs) to help you understand the reasoning behind our choices.
+    Then we include some of our [Best Practices](/best-practices) and [Architectural Design Decisions](/resources/adrs) to help you understand the reasoning behind our choices.
   </Step>
 
   <Step>

docs/jumpstart/action-items.mdx

@@ -37,7 +37,7 @@ Before we can get started, here's the minimum information we need from you.
     <TaskList>
       - [ ] Create a new Slack channel for AWS notifications, for example `#aws-notifications`
       - [ ] Invite Cloud Posse
-      - [ ] [Set Up AWS Email Notifications](/reference-architecture/setup/cold-start/how-to-set-up-aws-email-notifications/) with your chosen email address for each account. If you are using plus-addressing, you will only need to connect the primary email address.
+      - [ ] [Set Up AWS Email Notifications](/layers/accounts/tutorials/how-to-set-up-aws-email-notifications) with your chosen email address for each account. If you are using plus-addressing, you will only need to connect the primary email address.
       - [ ] [Create a Slack Webhook for that same channel](https://api.slack.com/messaging/webhooks). This is required to enable Budget alerts in Slack. Please share the Webhook URL and the final name of the Slack channel with Cloud Posse.
     </TaskList>
   </Step>
@@ -64,7 +64,7 @@ Before we can get started, here's the minimum information we need from you.
     Please also provision a single test user in your IdP for Cloud Posse to use for testing and add those user credentials to 1Password.
 
     - [GSuite](https://aws.amazon.com/blogs/security/how-to-use-g-suite-as-external-identity-provider-aws-sso/): Follow the "Google Workspace SAML application setup" steps only. Cloud Posse will handle the rest.
-    - [Office 365](/reference-architecture/how-to-guides/integrations/how-to-setup-office-365-aws-sso/)
+    - [Office 365](/layers/identity/aws-sso/office365/how-to-setup-office-365-aws-sso)
     - [JumpCloud](https://jumpcloud.com/support/integrate-with-aws-iam-identity-center)
     - [Other AWS supported IdPs: Azure AD, CyberArk, Okta, OneLogin, Ping Identity](https://docs.aws.amazon.com/singlesignon/latest/userguide/supported-idps.html)
 
@@ -80,7 +80,7 @@ Before we can get started, here's the minimum information we need from you.
     If deploying AWS SAML as an alternative to AWS SSO, we will need a separate configuration and metadata file. Again, please refer to the relevant linked guide.
 
     - [GSuite](https://aws.amazon.com/blogs/desktop-and-application-streaming/setting-up-g-suite-saml-2-0-federation-with-amazon-appstream-2-0/): Follow Steps 1 through 7. This document refers to Appstream, but the process will be the same for AWS.
-    - [Office 365](/reference-architecture/how-to-guides/integrations/how-to-setup-saml-login-to-aws-from-office-365/)
+    - [Office 365](/layers/identity/aws-saml/how-to-setup-saml-login-to-aws-from-office-365)
     - [JumpCloud](https://support.jumpcloud.com/support/s/article/getting-started-applications-saml-sso2)
     - [Okta](https://help.okta.com/en-us/Content/Topics/DeploymentGuides/AWS/aws-configure-identity-provider.htm)
   </Step>
@@ -97,7 +97,7 @@ Feel free to store these secrets in 1Password if you do not have AWS access yet.
 
 ### Self Hosted Github Runners with Philips Labs (ECS)
 
-If you have chosen ECS as a platform, we recommend deploying Philips Labs GitHub Action Runners. Please read through the [Philips Labs GitHub Action Runners Setup Requirements](/reference-architecture/setup/philips-labs-github-runners/#requirements).
+If you have chosen ECS as a platform, we recommend deploying Philips Labs GitHub Action Runners. Please read through the [Philips Labs GitHub Action Runners Setup Requirements](/layers/github-actions/philips-labs-github-runners#requirements).
 
 In particular, we will need a new GitHub App including a Private Key, an App ID, and an App Installation ID. Please store these secrets in 1Password.
 
@@ -176,23 +176,23 @@ Confirm if you plan to deploy any of the following integrations. If so, we will
   <Step>
     ### <StepNumber/> Spacelift Access
 
-    If deploying Spacelift, we will need a Spacelift subscription. Please see [How to Sign Up for Spacelift](/reference-architecture/how-to-guides/integrations/spacelift/). This document answers many common questions and describes the signup process step-by-step.
+    If deploying Spacelift, we will need a Spacelift subscription. Please see [How to Sign Up for Spacelift](/layers/spacelift). This document answers many common questions and describes the signup process step-by-step.
 
     Cloud Posse will need "admin" access for Spacelift to deploy all resources.
   </Step>
 
   <Step>
     ### <StepNumber/> Datadog Access
 
-    Sign up for Datadog following the [How to Sign Up for Datadog?](/reference-architecture/how-to-guides/integrations/datadog/how-to-sign-up-for-datadog/) documentation.
+    Sign up for Datadog following the [How to Sign Up for Datadog?](/layers/monitoring/datadog/tutorials/how-to-sign-up-for-datadog) documentation.
 
     Cloud Posse will need "admin" access for Datadog as well to complete the Datadog setup.
   </Step>
 
   <Step>
     ### <StepNumber/> OpsGenie Access
 
-    Sign up for OpsGenie following the [How to Sign Up for OpsGenie?](/reference-architecture/how-to-guides/tutorials/how-to-implement-incident-management-with-opsgenie/how-to-sign-up-for-opsgenie/) documentation.
+    Sign up for OpsGenie following the [How to Sign Up for OpsGenie?](/layers/alerting/opsgenie/how-to-sign-up-for-opsgenie) documentation.
   </Step>
 </Steps>
 
@@ -241,6 +241,6 @@ If your engagement with Cloud Posse includes Release Engineering, we will also n
   <Step>
     ### <StepNumber/> PATs for EKS with ArgoCD
 
-    ArgoCD requires a number of PATs. Please see [How to set up Authorization for ArgoCD with GitHub PATs](/reference-architecture/how-to-guides/integrations/argocd/pats)
+    ArgoCD requires a number of PATs. Please see [How to set up Authorization for ArgoCD with GitHub PATs](/layers/software-delivery/eks-argocd/tutorials/pats)
   </Step>
 </Steps>

docs/jumpstart/kick-off.mdx

@@ -98,16 +98,16 @@ This document outlines what to expect from your first call with Cloud Posse. In
     ### <StepNumber/> Review [Design Decisions](/reference-architecture/fundamentals/design-decisions)
 
     <TaskList>
-      - [ ] [Decide on Namespace Abbreviation](/reference-architecture/fundamentals/design-decisions/cold-start/decide-on-namespace-abbreviation/)
-      - [ ] [Decide on Infrastructure Repository Name](/reference-architecture/fundamentals/design-decisions/cold-start/decide-on-infrastructure-repository-name/)
-      - [ ] [Decide on Email Address Format for AWS Accounts](/reference-architecture/fundamentals/design-decisions/cold-start/decide-on-email-address-format-for-aws-accounts/)
-      - [ ] [Decide on IdP](/reference-architecture/fundamentals/design-decisions/cold-start/decide-on-idp/)
-      - [ ] [Decide on IdP Integration Method](/reference-architecture/fundamentals/design-decisions/cold-start/decide-on-idp-integration)
-      - [ ] [Decide on Primary AWS Region and Secondary AWS Region](/reference-architecture/fundamentals/design-decisions/cold-start/decide-on-primary-aws-region/)
-      - [ ] [Decide on CIDR Allocation Strategy](/reference-architecture/fundamentals/design-decisions/cold-start/decide-on-cidr-allocation/)
-      - [ ] [Decide on Service Discovery Domain](/reference-architecture/fundamentals/design-decisions/cold-start/decide-on-service-discovery-domain/)
+      - [ ] [Decide on Namespace Abbreviation](/layers/foundation/design-decisions/decide-on-namespace-abbreviation)
+      - [ ] [Decide on Infrastructure Repository Name](/layers/foundation/design-decisions/decide-on-infrastructure-repository-name)
+      - [ ] [Decide on Email Address Format for AWS Accounts](/layers/accounts/design-decisions/decide-on-email-address-format-for-aws-accounts)
+      - [ ] [Decide on IdP](/layers/identity/design-decisions/decide-on-idp)
+      - [ ] [Decide on IdP Integration Method](/layers/identity/design-decisions/decide-on-idp-integration)
+      - [ ] [Decide on Primary AWS Region and Secondary AWS Region](/layers/network/design-decisions/decide-on-primary-aws-region)
+      - [ ] [Decide on CIDR Allocation Strategy](/layers/network/design-decisions/decide-on-cidr-allocation)
+      - [ ] [Decide on Service Discovery Domain](/layers/network/design-decisions/decide-on-service-discovery-domain)
       - [ ] [Decide on Vanity Domain](/reference-architecture/reference/adrs/jumpstart/decide-on-vanity-domain/)
-      - [ ] [Decide on Release Engineering Strategy](/reference-architecture/fundamentals/design-decisions/cold-start/decide-on-release-engineering-strategy/)
+      - [ ] [Decide on Release Engineering Strategy](/layers/software-delivery/design-decisions/decide-on-release-engineering-strategy)
     </TaskList>
   </Step>
 
@@ -116,16 +116,16 @@ This document outlines what to expect from your first call with Cloud Posse. In
 
     Generally, expect to schedule the following Handoff calls. These are subject to change and should be adaptable to fit your individual engagement.
     <TaskList>
-      - [Kick Off](/reference-architecture/fundamentals/kick-off/)
+      - [Kick Off](/jumpstart/kick-off)
       - [Introduction to Toolset](/reference-architecture/fundamentals)
       - [Identity and Authentication](/reference-architecture/fundamentals/iam-identity/)
-      - [Component Development](/reference-architecture/fundamentals/component-development/)
+      - [Component Development](/learn/component-development)
       - [Account Management](/reference-architecture/fundamentals/account-management/)
       - [Network and DNS](/reference-architecture/fundamentals/network-and-dns/)
-      - [Spacelift](/reference-architecture/fundamentals/spacelift/) or [GitOps](/reference-architecture/fundamentals/gitops/)
-      - [ECS](/reference-architecture/fundamentals/ecs/) or [EKS](/reference-architecture/fundamentals/eks/)
-      - [Monitoring](/reference-architecture/fundamentals/monitoring/) and [Alerting](/reference-architecture/fundamentals/alerting)
-      - [Release Engineering](/reference-architecture/fundamentals/release-engineering/)
+      - [Spacelift](/layers/spacelift) or [GitOps](/layers/gitops)
+      - [ECS](/layers/ecs) or [EKS](/layers/eks)
+      - [Monitoring](/layers/monitoring) and [Alerting](/layers/alerting)
+      - [Release Engineering](/layers/software-delivery)
       - Final Call (Sign-off)
     </TaskList>
   </Step>
@@ -164,7 +164,7 @@ Cloud Posse has noticed several patterns that lead to successful projects.
 
 ## Get Support
 
-See [Support](/reference-architecture/support/)
+See [Support](/support)
 
 ### Slack
 

docs/jumpstart/onboarding.mdx

@@ -17,5 +17,5 @@ After ensuring you’ve satisfied all the prerequisites, we recommend doing the
       Cloud Posse PMs can help add members. **Only applicable for Enterprise engagements**.
 - [ ] Learn more about Cloud Posse because as a [DevOps Accelerator](https://cloudposse.com) we are very different from
       typical professional services companies.
-- [ ] Review the different ways you can get [Support](/reference-architecture/support).
+- [ ] Review the different ways you can get [Support](/support).
 </TaskList>

docs/jumpstart/support.mdx

@@ -14,11 +14,11 @@ Learn how to access support from Cloud Posse and the various support options ava
 
 All customers have direct access to our team via Slack, Zoom, and Email. If you’re having trouble getting the help you need, you can always reach out to Cloud Posse PMs who will direct you to the right person.
 
-1. Use the private shared Slack channels between Cloud Posse and your company to ask our team questions directly. See [How to Provision Shared Slack Channels](/reference-architecture/how-to-guides/integrations/how-to-provision-shared-slack-channels) to set up additional channels with our team.
+1. Use the private shared Slack channels between Cloud Posse and your company to ask our team questions directly. See [How to Provision Shared Slack Channels](/jumpstart/tutorials/how-to-provision-shared-slack-channels) to set up additional channels with our team.
 
 2. **Ask questions during calls.** Ask Cloud Posse PMs to add your question to the agenda.
 
-3. Join the [Shared Customer Workshops](/reference-architecture/fundamentals/kick-off/#shared-customer-workshop) and ask the team questions. Customer Workshops are only available to current and previous customers and are held twice a week. Please reach out to Cloud Posse PMs if you need to be added to the recurring events.
+3. Join the [Shared Customer Workshops](/jumpstart/kick-off#shared-customer-workshop) and ask the team questions. Customer Workshops are only available to current and previous customers and are held twice a week. Please reach out to Cloud Posse PMs if you need to be added to the recurring events.
 
 4. Reach out to Cloud Posse PMs to book time directly with members of our team. We're here to help you.
 
@@ -78,7 +78,7 @@ Reach out in the `#refarch` channel with questions specific to Cloud Posse archi
 
 :::
 
-3. Join the [Shared Customer Workshops](/reference-architecture/fundamentals/kick-off/#shared-customer-workshop) and ask our team questions. Customer Workshops are only available to current and previous customers and are held twice weekly. You can still join and ask questions after your engagement has concluded! Please reach out to Cloud Posse PMs if you need to be added to the recurring events.
+3. Join the [Shared Customer Workshops](/jumpstart/kick-off#shared-customer-workshop) and ask our team questions. Customer Workshops are only available to current and previous customers and are held twice weekly. You can still join and ask questions after your engagement has concluded! Please reach out to Cloud Posse PMs if you need to be added to the recurring events.
 
 4. [Sign up](https://cloudposse.com/office-hours/) for our free public “Office Hours” are held every Wednesday at 11:30am PT via Zoom. Past recordings are available on our [YouTube channel](https://youtube.com/cloudposse).
 

docs/layers/accounts/design-decisions/decide-on-aws-account-flavors-and-organizational-units.mdx

@@ -47,7 +47,7 @@ This is our recommended approach.
 :::note
 
 It is advised to keep the names of accounts as short as possible because of resources with low max character limits
-[AWS Resources Limitations](/resources/aws/aws-feature-requests-and-limitations)
+[AWS Resources Limitations](/resources/legacy/aws-feature-requests-and-limitations)
 
 :::
 

docs/layers/accounts/tutorials/how-to-add-a-new-organizational-unit.mdx

@@ -25,7 +25,7 @@ Add the new OU to the `account` catalog and reapply the component.
 :::info
 
 The `account` component must be applied with the SuperAdmin user, which is typically found in 1Password. For more on
-SuperAdmin, see[How to Create SuperAdmin user](/learn/accounts/tutorials/how-to-create-superadmin-user)
+SuperAdmin, see[How to Create SuperAdmin user](/layers/accounts/tutorials/how-to-create-superadmin-user)
 
 :::
 

docs/layers/accounts/tutorials/how-to-create-and-setup-aws-accounts.mdx

@@ -204,4 +204,4 @@ are more components to deploy.
 
 ## References
 
-- [How to Delete AWS Accounts](/learn/accounts/tutorials/how-to-delete-aws-accounts) (in case a mistake was made)
+- [How to Delete AWS Accounts](/layers/accounts/tutorials/how-to-delete-aws-accounts) (in case a mistake was made)

docs/layers/accounts/tutorials/how-to-delete-aws-accounts.mdx

@@ -233,6 +233,6 @@ You can only close up to 10% of accounts per month.
 - [https://onecloudplease.com/blog/automating-aws-account-deletion#deleting-an-aws-account](https://onecloudplease.com/blog/automating-aws-account-deletion#deleting-an-aws-account)
   (including for comedic value) 🤣
 
-- [How to Create and Setup AWS Accounts](/learn/accounts/tutorials/how-to-create-and-setup-aws-accounts)
+- [How to Create and Setup AWS Accounts](/layers/accounts/tutorials/how-to-create-and-setup-aws-accounts)
 
 - [https://github.com/gruntwork-io/cloud-nuke](https://github.com/gruntwork-io/cloud-nuke)

docs/layers/accounts/tutorials/how-to-register-pristine-aws-root-account.mdx

@@ -114,7 +114,7 @@ Congratulations! You are now able to proceed with the rest of the cold start pro
 
 ### Related articles
 
-- [Decide on AWS Organization Strategy](/learn/accounts/design-decisions/decide-on-aws-organization-strategy)
+- [Decide on AWS Organization Strategy](/layers/accounts/design-decisions/decide-on-aws-organization-strategy)
 
 - [AWS Documentation: How do I create and activate a new AWS account?](https://aws.amazon.com/premiumsupport/knowledge-center/create-and-activate-aws-account/)