Refactored with refarch-scaffold Updates (#805)

Co-authored-by: Benbentwo <14911525+Benbentwo@users.noreply.github.com>
Co-authored-by: Cloud Posse Bot (CI/CD) <bot@cloudposse.com>
Co-authored-by: milldr <14060048+milldr@users.noreply.github.com>

Author: 3 people

docs/jumpstart/action-items.mdx

@@ -169,14 +169,6 @@ Confirm if you plan to deploy any of the following integrations. If so, we will
 
 <Steps>
 
-  <Step>
-    ### <StepNumber/> Spacelift Access
-
-    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
 
@@ -185,11 +177,6 @@ Confirm if you plan to deploy any of the following integrations. If so, we will
     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?](/layers/alerting/opsgenie/how-to-sign-up-for-opsgenie) documentation.
-  </Step>
 </Steps>
 
 

docs/jumpstart/handoffs.mdx

@@ -77,13 +77,13 @@ https://github.com/facebook/docusaurus/issues/6201
     <PrimaryCTA to="/layers/software-delivery">Get Started</PrimaryCTA>
   </Slide>
 
-  <Slide title="GitOps with GitHub Actions">
+  <Slide title="Terraform Automation with GitHub Actions">
     <figure>
       <ReactPlayer controls url='https://docs.cloudposse.com/assets/refarch/handoffs/gitops.mp4' />
       <figcaption>AI generated voice</figcaption>
     </figure>
 
-    <PrimaryCTA to="/layers/gitops">Get Started</PrimaryCTA>
+    <PrimaryCTA to="/layers/atmos-pro">Get Started</PrimaryCTA>
   </Slide>
 
   <Slide title="ECS Platform">

docs/jumpstart/kickoff.mdx

@@ -131,7 +131,7 @@ This document outlines what to expect from your first call with Cloud Posse. In
     </TaskList>
 
     <Admonition>
