feat(ui): add a progress bar in the onboarding doc (#587)

Author: swarna1101

docs/hackathon/0-onboarding.mdx

@@ -12,6 +12,7 @@ import useBaseUrl from "@docusaurus/useBaseUrl";
 import AccessGranted from "/static/img/verifiable-ai-hackathon/access-granted.png";
 import ChooseTemplate from "/static/img/verifiable-ai-hackathon/choose-template.png";
 import GeminiKey from "/static/img/verifiable-ai-hackathon/gemini-key.png";
+import OnboardingChecklist from "@site/src/components/hackathon/OnboardingChecklist";
 import CreateKey from "/static/img/verifiable-ai-hackathon/create-key.png";
 
 # Onboarding
@@ -20,6 +21,8 @@ Welcome to the **Verifiable AI Hackathon**! 🎉
 
 This guide walks you through the **four-step setup** to ensure you have the necessary access and tools to start building.
 
+<OnboardingChecklist />
+
 ## Before You Begin
 
 - **Estimated Time:** ~15-20 minutes

docs/hackathon/1-cookbook.mdx

@@ -6,8 +6,26 @@ description: Cookbook commands for managing Confidential VMs.
 keywords: [flare, ai, confidential-compute, hackathon, google-cloud, onboarding]
 ---
 
+import ConfidentialVMBuilder from "@site/src/components/ConfidentialVMBuilder";
+
 Reference for commands you will encounter when interacting with Confidential VMs.
 
+## Confidential Space command builder
+
+Use this interactive builder to generate the exact Confidential Space VM deploy command you need.
+
+:::warning[Source your .env file]
+
+Before running the following gcloud command don't forget to source your `.env` file:
+
+```bash
+source .env
+```
+
+:::
+
+<ConfidentialVMBuilder />
+
 ## Restarting VMs
 
 During testing, you often need to restart a VM to pull updated docker images.
@@ -46,9 +64,9 @@ You can also view logs in the Google Cloud Console by navigating to the Logging
 
 :::
 
-## Deploying AMD SEV Confidential VMs
+## Deploying on AMD SEV
 
-This command creates a Confidential Computing VM instance using AMD SEV ([Secure Encrypted Virtualization](https://www.amd.com/content/dam/amd/en/documents/epyc-business-docs/white-papers/memory-encryption-white-paper.pdf)), with a specific image, network configuration, and security settings.
+This command creates a Confidential Space VM instance using AMD SEV ([Secure Encrypted Virtualization](https://www.amd.com/content/dam/amd/en/documents/epyc-business-docs/white-papers/memory-encryption-white-paper.pdf)), with a specific image, network configuration, and security settings.
 The metadata section is critical for configuring the Trusted Execution Environment (TEE).
 The command is broken down in the following sections.
 
@@ -188,10 +206,10 @@ gcloud compute instances create $INSTANCE_NAME \
 - `--reservation-affinity=any`: If you have reservations, this allows the VM to use any available reservation.
 - `--confidential-compute-type=SEV`: Enables AMD SEV (Secure Encrypted Virtualization) Confidential Computing. This is the core flag that makes this instance a confidential VM.
 
-## Deploying Intel TDX Confidential VMs
+## Deploying on Intel TDX
 
-This command creates a Confidential Computing VM instance using Intel TDX ([Trust Domain Extensions](https://www.intel.com/content/www/us/en/developer/tools/trust-domain-extensions/documentation.html)), with a specific image, network configuration, and security settings.
-The command instructions differing from [Deploying AMD SEV Confidential VMs](#deploying-amd-sev-confidential-vms) are highlighted.
+This command creates a Confidential Space VM instance using Intel TDX ([Trust Domain Extensions](https://www.intel.com/content/www/us/en/developer/tools/trust-domain-extensions/documentation.html)), with a specific image, network configuration, and security settings.
+The command instructions differing from [Deploying AMD SEV Confidential VMs](#deploying-on-amd-sev) are highlighted.
 
 ```bash
 gcloud compute instances create $INSTANCE_NAME \