Update terraform/opentofu design decision (#715)

Author: osterman

docs/jumpstart/kickoff.mdx

@@ -4,37 +4,48 @@ sidebar_label: "Kick Off"
 sidebar_position: 2
 describe: Set project expectations for Jumpstarts with Cloud Posse
 ---
-import Link from '@docusaurus/Link'
-import KeyPoints from '@site/src/components/KeyPoints'
-import Steps from '@site/src/components/Steps'
-import Step from '@site/src/components/Step'
-import StepNumber from '@site/src/components/StepNumber'
-import Intro from '@site/src/components/Intro'
-import ActionCard from '@site/src/components/ActionCard'
-import PrimaryCTA from '@site/src/components/PrimaryCTA'
-import TaskList from '@site/src/components/TaskList'
-import Admonition from '@theme/Admonition';
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
+
+import Link from "@docusaurus/Link";
+import KeyPoints from "@site/src/components/KeyPoints";
+import Steps from "@site/src/components/Steps";
+import Step from "@site/src/components/Step";
+import StepNumber from "@site/src/components/StepNumber";
+import Intro from "@site/src/components/Intro";
+import ActionCard from "@site/src/components/ActionCard";
+import PrimaryCTA from "@site/src/components/PrimaryCTA";
+import TaskList from "@site/src/components/TaskList";
+import Admonition from "@theme/Admonition";
+import Tabs from "@theme/Tabs";
+import TabItem from "@theme/TabItem";
 
 <Intro>
-The kickoff process for Jumpstart engagements with Cloud Posse ensures a smooth start with clear communication for a successful project delivery. During the call, we will confirm contract requirements and set project expectations. We also cover how Cloud Posse will deploy your infrastructure in layers using our reference architecture and introduce various support options, including Slack channels, customer workshops, and office hours.
+  The kickoff process for Jumpstart engagements with Cloud Posse ensures a
+  smooth start with clear communication for a successful project delivery.
+  During the call, we will confirm contract requirements and set project
+  expectations. We also cover how Cloud Posse will deploy your infrastructure in
+  layers using our reference architecture and introduce various support options,
+  including Slack channels, customer workshops, and office hours.
 </Intro>
 
 <KeyPoints title="We Will Review">
-- **Kickoff Process:** Establish roles, confirm requirements, and set project expectations for a smooth start
-- **Implementation Phase:** Understand how we go about provisioning infrastructure in layers using the reference architecture, including comprehensive handoffs with documentation
-- **Support and Communication:** Review the multiple channels for support, including Slack, customer workshops, office hours, and detailed documentation to ensure successful engagement
+  - **Kickoff Process:** Establish roles, confirm requirements, and set project
+  expectations for a smooth start - **Implementation Phase:** Understand how we
+  go about provisioning infrastructure in layers using the reference
+  architecture, including comprehensive handoffs with documentation - **Support
+  and Communication:** Review the multiple channels for support, including
+  Slack, customer workshops, office hours, and detailed documentation to ensure
+  successful engagement
 </KeyPoints>
 
 ## Preparing for the Kickoff Meeting
 
 This document outlines what to expect from your first call with Cloud Posse. In order to make the most of this meeting, please read through this document and come prepared with questions. In particular, please review the following:
 
 <Steps>
-1. Identify stakeholders and establish ownership of the engagement within your Organization.
-2. Read through the [Design Decisions](#review-design-decisions) and prepare questions and decisions.
-3. Review the list of [Actions Items](#action-items) following this call.
+  1. Identify stakeholders and establish ownership of the engagement within your
+  Organization. 2. Read through the [Design Decisions](#review-design-decisions)
+  and prepare questions and decisions. 3. Review the list of [Actions
+  Items](#action-items) following this call.
 </Steps>
 
 ## Kickoff Meeting Agenda
@@ -44,6 +55,7 @@ This document outlines what to expect from your first call with Cloud Posse. In
     ### <StepNumber/> Introductions
 
     Here we will review who is on the call, what their roles are, and identify our technical point of contact at Cloud Posse. We will also review the working timezones of the teams.
+
   </Step>
 
   <Step>
@@ -58,6 +70,7 @@ This document outlines what to expect from your first call with Cloud Posse. In
     <Admonition type="tip">
       If you come prepared for Hand-Off calls, we can skip the lecture and spend more time answering questions or working through hands-on labs.
     </Admonition>
+
   </Step>
 
   <Step>
@@ -82,6 +95,7 @@ This document outlines what to expect from your first call with Cloud Posse. In
     </Tabs>
 
     This is a great opportunity to get your questions answered and to get help with your project.
+
   </Step>
 
   <Step>
@@ -94,18 +108,21 @@ This document outlines what to expect from your first call with Cloud Posse. In
     This is a good way to keep up with the latest developments and trends in the DevOps community.
 
     Sign up at [cloudposse.com/office-hours](https://cloudposse.com/office-hours/)
+
   </Step>
 
   <Step>
     ### <StepNumber/> SweetOps Slack
 
     If you are looking for a community of like-minded DevOps practitioners, please join the [SweetOps Slack](https://slack.sweetops.com/).
+
   </Step>
 
   <Step>
     ### <StepNumber/> Review Design Decisions
 
     <TaskList>
+      - [ ] [Decide on Terraform Version](/layers/project/design-decisions/decide-on-terraform-version)
       - [ ] [Decide on Namespace Abbreviation](/layers/project/design-decisions/decide-on-namespace-abbreviation)
       - [ ] [Decide on Infrastructure Repository Name](/layers/project/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)
@@ -117,6 +134,11 @@ This document outlines what to expect from your first call with Cloud Posse. In
       - [ ] [Decide on Vanity Domain](/layers/network/design-decisions/decide-on-vanity-branded-domain)
       - [ ] [Decide on Release Engineering Strategy](/layers/software-delivery/design-decisions/decide-on-release-engineering-strategy)
     </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).
+    </Admonition>
+
   </Step>
 
   <Step>
@@ -136,10 +158,10 @@ This document outlines what to expect from your first call with Cloud Posse. In
       - [Release Engineering](/layers/software-delivery)
       - Final Call (Sign-off)
     </TaskList>
+
   </Step>
 </Steps>
 
-
 ## How to Succeed
 
 Cloud Posse has noticed several patterns that lead to successful projects.
@@ -149,24 +171,28 @@ Cloud Posse has noticed several patterns that lead to successful projects.
     ### <StepNumber/> Come Prepared
 
     Review six pagers and documentation before Hand-Off calls. This will help you to know what questions need to be asked. Coming unprepared will lead to a lot of questions and back-and-forth. This will slow down material resulting in less time for new material.
+
   </Step>
 
   <Step>
     ### <StepNumber/> Take Initiative
 
     The most successful customers take initiative to make customizations to their Reference Architecture. This is a great way to make the Reference Architecture your own. It also helps to build a deeper understanding of the Reference Architecture and how it works.
+
   </Step>
 
   <Step>
     ### <StepNumber/> Cameras On
 
     We recommend that all participants have their cameras on. This helps to build trust and rapport. It also helps to keep everyone engaged and focused. This also lets us gage how everyone is understanding the material. If you are having trouble understanding something, please ask questions.
+
   </Step>
 
   <Step>
     ### <StepNumber/> Ask Questions
 
     We encourage you to ask questions. We want to make sure that everyone understands the material. We also want to make sure that we are providing the right level of detail. Our meetings are intended to be interactive and encourage conversation. Please feel free to interject at any time if you have a question or a comment to add to the discussion.
+
   </Step>
 </Steps>
 
@@ -187,4 +213,3 @@ Both the [Shared Customer Workshops](#shared-customer-workshop) and [Community O
 ### Documentation
 
 You can always find how-to guides, design decisions, and other helpful pages at [docs.cloudposse.com](/)
-