-      These are the design decisions you can customize as part of the Jumpstart package. [All other decisions are pre-made](/tags/design-decision/) for you, but you’re welcome to review them. If you’d like to make additional changes, [let us know—we’re happy to provide a quote](https://cloudposse.com/meet).
+      These are the design decisions you can customize as part of the Jumpstart package. [All other decisions are pre-made](/tags/design-decision/) for you, but you're welcome to review them. If you'd like to make additional changes, [let us know—we're happy to provide a quote](https://cloudposse.com/meet).
     </Admonition>
 
   </Step>
@@ -147,9 +147,9 @@ This document outlines what to expect from your first call with Cloud Posse. In
       - [Component Development](/learn/component-development)
       - [Account Management](/layers/accounts/)
       - [Network and DNS](/layers/network/)
-      - [Spacelift](/layers/spacelift) or [GitOps](/layers/gitops)
+      - [Automate Terraform](/layers/atmos-pro)
       - [ECS](/layers/ecs) or [EKS](/layers/eks)
-      - [Monitoring](/layers/monitoring) and [Alerting](/layers/alerting)
+      - [Monitoring](/layers/monitoring)
       - [Release Engineering](/layers/software-delivery)
       - Final Call (Sign-off)
     </TaskList>
@@ -197,7 +197,7 @@ The Jumpstart accelerator does not include support. To get help, we offer multip
 
 ### Slack
 
-If you need help scheduling meetings, please post in your team’s Cloud Posse channel (e.g., `#acme-general`). This keeps discussions open and prevents duplicated or siloed information in direct messages (DMs). In general, please avoid DMs, as they make it harder to escalate requests or follow up. Feel free to @ a team member if you need assistance—we’re here to help!
+If you need help scheduling meetings, please post in your team's Cloud Posse channel (e.g., `#acme-general`). This keeps discussions open and prevents duplicated or siloed information in direct messages (DMs). In general, please avoid DMs, as they make it harder to escalate requests or follow up. Feel free to @ a team member if you need assistance—we're here to help!
 
 You can also reach out to our community with our [SweetOps Slack community](#sweetops-slack).
 

docs/jumpstart/tutorials/offboarding-cloudposse.mdx

@@ -87,10 +87,6 @@ See:
 
 Offboard any `@cloudposse.com` email addresses.
 
-### OpsGenie
-
-Offboard any `@cloudposse.com` email addresses.
-
 ### Customer Jira & Confluence
 
 Some customers have added our team directly to their Atlassian products. Make sure to offboard any `@cloudposse.com` email addresses.

docs/layers/accounts/account-baseline.mdx

@@ -16,16 +16,16 @@ Now that all the accounts have been deployed, we need to finalize the setup of t
 
 | Steps                      | Actions                             |
 | -------------------------- | ----------------------------------- |
-| Deploy baseline components | `atmos workflow deploy -f baseline` |
-| Deploy account budgets     | Create Slack Webhook and `atmos workflow deploy -f accounts` |
+| Deploy baseline components | `atmos workflow deploy -f quickstart/foundation/baseline` |
+| Deploy account budgets     | Create Slack Webhook and `atmos workflow deploy -f quickstart/foundation/accounts` |
 
 <Steps>
   <Step>
   ## <StepNumber/> Deploy CloudTrail
 
   Deploy CloudTrail and the the CloudTrail bucket:
 
-  <AtmosWorkflow workflow="deploy/cloudtrail" fileName="baseline" />
+      <AtmosWorkflow workflow="deploy/cloudtrail" fileName="quickstart/foundation/baseline" />
   </Step>
 
   <Step>
@@ -106,7 +106,7 @@ Now that all the accounts have been deployed, we need to finalize the setup of t
                time_unit: MONTHLY
      ```
   5. Finally, reapply `account-settings` in any changed account to apply the new settings
-     <AtmosWorkflow workflow="deploy/account-settings" fileName="accounts" />
+     <AtmosWorkflow workflow="deploy/account-settings" fileName="quickstart/foundation/accounts" />
   </Steps>
   </Step>
 </Steps>

docs/layers/accounts/accounts.mdx

@@ -304,29 +304,4 @@ Cloud Posse manages this process with the following components.
 - [Decide on AWS Account Flavors and Organizational Units](/layers/accounts/design-decisions/decide-on-aws-account-flavors-and-organizational-units/)
 - [Decide on AWS Support](/layers/accounts/design-decisions/decide-on-aws-support/)
 - [Decide on Email Address Format for AWS Accounts](/layers/accounts/design-decisions/decide-on-email-address-format-for-aws-accounts/)
-- [Structure of Terraform S3 State Backend Bucket](/layers/accounts/tutorials/terraform-s3-state/)
-
-
-### Mixins and Imports with Atmos
-
-As infrastructure grows, we end up with hundreds or thousands of settings for components and stack configurations. If we
-copy and paste these settings everywhere, it’s error-prone and not DRY. What we really want to do is to define a sane
-set of defaults and override those defaults when we need them to change.
-
-We accomplish this with Mixins. Mixins are imported into all stacks and each follow a set of rules. We use the
-`mixins/region` and `mixins/account` configurations to define common **variables** for all stacks. For example,
-`mixins/region/us-east-1.yaml` will define the variable `region: us-east-1`.
-
-**Note.** Do not import components into the account or region mixins. These are imported multiple times to define common
-variables, so any component imports would be duplicated and cause an Atmos error such as this:
-
-```
-Executing command:
-/usr/bin/atmos terraform deploy account-settings -s core-gbl-artifacts
-
-Found duplicate config for the component 'account-settings' for the stack 'core-gbl-artifacts' in the files: orgs/cch/core/artifacts/global-region/baseline, orgs/cch/core/artifacts/global-region/monitoring, orgs/cch/core/artifacts/global-region/identity.
-Check that all context variables in the stack name pattern '{tenant}-{environment}-{stage}' are correctly defined in the files and not duplicated.
-Check that all imports are valid.
-
-exit status 1
-```
+- [Structure of Terraform S3 State Backend Bucket](/layers/accounts/tutorials/terraform-s3-state/)

docs/layers/accounts/deploy-accounts.mdx

@@ -11,17 +11,18 @@ import Step from '@site/src/components/Step';
 import StepNumber from '@site/src/components/StepNumber';
 import Note from '@site/src/components/Note';
 import AtmosWorkflow from '@site/src/components/AtmosWorkflow';
+import TaskList from '@site/src/components/TaskList';
 
 <Intro>
 This step-by-step process outlines how to deploy AWS accounts using `atmos` workflows and ClickOps steps. It covers necessary preparations, such as configuring the AWS Organization, increasing account quotas, and verifying account configurations. The guide details the deployment processes and post-deployment configurations, including setting up account settings, enabling AWS RAM for Organizations, and performing certain manual configurations via ClickOps.
 </Intro>
 
 | Steps                     | Actions                                              |
 | ------------------------- | ---------------------------------------------------- |
-| Deploy AWS Organization   | `atmos workflow deploy/organization -f accounts`     |
+| Deploy AWS Organization   | `atmos workflow deploy/organization -f quickstart/foundation/accounts`     |
 | Prepare accounts creation | Click Ops                                            |
-| Deploy accounts           | `atmos workflow deploy/accounts -f accounts`         |
-| Deploy accounts settings  | `atmos workflow deploy/account-settings -f accounts` |
+| Deploy accounts           | `atmos workflow deploy/accounts -f quickstart/foundation/accounts`         |
+| Deploy accounts settings  | `atmos workflow deploy/account-settings -f quickstart/foundation/accounts` |
 | Finalize account setup    | Click Ops                                            |
 
 <Steps>
@@ -34,16 +35,18 @@ This step-by-step process outlines how to deploy AWS accounts using `atmos` work
 
     You should double-check the following:
 
-    1. Check that `stacks/catalog/account.yaml` has the values you expect, especially account email format
-    2. Run `atmos describe component account -s core-gbl-root` to inspect the final component configuration (e.g. _after_
+    <TaskList>
+    - Check that `stacks/catalog/account.yaml` has the values you expect, especially account email format
+    - Run `atmos describe component account -s core-gbl-root` to inspect the final component configuration (e.g. _after_
       all the mixins have been imported)
-    3. Plan the run with `atmos terraform plan account -s core-gbl-root`
+    - Plan the run with `atmos terraform plan account -s core-gbl-root`
+    </TaskList>
   </Step>
 
   <Step>
     ## <StepNumber/> Deploy the AWS Organization
 
-    <AtmosWorkflow workflow="deploy/organization" fileName="accounts" />
+    <AtmosWorkflow workflow="deploy/organization" fileName="quickstart/foundation/accounts" />
 
   </Step>
 
@@ -144,7 +147,7 @@ This step-by-step process outlines how to deploy AWS accounts using `atmos` work
 
     Once confident, begin the accounts deployment:
 
-    <AtmosWorkflow workflow="deploy/accounts" fileName="accounts" />
+    <AtmosWorkflow workflow="deploy/accounts" fileName="quickstart/foundation/accounts" />
 
     <Note title="Info">
       With the addition of support for dynamic Terraform roles, our `baseline` cold start refarch layer now depends
@@ -168,7 +171,7 @@ This step-by-step process outlines how to deploy AWS accounts using `atmos` work
 
     Once you've created the accounts, you'll need to provision the baseline configuration within the accounts themselves. Run the following:
 
-    <AtmosWorkflow workflow="deploy/account-settings" fileName="accounts" />
+    <AtmosWorkflow workflow="deploy/account-settings" fileName="quickstart/foundation/accounts" />
 
     The workflows will kick off several sequential Terraform runs to provision all the AWS member account settings for
     member accounts in the Organization.

docs/layers/accounts/design-decisions/decide-on-email-address-format-for-aws-accounts.mdx

@@ -55,11 +55,6 @@ Mailgun supports plus addressing and complex forwarding rules. It’s free for 5
 Google Groups are probably the most common solution we see. It
 [works very well with plus addressing](https://support.google.com/a/users/answer/9308648?hl=en).
 
-### Use OpsGenie Email Integration
-
-OpsGenie is nice, but it does not support plus addressing. That means we’ll need to provision one integration for each
-account.
-
 ### Use AWS SES with Lambda Forwarder (catch-22)
 
 Provisioning AWS SES is nice, but we need an email address even for the root account, so it doesn’t solve the cold-start

docs/layers/accounts/faq.mdx

@@ -54,6 +54,30 @@ This component manages the state of all AWS accounts, so apply with extreme caut
 
 [Follow the documentation for creating a new Organizational Unit](/layers/accounts/tutorials/how-to-add-a-new-organizational-unit/)
 
+### How do I use mixins and imports with Atmos
+
+As infrastructure grows, we end up with hundreds or thousands of settings for components and stack configurations. If we
+copy and paste these settings everywhere, it’s error-prone and not DRY. What we really want to do is to define a sane
+set of defaults and override those defaults when we need them to change.
+
+We accomplish this with Mixins. Mixins are imported into all stacks and each follow a set of rules. We use the
+`mixins/region` and `mixins/account` configurations to define common **variables** for all stacks. For example,
+`mixins/region/us-east-1.yaml` will define the variable `region: us-east-1`.
+
+**Note.** Do not import components into the account or region mixins. These are imported multiple times to define common
+variables, so any component imports would be duplicated and cause an Atmos error such as this:
+
+```
+Executing command:
+/usr/bin/atmos terraform deploy account-settings -s core-gbl-artifacts
+
+Found duplicate config for the component 'account-settings' for the stack 'core-gbl-artifacts' in the files: orgs/cch/core/artifacts/global-region/baseline, orgs/cch/core/artifacts/global-region/monitoring, orgs/cch/core/artifacts/global-region/identity.
+Check that all context variables in the stack name pattern '{tenant}-{environment}-{stage}' are correctly defined in the files and not duplicated.
+Check that all imports are valid.
+
+exit status 1
+```
+
 ### Why does `account-map` fail with "The given key does not identify an element in this collection value"?
 
 This is a common error you may encounter when reading from `account-map`:

docs/layers/accounts/initialize-tfstate.mdx

@@ -17,7 +17,7 @@ Follow these steps to configure and initialize the Terraform state backend using
 
 | Steps                     | Actions                                   |
 | ------------------------- | ----------------------------------------- |
-| Configure Terraform state | `atmos workflow init/tfstate -f baseline` |
+| Configure Terraform state | `atmos workflow init/tfstate -f quickstart/foundation/baseline` |
 
 ## Setting up the Terraform State Backend
 
@@ -35,15 +35,27 @@ If you look at `components/terraform/`, you'll see a bunch of directories. These
 
     Vendor the Terraform State Backend component by running the following command. The steps here require the `tfstate-backend` and `account-map` components.
 
-    <AtmosWorkflow workflow="vendor" fileName="baseline" />
+    :::tip What is Vendoring?
+
+    Vendoring downloads the upstream component files from a central repository at a specified version. In this case, we are pulling the baseline components, which include all account components, the Terraform State component, and other necessary files for setting up the account foundation. 
+    
+    This step only downloads the files to your local project - it does not deploy or make any changes to your infrastructure.
+
+    [Read more about vendoring with Atmos](https://atmos.tools/core-concepts/vendor/)
+
+    :::
+
+    <AtmosWorkflow workflow="vendor" fileName="quickstart/foundation/baseline" />
 
   </Step>
   <Step>
     ## <StepNumber/> Initialize the Terraform State Backend
 
-    Initialize the Terraform State Backend by running the following command:
+    Run the following command to initialize the Terraform State Backend. This workflow has two steps:
+    - Create the backend using a local Terraform state
+    - Once the backend bucket exists, migrate the state file into the newly created S3 bucket
 
-    <AtmosWorkflow workflow="init/tfstate" fileName="baseline" />
+    <AtmosWorkflow workflow="init/tfstate" fileName="quickstart/foundation/baseline" />
   </Step>
 
   <Step>