diff --git a/docs/configuration/clusters.mdx b/docs/configuration/clusters.mdx
index c7c6819..1ca6576 100644
--- a/docs/configuration/clusters.mdx
+++ b/docs/configuration/clusters.mdx
@@ -16,7 +16,7 @@ description: "Manage your Kubernetes clusters with Qovery"
 To create a new cluster:
 
 1. Open the [Qovery Console](https://console.qovery.com)
-2. Navigate to the **Cluster** page in the left menu
+2. Navigate to the **Clusters** tab
 3. Click **Add Cluster**
 4. Follow the provider-specific guide for your cloud platform:
 
@@ -197,13 +197,11 @@ Resumes a stopped cluster and redeploys all services.
 Permanently removes your cluster. You have three deletion options:
 
 1. **Default (Recommended)**: Complete cleanup
-
    - Deletes all Qovery-managed resources
    - Removes cloud provider infrastructure
    - No residual costs
 
 2. **Delete on cloud provider and Qovery configuration**: Manual database handling
-
    - Deletes cluster from cloud provider
    - Removes Qovery configuration
    - Requires manual database cleanup
@@ -306,6 +304,7 @@ To use your own custom domain with wildcard TLS certificates, Qovery supports **
     - Your Cloudflare account email
 
     The Qovery team will configure the integration for you.
+
   </Step>
 
   <Step title="Verify DNS">
@@ -365,6 +364,7 @@ To use your own custom domain with wildcard TLS certificates, Qovery supports **
     <Info>
     The Hosted Zone ID is optional. If not provided, Qovery will auto-detect it.
     </Info>
+
   </Step>
 
   <Step title="Contact Qovery Support">
@@ -377,6 +377,7 @@ To use your own custom domain with wildcard TLS certificates, Qovery supports **
     - Your Hosted Zone ID (optional)
 
     The Qovery team will configure the integration for you.
+
   </Step>
 
   <Step title="Verify DNS">
@@ -385,7 +386,8 @@ To use your own custom domain with wildcard TLS certificates, Qovery supports **
 </Steps>
 
 <Info>
-This feature is currently in **Beta**. Both **Cloudflare** and **AWS Route53** are supported. Additional DNS providers will be added in future releases.
+  This feature is currently in **Beta**. Both **Cloudflare** and **AWS Route53**
+  are supported. Additional DNS providers will be added in future releases.
 </Info>
 
 ## AWS Account Cleanup
@@ -399,11 +401,10 @@ If cluster deletion fails or leaves resources behind, you can manually clean up
     Navigate to the [AWS Resource Groups & Tag Editor](https://console.aws.amazon.com/resource-groups/tag-editor)
   </Step>
 
-  <Step title="Search for Qovery Resources">
-    1. Select **All supported resource types**
-    2. Add tag filter: `ClusterId` or `QoveryCluster`
-    3. Search for resources
-  </Step>
+<Step title="Search for Qovery Resources">
+  1. Select **All supported resource types** 2. Add tag filter: `ClusterId` or
+  `QoveryCluster` 3. Search for resources
+</Step>
 
   <Step title="Review and Delete">
     1. Review the list of tagged resources
diff --git a/docs/configuration/connect-to-cluster.mdx b/docs/configuration/connect-to-cluster.mdx
index f01647d..1b2c118 100644
--- a/docs/configuration/connect-to-cluster.mdx
+++ b/docs/configuration/connect-to-cluster.mdx
@@ -12,7 +12,8 @@ Connecting to your Kubernetes cluster with kubectl gives you direct access to ma
 3. **AWS CLI Method (Traditional)** - Manual setup for advanced users who need full control
 
 <Warning>
-Any manual operations on your cluster could conflict with Qovery's management. Use with caution and understand the implications of direct cluster access.
+  Any manual operations on your cluster could conflict with Qovery's management.
+  Use with caution and understand the implications of direct cluster access.
 </Warning>
 
 ## Method 1: Using Qovery Console Shell (Easiest)
@@ -27,11 +28,12 @@ The Qovery Console provides the fastest way to access your cluster - directly fr
   </Step>
 
   <Step title="Open Shell">
-    In the cluster toolbar, click on the shell icon (">") to open an embedded terminal.
+    Click on the Cloud shell tab to open an embedded terminal.
 
     <Frame>
       <img src="/images/configuration/clusters/cluster-shell-access.png" alt="Cluster Shell Access" />
     </Frame>
+
   </Step>
 
   <Step title="Use k9s or kubectl">
@@ -46,19 +48,20 @@ The Qovery Console provides the fastest way to access your cluster - directly fr
     kubectl get pods -A
     kubectl get namespaces
     ```
+
   </Step>
 </Steps>
 
 <Info>
-The Console Shell comes pre-configured with:
-- **k9s** - Interactive Kubernetes cluster management
-- **kubectl** - Full kubectl access
-- Cluster credentials automatically configured
-- No local installation required
+  The Console Shell comes pre-configured with: - **k9s** - Interactive
+  Kubernetes cluster management - **kubectl** - Full kubectl access - Cluster
+  credentials automatically configured - No local installation required
 </Info>
 
 <Tip>
-This method is perfect for quick debugging, viewing resources, or when you don't have local tools installed. The shell runs directly in your cluster with full access.
+  This method is perfect for quick debugging, viewing resources, or when you
+  don't have local tools installed. The shell runs directly in your cluster with
+  full access.
 </Tip>
 
 ## Method 2: Using Qovery CLI (Recommended for Local Development)
@@ -66,6 +69,7 @@ This method is perfect for quick debugging, viewing resources, or when you don't
 ### Prerequisites
 
 Before using Qovery CLI, ensure you have:
+
 - [Qovery CLI installed](/cli/overview)
 - An existing cluster managed by Qovery
 - kubectl installed ([installation guide](https://kubernetes.io/docs/tasks/tools/))
@@ -112,6 +116,7 @@ This method downloads the kubeconfig file to your local machine for full kubectl
     ```bash
     qovery auth --headless
     ```
+
   </Step>
 
   <Step title="List Available Clusters">
@@ -127,6 +132,7 @@ This method downloads the kubeconfig file to your local machine for full kubectl
     prod-us-east   us-east-1     AWS       Running   1.28
     staging-eu     eu-west-1     AWS       Running   1.27
     ```
+
   </Step>
 
   <Step title="Download Kubeconfig">
@@ -140,6 +146,7 @@ This method downloads the kubeconfig file to your local machine for full kubectl
     - Generate a kubeconfig file
     - Save it to your current directory
     - Display the file location
+
   </Step>
 
   <Step title="Configure kubectl">
@@ -160,6 +167,7 @@ This method downloads the kubeconfig file to your local machine for full kubectl
       kubectl config view --flatten > ~/.kube/config.new
     mv ~/.kube/config.new ~/.kube/config
     ```
+
   </Step>
 
   <Step title="Verify Connection">
@@ -170,6 +178,7 @@ This method downloads the kubeconfig file to your local machine for full kubectl
     ```
 
     You should see your cluster nodes listed.
+
   </Step>
 </Steps>
 
@@ -191,6 +200,7 @@ For quick troubleshooting without local setup, use the debug pod feature:
     - kubectl pre-configured
     - Common debugging tools
     - Network access to cluster services
+
   </Step>
 
   <Step title="Run kubectl Commands">
@@ -206,6 +216,7 @@ For quick troubleshooting without local setup, use the debug pod feature:
     # Check service endpoints
     kubectl get endpoints -n <namespace>
     ```
+
   </Step>
 
   <Step title="Exit Debug Pod">
@@ -214,11 +225,14 @@ For quick troubleshooting without local setup, use the debug pod feature:
     ```bash
     exit
     ```
+
   </Step>
 </Steps>
 
 <Tip>
-The debug pod method is perfect for quick checks and doesn't require any local configuration. It's ideal for debugging connectivity issues or testing from within the cluster.
+  The debug pod method is perfect for quick checks and doesn't require any local
+  configuration. It's ideal for debugging connectivity issues or testing from
+  within the cluster.
 </Tip>
 
 ## Method 3: Using AWS CLI (Advanced)
@@ -226,12 +240,14 @@ The debug pod method is perfect for quick checks and doesn't require any local c
 For users who need full control or want to use AWS IAM directly, you can configure kubectl using the AWS CLI. This method requires more manual setup but provides flexibility.
 
 <Info>
-This method is recommended for advanced users who need custom IAM configurations or want to integrate with existing AWS tooling.
+  This method is recommended for advanced users who need custom IAM
+  configurations or want to integrate with existing AWS tooling.
 </Info>
 
 ### Prerequisites
 
 Before using AWS CLI method, ensure you have:
+
 - [AWS CLI installed](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html)
 - [kubectl installed](https://kubernetes.io/docs/tasks/tools/)
 - [Qovery CLI installed](/cli/overview)
@@ -255,6 +271,7 @@ Before using AWS CLI method, ensure you have:
     1. Go to your Qovery cluster settings
     2. Navigate to Advanced Settings
     3. Enable SSO authentication for the cluster
+
   </Step>
 
   <Step title="Configure AWS CLI Credentials">
@@ -269,6 +286,7 @@ Before using AWS CLI method, ensure you have:
     - AWS Secret Access Key
     - Default region (match your cluster region)
     - Default output format (json recommended)
+
   </Step>
 
   <Step title="Verify AWS Access">
@@ -279,6 +297,7 @@ Before using AWS CLI method, ensure you have:
     ```
 
     This should return your IAM user information.
+
   </Step>
 </Steps>
 
@@ -292,6 +311,7 @@ Before using AWS CLI method, ensure you have:
     qovery cluster list
     qovery cluster kubeconfig --cluster-id <cluster-id>
     ```
+
   </Step>
 
   <Step title="Set kubectl Context">
@@ -306,6 +326,7 @@ Before using AWS CLI method, ensure you have:
     ```bash
     kubectl config current-context
     ```
+
   </Step>
 
   <Step title="Test Cluster Access">
@@ -316,6 +337,7 @@ Before using AWS CLI method, ensure you have:
     ```
 
     If successful, you'll see the list of nodes in your cluster.
+
   </Step>
 </Steps>
 
@@ -330,7 +352,9 @@ aws eks update-kubeconfig \
 ```
 
 <Warning>
-When using AWS CLI to generate kubeconfig, ensure the cluster name matches exactly as it appears in AWS EKS. Qovery-managed clusters follow a specific naming convention.
+  When using AWS CLI to generate kubeconfig, ensure the cluster name matches
+  exactly as it appears in AWS EKS. Qovery-managed clusters follow a specific
+  naming convention.
 </Warning>
 
 ## Working with Applications
@@ -348,6 +372,7 @@ Qovery creates a unique namespace for each environment:
     ```
 
     Qovery namespaces start with 'z' followed by a unique identifier.
+
   </Step>
 
   <Step title="Identify Your Namespace">
@@ -358,6 +383,7 @@ Qovery creates a unique namespace for each environment:
     ```
 
     Look for a namespace like: `z<environment-id>`
+
   </Step>
 
   <Step title="Set Default Namespace">
@@ -366,6 +392,7 @@ Qovery creates a unique namespace for each environment:
     ```bash
     kubectl config set-context --current --namespace=z<environment-id>
     ```
+
   </Step>
 </Steps>
 
@@ -436,7 +463,9 @@ kubectl port-forward --namespace <namespace> service/<service-name> 8080:80
 ```
 
 <Info>
-The Qovery CLI also provides a `qovery port-forward` command that can be easier to use. See [qovery port-forward](/cli/commands/port-forward) for details.
+  The Qovery CLI also provides a `qovery port-forward` command that can be
+  easier to use. See [qovery port-forward](/cli/commands/port-forward) for
+  details.
 </Info>
 
 ### Describe Resources
@@ -497,6 +526,7 @@ kubectl get events --namespace <namespace> --sort-by='.lastTimestamp'
     - Check your kubeconfig path: `echo $KUBECONFIG`
     - Ensure AWS credentials are valid: `aws sts get-caller-identity`
     - Regenerate kubeconfig: `qovery cluster kubeconfig --cluster-id <cluster-id>`
+
   </Accordion>
 
   <Accordion title="Authentication Failed">
@@ -507,6 +537,7 @@ kubectl get events --namespace <namespace> --sort-by='.lastTimestamp'
     - Verify IAM permissions for AWS CLI method
     - Check if your IAM user is in the cluster admin group
     - Ensure SSO is enabled if using SSO authentication
+
   </Accordion>
 
   <Accordion title="Forbidden Access">
@@ -517,6 +548,7 @@ kubectl get events --namespace <namespace> --sort-by='.lastTimestamp'
     - Check RBAC roles: `kubectl get rolebindings --namespace <namespace>`
     - Ensure you're using the correct namespace
     - Contact your organization admin for access
+
   </Accordion>
 
   <Accordion title="Namespace Not Found">
@@ -527,6 +559,7 @@ kubectl get events --namespace <namespace> --sort-by='.lastTimestamp'
     - Verify environment ID from Qovery Console
     - Ensure environment is deployed
     - Check if namespace starts with 'z' prefix
+
   </Accordion>
 </AccordionGroup>
 
@@ -557,7 +590,8 @@ kubectl run -ti --rm debug --image=busybox --restart=Never -- nslookup kubernete
 ## Security Best Practices
 
 <Warning>
-Direct cluster access bypasses Qovery's safety mechanisms. Follow these best practices to avoid issues.
+  Direct cluster access bypasses Qovery's safety mechanisms. Follow these best
+  practices to avoid issues.
 </Warning>
 
 ### Do's and Don'ts
@@ -583,19 +617,15 @@ Direct cluster access bypasses Qovery's safety mechanisms. Follow these best pra
 ### Resource Management
 
 <Accordion title="Resources Safe to Modify">
-  - Application-specific ConfigMaps (not created by Qovery)
-  - Application-specific Secrets (not created by Qovery)
-  - Custom resources you deployed
-  - Debug pods you created
+  - Application-specific ConfigMaps (not created by Qovery) -
+  Application-specific Secrets (not created by Qovery) - Custom resources you
+  deployed - Debug pods you created
 </Accordion>
 
 <Accordion title="Resources to Avoid Modifying">
-  - Deployments managed by Qovery
-  - Services created by Qovery
-  - Ingress resources
-  - Qovery system namespaces (qovery, qovery-system, etc.)
-  - Network policies
-  - Resource quotas
+  - Deployments managed by Qovery - Services created by Qovery - Ingress
+  resources - Qovery system namespaces (qovery, qovery-system, etc.) - Network
+  policies - Resource quotas
 </Accordion>
 
 ### Access Control
@@ -609,18 +639,18 @@ Direct cluster access bypasses Qovery's safety mechanisms. Follow these best pra
 
 ## Comparison of Methods
 
-| Feature | Console Shell | Qovery CLI | AWS CLI |
-|---------|--------------|-----------|---------|
-| Setup Complexity | None (browser only) | Low (1-2 commands) | Medium (IAM setup required) |
-| Local Installation | Not required | Qovery CLI + kubectl | AWS CLI + kubectl |
-| Authentication | Automatic | Qovery account | IAM credentials |
-| Best For | Quick debugging | Local development | Advanced users, automation |
-| k9s Included | ✅ Yes | ❌ No | ❌ No |
-| kubectl Access | ✅ Yes | ✅ Yes | ✅ Yes |
-| Works Offline | ❌ No | ✅ Yes (once configured) | ✅ Yes (once configured) |
-| IAM Configuration | Not required | Not required | Required |
-| Learning Curve | Minimal | Minimal | Moderate |
-| Flexibility | Standard access | Standard access | Full AWS control |
+| Feature            | Console Shell       | Qovery CLI               | AWS CLI                     |
+| ------------------ | ------------------- | ------------------------ | --------------------------- |
+| Setup Complexity   | None (browser only) | Low (1-2 commands)       | Medium (IAM setup required) |
+| Local Installation | Not required        | Qovery CLI + kubectl     | AWS CLI + kubectl           |
+| Authentication     | Automatic           | Qovery account           | IAM credentials             |
+| Best For           | Quick debugging     | Local development        | Advanced users, automation  |
+| k9s Included       | ✅ Yes              | ❌ No                    | ❌ No                       |
+| kubectl Access     | ✅ Yes              | ✅ Yes                   | ✅ Yes                      |
+| Works Offline      | ❌ No               | ✅ Yes (once configured) | ✅ Yes (once configured)    |
+| IAM Configuration  | Not required        | Not required             | Required                    |
+| Learning Curve     | Minimal             | Minimal                  | Moderate                    |
+| Flexibility        | Standard access     | Standard access          | Full AWS control            |
 
 ## Next Steps
 
@@ -629,13 +659,17 @@ Direct cluster access bypasses Qovery's safety mechanisms. Follow these best pra
     Explore all Qovery CLI commands and features
   </Card>
 
-  <Card title="Cluster Management" icon="server" href="/configuration/clusters">
-    Learn more about managing clusters in Qovery
-  </Card>
-
-  <Card title="Deployment Logs" icon="scroll" href="/configuration/deployment/logs">
-    View deployment logs through Qovery Console
-  </Card>
+<Card title="Cluster Management" icon="server" href="/configuration/clusters">
+  Learn more about managing clusters in Qovery
+</Card>
+
+<Card
+  title="Deployment Logs"
+  icon="scroll"
+  href="/configuration/deployment/logs"
+>
+  View deployment logs through Qovery Console
+</Card>
 
   <Card title="Port Forwarding" icon="arrow-right-arrow-left" href="/cli/commands/port-forward">
     Use Qovery CLI port forwarding feature
diff --git a/docs/configuration/deployment/logs.mdx b/docs/configuration/deployment/logs.mdx
index d6c3d74..672edf5 100644
--- a/docs/configuration/deployment/logs.mdx
+++ b/docs/configuration/deployment/logs.mdx
@@ -19,7 +19,7 @@ You can access logs from three different entry points in the Qovery Console:
 ![Access Logs](/images/deployment/access_logs.png)
 
 1. **Scroll icon** next to the service: Access the service logs (runtime logs from your application)
-2. **Pipeline icon**: Access the deployment pipeline view showing all stages of the deployment
+2. **Last Deployment section**: Access the deployment pipeline view showing all stages of the deployment
 3. **Deployment status label**: Access the deployment logs for a specific deployment
 
 ## Pipeline View
@@ -33,7 +33,6 @@ The pipeline view provides a centralized overview of your deployment process, sh
 - Pre-check logs for validation processes
 - Direct access to specific deployment logs per service
 - Automatic filtering of services not involved in the deployment
-- **Hide skipped** toggle to show or hide [skipped services](/configuration/deployment/pipeline#skipped-services) in the pipeline view
 
 ## Deployment Logs
 
diff --git a/docs/configuration/deployment/statuses.mdx b/docs/configuration/deployment/statuses.mdx
index 831f767..378a2eb 100644
--- a/docs/configuration/deployment/statuses.mdx
+++ b/docs/configuration/deployment/statuses.mdx
@@ -7,6 +7,13 @@ Qovery allows you to track the status of your environments and services through
 
 ![Running and Deployment Statuses](/images/deployment/run_deployment_statuses.png)
 
+The image above shows the different status indicators available in the Qovery Console:
+
+1. **Environment running status** — A summary of the running status of all services in the environment
+2. **Environment last deployment status** — The result of the last deployment triggered on the environment
+3. **Service running status** — The running status of each individual service
+4. **Service last deployment status** — The result of the last deployment for each individual service
+
 ## Running Statuses
 
 The running status indicates if your application is running correctly or not.
@@ -42,8 +49,6 @@ You can view the status of individual Kubernetes pods by clicking on a service i
 - The status of each individual pod
 - Error details for pods that are failing
 
-![Job Completed Status](/images/deployment/clear_job_status.png)
-
 Clicking on a problematic pod will show you the specific reason why it's failing.
 
 ## Deployment Statuses
diff --git a/docs/configuration/integrations/iac/cloudformation.mdx b/docs/configuration/integrations/iac/cloudformation.mdx
index 634e0ac..71e3545 100644
--- a/docs/configuration/integrations/iac/cloudformation.mdx
+++ b/docs/configuration/integrations/iac/cloudformation.mdx
@@ -45,4 +45,3 @@ If your CloudFormation manifest/template generates an output, the output will be
 
 - [Lifecycle Job Documentation](/configuration/lifecycle-job)
 - [Lifecycle Job Examples Repository](https://github.com/Qovery/lifecycle-job-examples)
-- [Deployment Guide for Custom Resources](/integrations/iac/lifecycle-job-tutorial)
diff --git a/docs/configuration/integrations/iac/lifecycle-job-tutorial.mdx b/docs/configuration/integrations/iac/lifecycle-job-tutorial.mdx
deleted file mode 100644
index 2bd6a13..0000000
--- a/docs/configuration/integrations/iac/lifecycle-job-tutorial.mdx
+++ /dev/null
@@ -1,115 +0,0 @@
----
-title: "Using Lifecycle Jobs to Deploy Resources"
-description: "Tutorial on deploying any kind of resources using Lifecycle Jobs"
----
-
-## Overview
-
-The Lifecycle Job feature enables executing commands before or after environment deployment. Use cases include running infrastructure-as-code tools, creating cloud resources (SQS, SNS, Lambdas), deploying managed services, or seeding databases.
-
-## Execution Flow
-
-**Deployment sequence:**
-1. Qovery builds the Lifecycle Job and other services
-2. Qovery executes the Job's Start Event
-3. Job creates AWS RDS MySQL instance
-4. Job writes database credentials to `/qovery-output/qovery-output.json`
-5. Qovery injects credentials as environment variables
-6. Services access the database
-
-**Deletion sequence:**
-1. Qovery runs Job's Deleted Event
-2. Job destroys AWS RDS MySQL instance
-3. Qovery releases all resources
-
-## Prerequisites
-
-- Active Qovery account
-- Existing project and environment
-- S3 bucket for Terraform state backend
-
-## Step 1: Repository Setup
-
-Fork the [lifecycle-job-examples repository](https://github.com/Qovery/lifecycle-job-examples)
-
-Root application path: `/examples/aws-rds-with-terraform`
-
-## Step 2: Add Lifecycle Job
-
-![Add Lifecycle Job](/images/how-to-use-lifecycle-job/1.png)
-
-Configure the job with the following settings:
-
-![Configure name and repository](/images/how-to-use-lifecycle-job/2.png)
-
-**Select both Start and Deleted events:**
-
-![Select events](/images/how-to-use-lifecycle-job/3.png)
-
-**Event commands:**
-- Start Event command: `["-c","terraform apply -no-color -auto-approve && terraform output -json > /qovery-output/qovery-output.json"]`
-- Deleted Event command: `["-c","terraform destroy -no-color -auto-approve"]`
-
-**Timeout configuration:**
-
-![Set timeout](/images/how-to-use-lifecycle-job/4.png)
-
-Set timeout to 1800 seconds (30 minutes)
-
-**Resource allocation:**
-
-![Allocate resources](/images/how-to-use-lifecycle-job/5.png)
-
-- CPU: 0.5
-- RAM: 256 MB
-
-## Step 3: Environment Variables
-
-![Configure environment variables](/images/how-to-use-lifecycle-job/6.png)
-
-Required variables:
-- `TF_VAR_terraform_backend_bucket`
-- `TF_VAR_aws_region`
-- `TF_VAR_aws_access_key_id`
-- `TF_VAR_aws_secret_access_key`
-- `TF_VAR_qovery_environment_id`
-
-![Create without deployment](/images/how-to-use-lifecycle-job/7.png)
-
-## Step 4: Multi-Environment Support
-
-![MySQL RDS Variables](/images/how-to-use-lifecycle-job/8.png)
-
-![Search QOVERY_ENVIRONMENT_ID](/images/how-to-use-lifecycle-job/9.png)
-
-Create an alias linking `QOVERY_ENVIRONMENT_ID` to `TF_VAR_qovery_environment_id` at service scope level.
-
-![Create environment variable alias](/images/how-to-use-lifecycle-job/10.png)
-
-## Step 5: Deploy
-
-![Deploy Lifecycle Job](/images/how-to-use-lifecycle-job/11.png)
-
-![Access job logs](/images/how-to-use-lifecycle-job/12.png)
-
-![Terraform init logs](/images/how-to-use-lifecycle-job/13.png)
-
-![Terraform apply](/images/how-to-use-lifecycle-job/14.png)
-
-![Completed deployment](/images/how-to-use-lifecycle-job/15.png)
-
-## Output Credentials
-
-After deployment, Terraform output automatically generates `QOVERY_OUTPUT_**` environment variables containing database credentials for application use.
-
-![Generated output variables](/images/how-to-use-lifecycle-job/16.png)
-
-## FAQ
-
-**Environment Deletion:** Deleted Event executes `terraform destroy` automatically.
-
-**Application Deployment:** Lifecycle Jobs can deploy applications but official Qovery methods are recommended.
-
-**Environment Cloning:** Cloned environments receive unique `QOVERY_ENVIRONMENT_ID` values; S3 state management preserves existing resources.
-
-**Post-Deployment Modifications:** Redeploying updated Jobs uses existing S3 state; resource modifications depend on configuration file changes.
diff --git a/docs/configuration/integrations/iac/terraform.mdx b/docs/configuration/integrations/iac/terraform.mdx
index 7344224..db7eecc 100644
--- a/docs/configuration/integrations/iac/terraform.mdx
+++ b/docs/configuration/integrations/iac/terraform.mdx
@@ -43,4 +43,3 @@ Terraform outputs are automatically captured and injected as environment variabl
 
 - [Lifecycle Job Documentation](/configuration/lifecycle-job)
 - [Lifecycle Job Examples Repository](https://github.com/Qovery/lifecycle-job-examples)
-- [Deployment Guide for Custom Resources](/integrations/iac/lifecycle-job-tutorial)
diff --git a/docs/configuration/integrations/kubernetes/aks/managed.mdx b/docs/configuration/integrations/kubernetes/aks/managed.mdx
index 7fa6bd6..3b4378a 100644
--- a/docs/configuration/integrations/kubernetes/aks/managed.mdx
+++ b/docs/configuration/integrations/kubernetes/aks/managed.mdx
@@ -3,11 +3,13 @@ title: "Qovery-Managed AKS"
 description: "Learn how to configure your AKS Kubernetes clusters on Qovery"
 ---
 
+import AzureCredentials from "/snippets/azure-credentials.mdx";
+
 ## Creating an Azure AKS Cluster
 
 ### Connect Your Azure Account
 
-<Snippet file="azure-credentials.mdx" />
+<AzureCredentials />
 
 ### Create the Cluster
 
@@ -44,11 +46,11 @@ To manage the settings of an existing cluster:
   </Step>
 
   <Step title="Navigate to Cluster Page">
-    On the left menu bar, click on the Cluster page.
+    On your organization overview, go to the **Clusters** tab.
   </Step>
 
   <Step title="Access Cluster Settings">
-    To access your cluster settings, click on the wheel button.
+    Click on your cluster card and go to the **Settings** tab.
   </Step>
 </Steps>
 
diff --git a/docs/configuration/integrations/kubernetes/eks/managed.mdx b/docs/configuration/integrations/kubernetes/eks/managed.mdx
index 788de7a..ad2bba6 100644
--- a/docs/configuration/integrations/kubernetes/eks/managed.mdx
+++ b/docs/configuration/integrations/kubernetes/eks/managed.mdx
@@ -3,10 +3,13 @@ title: "AWS EKS"
 description: "Learn how to configure your AWS Kubernetes clusters on Qovery"
 ---
 
+import AwsCredentials from "/snippets/aws-credentials.mdx";
+
 <Info>
 **Default Autoscaling Mode**
 
 All AWS EKS clusters on Qovery now use Karpenter for autoscaling, which automatically launches the right compute resources to handle your cluster's applications.
+
 </Info>
 
 Karpenter automatically launches just the right compute resources to handle your cluster's applications. It is designed to let you take full advantage of the cloud with fast and simple compute provisioning for Kubernetes clusters.
@@ -14,6 +17,10 @@ You can read our [blog post](https://www.qovery.com/blog/save-up-to-60-on-aws-co
 
 ## Creating an AWS EKS Cluster
 
+### Connect Your AWS Account
+
+<AwsCredentials />
+
 ### Create the Cluster
 
 <Steps>
@@ -26,7 +33,7 @@ You can read our [blog post](https://www.qovery.com/blog/save-up-to-60-on-aws-co
     * **Description**: enter a description to identify better your cluster.
     * **Production cluster**: select this option if your cluster will be used for production. Note: Karpenter is currently only available for non-production clusters.
     * **Region**: select the geographical area in which you want your cluster to be hosted.
-    * **Credentials**: select one of the existing cloud provider credentials or [create new credentials](/getting-started/installation/aws#connect-your-aws-account).
+    * **Credentials**: select one of the existing cloud provider credentials or create new credentials using the section above.
 
     To confirm, click `Next`.
 
@@ -35,7 +42,6 @@ You can read our [blog post](https://www.qovery.com/blog/save-up-to-60-on-aws-co
   <Step title="Set Resources">
     In the `Set Resources` window, select:
 
-    * **Karpenter**: Toggle the switch to enable Karpenter on your AWS EKS cluster
     * **Node disk size (GB)**: Specify the disk capacity allocated per worker node, determining the amount of data each node can store. The minimum value is 20GB.
     * **Instance types scopes**: By editing it, you can apply different filters to the node architectures, categories, families, and sizes. On the right, you can view all the instance types that match the applied filters. This means Karpenter will be able to spawn nodes on any of the listed instance types.
       * **Architectures**: by default both `AMD64` and `ARM64` architectures are selected.
@@ -59,10 +65,10 @@ You can read our [blog post](https://www.qovery.com/blog/save-up-to-60-on-aws-co
 
   </Step>
 
-  <Step title="Configure Features">
-    In the `Features` step, select the features you want to enable on your cluster.
+  <Step title="Configure Network">
+    In the `Network` step, select the network mode you want to enable on your cluster.
 
-    If you want to manage the network layer of your cluster by yourself, you can switch VPC mode to `Deploy on my existing VPC` to use your own VPC instead of the one provided by Qovery.
+    If you want to manage the network layer of your cluster by yourself, you can switch Network mode to `Self-managed` to use your own VPC instead of the one provided by Qovery.
 
     <Warning>
     These options can only be configured during cluster creation and cannot be modified later.
@@ -159,51 +165,17 @@ You can read our [blog post](https://www.qovery.com/blog/save-up-to-60-on-aws-co
 
   </Step>
 
-  <Step title="Configure Additional Subnets (Existing VPC Only)">
-    If you have configured an existing vpc for your cluster, you'll need to indicate some additional subnets dedicated to fargate:
-    * those subnets must be **private**
-    * they must all have access to internet through a NAT gateway
-  </Step>
+<Step title="Configure Additional Subnets (Existing VPC Only)">
+  If you have configured an existing vpc for your cluster, you'll need to
+  indicate some additional subnets dedicated to fargate: * those subnets must be
+  **private** * they must all have access to internet through a NAT gateway
+</Step>
 
   <Step title="Update Daemonsets">
     If you have deployed some daemonsets, you must update their definitions to enable them to run on every node of the future nodepools (stable, default, and cronjob if enabled). Everything is explained in [our guide](/getting-started/guides/advanced-tutorials/deploy-daemonset-karpenter)
   </Step>
 </Steps>
 
-### Enable Karpenter
-
-You can easily activate Karpenter on your non-production existing cluster by following this process:
-
-<Steps>
-  <Step title="Open Qovery Console">
-    Open your [Qovery Console](https://console.qovery.com).
-  </Step>
-
-  <Step title="Navigate to Cluster Page">
-    On the left menu bar, click on the Cluster page.
-  </Step>
-
-  <Step title="Access Cluster Settings">
-    To access your cluster settings, click on the wheel button.
-  </Step>
-
-  <Step title="Activate Karpenter">
-    Access to `Resources` section and switch on the toggle `Activate Karpenter`
-  </Step>
-
-  <Step title="Update Your Cluster">
-    Update your cluster by selecting the action `Update` from the drop-down menu.
-  </Step>
-
-  <Step title="Verify and Add Instance Types">
-    Once the update is complete, your cluster will be running on Karpenter. By default, only the instance types selected when you created your AWS cluster with the auto-scaler will be configured. You can add additional instance types by editing the instance types in the resources section.
-  </Step>
-
-  <Step title="Redeploy Environments">
-    Please redeploy all your environments of your cluster: this will automatically update your services configuration to run them on the appropriate nodepool.
-  </Step>
-</Steps>
-
 ## Managing your Cluster Settings
 
 To manage the settings of an existing cluster:
@@ -213,12 +185,10 @@ To manage the settings of an existing cluster:
     Open your [Qovery Console](https://console.qovery.com).
   </Step>
 
-  <Step title="Navigate to Cluster Page">
-    On the left menu bar, click on the Cluster page.
-  </Step>
+<Step title="Navigate to Cluster Page">Click on the Clusters tab.</Step>
 
   <Step title="Access Cluster Settings">
-    To access your cluster settings, click on the wheel button.
+    To access your cluster settings, click on the settings tab.
   </Step>
 </Steps>
 
@@ -281,13 +251,12 @@ The credentials configured on this registry are the one used to create the clust
 
 Check [this link](/configuration/deployment/image-mirroring) for more information.
 
-### Features
-
-The `Features` tab in your cluster settings allows you to check if the [**Static IP**](#static-ip), [**Custom VPC subnet**](#custom-vpc-subnet), [**Deploy on existing VPC**](#use-your-existing-vpc) features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
-
 ### Network
 
-The `Network` tab in your cluster settings allows you to update your Qovery VPC route table so that you can perform VPC peering. For step-by-step guidelines on how to set up VPC peering, [see our dedicated tutorial](/configuration/integrations/aws/vpc-peering).
+The `Network` tab in your cluster settings allows you to:
+
+- check if the [**Static IP**](#static-ip), [**Custom VPC subnet**](#custom-vpc-subnet), [**Deploy on existing VPC**](#use-your-existing-vpc) features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
+- Update your Qovery VPC route table so that you can perform VPC peering. For step-by-step guidelines on how to set up VPC peering, [see our dedicated tutorial](/configuration/integrations/aws/vpc-peering).
 
 ## Defining cluster node constraints to run your Services
 
diff --git a/docs/configuration/integrations/kubernetes/gke/managed.mdx b/docs/configuration/integrations/kubernetes/gke/managed.mdx
index f6b5caa..5b3ba56 100644
--- a/docs/configuration/integrations/kubernetes/gke/managed.mdx
+++ b/docs/configuration/integrations/kubernetes/gke/managed.mdx
@@ -3,11 +3,13 @@ title: "Qovery-Managed GKE"
 description: "Learn how to configure your GCP Kubernetes clusters on Qovery"
 ---
 
+import GcpCredentials from "/snippets/gcp-credentials.mdx";
+
 ## Creating a GCP GKE Cluster
 
 ### Connect Your GCP Account
 
-<Snippet file="gcp-credentials.mdx" />
+<GcpCredentials />
 
 ### Create the Cluster
 
@@ -24,10 +26,11 @@ description: "Learn how to configure your GCP Kubernetes clusters on Qovery"
     * **Credentials**: select one of the existing cloud provider credentials or [create new credentials](/getting-started/installation/gcp#connect-your-gcp-account).
 
     To confirm, click `Next`.
+
   </Step>
 
-  <Step title="Configure Features">
-    In the `Features` step, select the features you want to enable on your cluster.
+  <Step title="Configure Network">
+    In the `Network` step, select the network mode you want to enable on your cluster.
 
     If you want to manage the network layer of your cluster by yourself, you can switch VPC mode to `Deploy on my existing VPC` to use your own VPC instead of the one provided by Qovery.
 
@@ -81,6 +84,7 @@ description: "Learn how to configure your GCP Kubernetes clusters on Qovery"
         </Info>
       </Tab>
     </Tabs>
+
   </Step>
 
   <Step title="Create and Install">
@@ -91,6 +95,7 @@ description: "Learn how to configure your GCP Kubernetes clusters on Qovery"
     Your cluster is now displayed in your organization settings, featuring the `Installing...` status (orange status). Once your cluster is properly installed, its status turns to green and you will be able to deploy your applications on it.
 
     You can follow the execution of the action via the cluster status and/or by accessing the [Cluster Logs](/configuration/clusters#logs)
+
   </Step>
 </Steps>
 
@@ -103,12 +108,12 @@ To manage the settings of an existing cluster:
     Open your [Qovery Console](https://console.qovery.com).
   </Step>
 
-  <Step title="Navigate to Cluster Page">
-    On the left menu bar, click on the Cluster page.
-  </Step>
+<Step title="Navigate to Cluster Page">
+  On your organization overview, go on the Clusters page.
+</Step>
 
   <Step title="Access Cluster Settings">
-    To access your cluster settings, click on the wheel button.
+    To access your cluster settings, click on your cluster card and then go on Settings tab.
   </Step>
 </Steps>
 
@@ -118,17 +123,18 @@ Below you can find a description of each section
 
 The `General` tab allows you to define high-level information on your cluster:
 
-|Item|Description|
-|--------------|---------------------------|
-|Cluster Name|To edit the name of your cluster.|
-|Description|To enter or edit the description of your cluster.|
-|Production Cluster|To enter or edit the production flag of your cluster.|
+| Item               | Description                                           |
+| ------------------ | ----------------------------------------------------- |
+| Cluster Name       | To edit the name of your cluster.                     |
+| Description        | To enter or edit the description of your cluster.     |
+| Production Cluster | To enter or edit the production flag of your cluster. |
 
 ### Credentials
 
 Here you can manage here the cloud provider credentials associated with your cluster.
 
 If you need to change the credentials:
+
 - generate a new set of credentials on your cloud provider ([Procedure for GCP account](/installation/gcp#connect-gcp-account))
 - create the new credential on the Qovery by opening the drop-down and selecting "New Credentials"
 
@@ -143,6 +149,6 @@ The credentials configured on this registry are the one used to create the clust
 
 Check [this link](/configuration/deployment/image-mirroring) for more information.
 
-### Features
+### Network
 
-The `Features` tab in your cluster settings allows you to check if the [**Static IP**](#static-ip), [**Deploy on existing VPC**](#use-existing-vpc) features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
+The `Network` tab in your cluster settings allows you to check if the [**Static IP**](#static-ip), [**Deploy on existing VPC**](#use-existing-vpc) features are enabled on your cluster. The enabled features cannot be changed after the creation of the cluster.
diff --git a/docs/configuration/integrations/kubernetes/scaleway/managed.mdx b/docs/configuration/integrations/kubernetes/scaleway/managed.mdx
index 7868b23..6a6bc0a 100644
--- a/docs/configuration/integrations/kubernetes/scaleway/managed.mdx
+++ b/docs/configuration/integrations/kubernetes/scaleway/managed.mdx
@@ -3,11 +3,13 @@ title: "Qovery-Managed Scaleway Kapsule"
 description: "Learn how to configure your Scaleway Kubernetes clusters on Qovery"
 ---
 
+import ScalewayCredentials from "/snippets/scaleway-credentials.mdx";
+
 ## Creating a Scaleway Kapsule Cluster
 
 ### Connect Your Scaleway Account
 
-<Snippet file="scaleway-credentials.mdx" />
+<ScalewayCredentials />
 
 ### Create the Cluster
 
@@ -84,11 +86,11 @@ To manage the settings of an existing cluster:
   </Step>
 
   <Step title="Navigate to Cluster Page">
-    On the left menu bar, click on the Cluster page.
+    On your organization overview, go to the **Clusters** tab.
   </Step>
 
   <Step title="Access Cluster Settings">
-    To access your cluster settings, click on the wheel button.
+    Click on your cluster card and go to the **Settings** tab.
   </Step>
 </Steps>
 
diff --git a/docs/configuration/integrations/observability/kubecost.mdx b/docs/configuration/integrations/observability/kubecost.mdx
index 9184a3d..beb97c6 100644
--- a/docs/configuration/integrations/observability/kubecost.mdx
+++ b/docs/configuration/integrations/observability/kubecost.mdx
@@ -6,12 +6,11 @@ description: "Monitor and reduce Kubernetes spend with Kubecost"
 Kubecost provides real-time cost visibility and insights for your Kubernetes clusters. This guide shows you how to deploy Kubecost on your Qovery cluster to track and optimize your infrastructure spending.
 
 <Note>
-**Prerequisites**: You need a functioning Qovery cluster before starting this tutorial.
+  **Prerequisites**: You need a functioning Qovery cluster before starting this
+  tutorial.
 </Note>
 
-<Info>
-This tutorial takes approximately **3 minutes** to complete.
-</Info>
+<Info>This tutorial takes approximately **3 minutes** to complete.</Info>
 
 ## Step 1. Add the Kubecost Helm Repository
 
@@ -44,6 +43,7 @@ Create a new Helm service in your environment:
    - Enter your token value
 
 5. If using a token, add this in the **Values override** section:
+
    ```yaml
    kubecostToken: qovery.env.KUBECOST_TOKEN
    ```
@@ -54,26 +54,20 @@ Create a new Helm service in your environment:
 
 To access the Kubecost interface, you need to expose it publicly:
 
-1. Once deployed, check the **Deployment logs** to find the service name
-
-<img src="/images/kubecost/service-name.png" alt="Service name" />
-
-The service name will be something like: `helm-z325f0565-kubecost-cost-analyzer`
-
-2. Go to your Helm service **Settings** → **Port**
-3. Click **Add Port**
+1. Go to your Helm service **Settings** → **Port**
+2. Click **Add Port**
 
 <img src="/images/kubecost/add-port.png" alt="Add port" />
 
-4. Configure the port:
-   - **Service name**: The service name from step 1 (e.g., `helm-z325f0565-kubecost-cost-analyzer`)
+3. Configure the port:
+   - **Service name**: Select the service name (e.g., `helm-z325f0565-kubecost-cost-analyzer`)
    - **Service port**: `9090`
    - **Protocol**: `HTTP`
    - **Publicly exposed**: Enable
 
-5. Click **Create**
+4. Click **Create**
 
-6. After redeployment, you'll see a public link to access Kubecost
+5. After redeployment, you'll see a public link to access Kubecost
 
 <img src="/images/kubecost/link.png" alt="Link" />
 
@@ -90,13 +84,21 @@ To learn more about using Kubecost, check out their [Getting Started guide](http
     Learn more about Kubecost features
   </Card>
 
-  <Card title="Optimize" icon="gauge-high" href="/getting-started/guides/qovery-101/optimize">
-    Optimization strategies with Qovery
-  </Card>
-
-  <Card title="Qovery Observe" icon="chart-line" href="/configuration/integrations/observability/qovery-observe">
-    Built-in observability
-  </Card>
+<Card
+  title="Optimize"
+  icon="gauge-high"
+  href="/getting-started/guides/qovery-101/optimize"
+>
+  Optimization strategies with Qovery
+</Card>
+
+<Card
+  title="Qovery Observe"
+  icon="chart-line"
+  href="/configuration/integrations/observability/qovery-observe"
+>
+  Built-in observability
+</Card>
 
   <Card title="Datadog" icon="dog" href="/configuration/integrations/observability/datadog">
     Advanced monitoring with Datadog
diff --git a/docs/configuration/organization.mdx b/docs/configuration/organization.mdx
index 51ecd54..8b53a3c 100644
--- a/docs/configuration/organization.mdx
+++ b/docs/configuration/organization.mdx
@@ -15,9 +15,9 @@ To follow this section, you must have [created an account](https://console.qover
 
 When you sign up for Qovery, you will be asked to create your first organization and project. You will need to:
 
-1. Sign in through your Git provider (GitHub, GitLab, or Bitbucket)
-2. Create your first organization and project
-3. Select a plan: Free, Team, or Enterprise
+1. Sign in through your Git provider (GitHub, GitLab, or Bitbucket), Google or Microsoft
+2. Create your first organization
+3. You will be on Team plan by default during your trial
 
 For more information on available plans, visit the [pricing page](https://www.qovery.com/pricing).
 
@@ -27,15 +27,16 @@ You can create multiple organizations to separate concerns. To create a new orga
 
 <Steps>
   <Step title="Access Organization Menu">
-    Click on your profile icon button on the left navbar
+    Click on your current organization dropdown meny in the header
   </Step>
 
   <Step title="Create New Organization">
-    Click the `+` button in the top right corner of the dropdown menu
+    Click the `+` button in the bottom of the dropdown menu
 
     <Frame>
       <img src="/images/configuration/organization/create_organization_after_signing_up.png" alt="Create organization after signing up" />
     </Frame>
+
   </Step>
 
   <Step title="Configure Organization">
@@ -47,18 +48,22 @@ You can create multiple organizations to separate concerns. To create a new orga
 
 If you have access to multiple organizations, you can switch between them:
 
-1. Locate the organization dropdown in the bottom left of the navbar
+1. Locate the organization dropdown in the header
 2. Click on the dropdown to see all available organizations
 3. Select the organization you want to switch to
 
 <Frame>
-  <img src="/images/configuration/organization/change_organization.png" alt="Change organization" />
+  <img
+    src="/images/configuration/organization/change_organization.png"
+    alt="Change organization"
+  />
 </Frame>
 
 ## Delete an Organization
 
 <Warning>
-Deleting an organization is **irreversible**. All data associated with the organization will be permanently deleted.
+  Deleting an organization is **irreversible**. All data associated with the
+  organization will be permanently deleted.
 </Warning>
 
 To delete an organization:
@@ -83,10 +88,13 @@ For pricing details, visit the [pricing page](https://www.qovery.com/pricing).
 
 ### Accessing Settings
 
-Click the **Wheel** button (⚙️) on the left navigation bar to access organization settings.
+Click the Settings tab while you are on your organization overview.
 
 <Frame>
-  <img src="/images/configuration/organization/access_settings.png" alt="Access organization settings" />
+  <img
+    src="/images/configuration/organization/access_settings.png"
+    alt="Access organization settings"
+  />
 </Frame>
 
 ### General Information
@@ -99,7 +107,8 @@ Configure basic organization details:
 - **Admin contact emails**: Enter one or multiple email addresses separated by commas
 
 <Info>
-Admin contact emails are used for communications about infrastructure outages, maintenance updates, and weekly and monthly usage reports.
+  Admin contact emails are used for communications about infrastructure outages,
+  maintenance updates, and weekly and monthly usage reports.
 </Info>
 
 Click **Update** to save your changes.
@@ -111,25 +120,45 @@ Click **Update** to save your changes.
     Generate and manage API tokens for programmatic access
   </Card>
 
-  <Card title="Cloud Credentials" icon="cloud" href="/configuration/organization/cloud-credentials">
-    Connect your cloud provider accounts (AWS, GCP, Azure, Scaleway)
-  </Card>
-
-  <Card title="Container Registry" icon="box" href="/configuration/organization/container-registry">
-    Configure access to your container registries
-  </Card>
-
-  <Card title="Git Repository Access" icon="code-branch" href="/configuration/organization/git-repository-access">
-    Manage Git provider integrations and repository access
-  </Card>
-
-  <Card title="Helm Repository" icon="/images/logos/helm-icon.svg" href="/configuration/organization/helm-repository">
-    Add and configure Helm chart repositories
-  </Card>
-
-  <Card title="Labels & Annotations" icon="tag" href="/configuration/organization/labels-annotations">
-    Define custom labels and annotations for your resources
-  </Card>
+<Card
+  title="Cloud Credentials"
+  icon="cloud"
+  href="/configuration/organization/cloud-credentials"
+>
+  Connect your cloud provider accounts (AWS, GCP, Azure, Scaleway)
+</Card>
+
+<Card
+  title="Container Registry"
+  icon="box"
+  href="/configuration/organization/container-registry"
+>
+  Configure access to your container registries
+</Card>
+
+<Card
+  title="Git Repository Access"
+  icon="code-branch"
+  href="/configuration/organization/git-repository-access"
+>
+  Manage Git provider integrations and repository access
+</Card>
+
+<Card
+  title="Helm Repository"
+  icon="/images/logos/helm-icon.svg"
+  href="/configuration/organization/helm-repository"
+>
+  Add and configure Helm chart repositories
+</Card>
+
+<Card
+  title="Labels & Annotations"
+  icon="tag"
+  href="/configuration/organization/labels-annotations"
+>
+  Define custom labels and annotations for your resources
+</Card>
 
   <Card title="Members & RBAC" icon="users" href="/configuration/organization/members-rbac">
     Manage team members and role-based access control
diff --git a/docs/configuration/organization/api-token.mdx b/docs/configuration/organization/api-token.mdx
index d9d4d2a..aaa4a6d 100644
--- a/docs/configuration/organization/api-token.mdx
+++ b/docs/configuration/organization/api-token.mdx
@@ -11,11 +11,12 @@ You can manage API tokens attached to your organization directly from the Qovery
 
 <Steps>
   <Step title="Open Organization Settings">
-    Click the **Wheel** button (⚙️) on the left navigation bar
+    Click the Settings tab while you are on your organization overview.
 
     <Frame>
       <img src="/images/configuration/organization/access_settings.png" alt="How to access your organization settings" />
     </Frame>
+
   </Step>
 
   <Step title="Navigate to Token API Section">
@@ -24,6 +25,7 @@ You can manage API tokens attached to your organization directly from the Qovery
     <Frame>
       <img src="/images/configuration/organization/token_api_access.png" alt="How to access your Token API section" />
     </Frame>
+
   </Step>
 </Steps>
 
@@ -34,12 +36,11 @@ You can manage API tokens attached to your organization directly from the Qovery
     Press the **Add** button to create a new API token
   </Step>
 
-  <Step title="Configure Token">
-    Provide the following information:
-    - **Name**: A descriptive name for the token
-    - **Description**: Purpose or usage details
-    - **Role**: Select a role managed via the [Qovery RBAC system](/configuration/organization/members-rbac)
-  </Step>
+<Step title="Configure Token">
+  Provide the following information: - **Name**: A descriptive name for the
+  token - **Description**: Purpose or usage details - **Role**: Select a role
+  managed via the [Qovery RBAC system](/configuration/organization/members-rbac)
+</Step>
 
   <Step title="Save Token">
     After creation, the token will be displayed once
@@ -47,7 +48,8 @@ You can manage API tokens attached to your organization directly from the Qovery
 </Steps>
 
 <Warning>
-**Important**: Make sure you safely store the token returned by the UI. You won't be able to retrieve it again (you will have to create a new one).
+  **Important**: Make sure you safely store the token returned by the UI. You
+  won't be able to retrieve it again (you will have to create a new one).
 </Warning>
 
 ## Delete a Token
@@ -61,5 +63,6 @@ To remove an API token:
 ## Edit a Token
 
 <Note>
-This functionality is not yet available. To modify a token, you'll need to delete the existing one and create a new token.
+  This functionality is not yet available. To modify a token, you'll need to
+  delete the existing one and create a new token.
 </Note>
diff --git a/docs/configuration/organization/git-repository-access.mdx b/docs/configuration/organization/git-repository-access.mdx
index d916c3d..47cc312 100644
--- a/docs/configuration/organization/git-repository-access.mdx
+++ b/docs/configuration/organization/git-repository-access.mdx
@@ -217,9 +217,7 @@ Once you've created a token in your Git provider, manage it in Qovery:
 
 <Steps>
   <Step title="Access Organization Settings">
-    Click the "Wheel" button (⚙️) on the left navigation bar
-
-    ![How to access your organization settings](/images/configuration/organization/access_settings.png)
+    Click on your organization name in the top left, then go to the **Settings** tab.
   </Step>
 
   <Step title="Navigate to Git Repository Access">
diff --git a/docs/configuration/organization/members-rbac.mdx b/docs/configuration/organization/members-rbac.mdx
index b571f51..ad82b94 100644
--- a/docs/configuration/organization/members-rbac.mdx
+++ b/docs/configuration/organization/members-rbac.mdx
@@ -11,11 +11,12 @@ You can invite someone to join your organization by email. Once they accept the
 
 <Steps>
   <Step title="Open Organization Settings">
-    Click the **Wheel** button (⚙️) on the left navigation bar
+    Click the Settings tab while you are on your organization overview.
 
     <Frame>
       <img src="/images/configuration/organization/access_settings.png" alt="How to access your organization settings" />
     </Frame>
+
   </Step>
 
   <Step title="Navigate to Members Section">
@@ -24,6 +25,7 @@ You can invite someone to join your organization by email. Once they accept the
     <Frame>
       <img src="/images/configuration/organization/members.png" alt="Qovery - List all members within an organization" />
     </Frame>
+
   </Step>
 </Steps>
 
@@ -37,7 +39,8 @@ You can invite someone to join your organization by email. Once they accept the
 The invited member will receive an email with instructions to join the organization.
 
 <Info>
-Changing the role of a member requires the user to logout/login to make the changes effective or wait a few minutes (max 1 hour).
+  Changing the role of a member requires the user to logout/login to make the
+  changes effective or wait a few minutes (max 1 hour).
 </Info>
 
 ## Default Roles
@@ -66,33 +69,29 @@ The user has read-only access to any section of the organization.
 
 ## Permissions Matrix
 
-| Action | Owner | Admin | DevOps | Billing Manager | Viewer |
-|--------|-------|-------|--------|-----------------|--------|
-| Read organization | yes | yes | yes | yes | yes |
-| Edit organization | yes | yes | no | no | no |
-| Delete organization | yes | no | no | no | no |
-| Manage billing | yes | yes | no | yes | no |
-| Manage members & roles | yes | yes | no | no | no |
-| Manage cluster & container registry | yes | yes | yes | no | no |
-| Manage organization setup | yes | yes | yes | no | no |
-| Read ANY project | yes | yes | yes | no | yes |
-| Edit/Delete ANY project | yes | yes | no | no | no |
-| Create project | yes | yes | no | no | no |
-| Read ANY environment | yes | yes | yes | no | yes |
-| Edit/Delete ANY environment or service | yes | yes | no | no | no |
-| Create environment or service | yes | yes | no | no | no |
-| Add/Edit/Delete environment variables and secrets | yes | yes | yes | no | no |
-| Deploy/Stop ANY environment or service | yes | yes | yes | no | no |
-| Connect via shell to ANY application | yes | yes | yes | no | no |
+| Action                                            | Owner | Admin | DevOps | Billing Manager | Viewer |
+| ------------------------------------------------- | ----- | ----- | ------ | --------------- | ------ |
+| Read organization                                 | yes   | yes   | yes    | yes             | yes    |
+| Edit organization                                 | yes   | yes   | no     | no              | no     |
+| Delete organization                               | yes   | no    | no     | no              | no     |
+| Manage billing                                    | yes   | yes   | no     | yes             | no     |
+| Manage members & roles                            | yes   | yes   | no     | no              | no     |
+| Manage cluster & container registry               | yes   | yes   | yes    | no              | no     |
+| Manage organization setup                         | yes   | yes   | yes    | no              | no     |
+| Read ANY project                                  | yes   | yes   | yes    | no              | yes    |
+| Edit/Delete ANY project                           | yes   | yes   | no     | no              | no     |
+| Create project                                    | yes   | yes   | no     | no              | no     |
+| Read ANY environment                              | yes   | yes   | yes    | no              | yes    |
+| Edit/Delete ANY environment or service            | yes   | yes   | no     | no              | no     |
+| Create environment or service                     | yes   | yes   | no     | no              | no     |
+| Add/Edit/Delete environment variables and secrets | yes   | yes   | yes    | no              | no     |
+| Deploy/Stop ANY environment or service            | yes   | yes   | yes    | no              | no     |
+| Connect via shell to ANY application              | yes   | yes   | yes    | no              | no     |
 
 ## Custom Roles
 
 You can create custom roles to fine-tune access control for your organization members. Custom roles allow you to define permissions at two levels: cluster level and project level.
 
-<Frame>
-  <img src="/images/configuration/organization/custom-role-creation.png" alt="Qovery - custom role creation" />
-</Frame>
-
 ### Cluster Level Permissions
 
 You can define the following permissions at the cluster level:
@@ -121,5 +120,6 @@ You can transfer ownership of the organization to another member. To do so:
 4. Confirm the transfer
 
 <Warning>
-Once ownership is transferred, you will no longer be the owner of the organization.
+  Once ownership is transferred, you will no longer be the owner of the
+  organization.
 </Warning>
diff --git a/docs/configuration/project.mdx b/docs/configuration/project.mdx
index f2aea5c..c71954b 100644
--- a/docs/configuration/project.mdx
+++ b/docs/configuration/project.mdx
@@ -14,12 +14,12 @@ A project allows you to group together a set of environments with the objective
 ## Create a New Project
 
 <Steps>
-  <Step title="Access Organization Settings">
-    Navigate to your organization settings
+  <Step title="Open Organization Overview">
+    Go to your organization overview in the [Qovery Console](https://console.qovery.com)
   </Step>
 
   <Step title="Create Project">
-    Click the **NEW** button in the projects section
+    Click the **New Project** button
 
     ![Project Creation](/images/configuration/project/project_creation.png)
   </Step>
diff --git a/docs/configuration/user-account.mdx b/docs/configuration/user-account.mdx
index 7094213..064a18f 100644
--- a/docs/configuration/user-account.mdx
+++ b/docs/configuration/user-account.mdx
@@ -9,13 +9,24 @@ Your user account settings allow you to manage your personal information and com
 
 To access your user account settings:
 
-1. Click on the **user icon** in the bottom left corner of the Qovery Console
-2. Select **Your profile** from the menu
+1. Click on the **user icon** in the top right corner of the Qovery Console
+2. Select **Profile settings** from the menu
 
 <Frame>
-  <img src="/images/configuration/user-account/access_user_account.png" alt="Access user account settings" />
+  <img
+    src="/images/configuration/user-account/access_user_account.png"
+    alt="Access user account settings"
+  />
 </Frame>
 
+## Theme
+
+Qovery supports **light**, **dark**, and **system** themes. To switch, click your avatar in the top-right corner and select your preferred option under **Theme**:
+
+- **System** — follows your OS/browser preference
+- **Light** — always use the light theme
+- **Dark** — always use the dark theme
+
 ## Account Information
 
 ### Name Fields
@@ -23,7 +34,8 @@ To access your user account settings:
 Your **first name** and **last name** are retrieved from your Git account and cannot be changed directly in Qovery.
 
 <Info>
-To update your name, you need to modify it in your Git provider (GitHub, GitLab, or Bitbucket) settings.
+  To update your name, you need to modify it in your Git provider (GitHub,
+  GitLab, or Bitbucket) settings.
 </Info>
 
 ### Account Email
@@ -31,7 +43,8 @@ To update your name, you need to modify it in your Git provider (GitHub, GitLab,
 Your **account email** is sourced from your Git credentials and cannot be modified within Qovery. This email is used for authentication and account identification.
 
 <Info>
-To change your account email, update it in your Git provider settings. The change will be reflected in Qovery after your next login.
+  To change your account email, update it in your Git provider settings. The
+  change will be reflected in Qovery after your next login.
 </Info>
 
 ### Communication Email
@@ -39,7 +52,9 @@ To change your account email, update it in your Git provider settings. The chang
 The **communication email** is a customizable field where you designate your preferred contact address for product updates, announcements, and important notifications.
 
 <Warning>
-Qovery uses your communication email to share important updates about the product. Please provide a valid, professional business email address that you check regularly.
+  Qovery uses your communication email to share important updates about the
+  product. Please provide a valid, professional business email address that you
+  check regularly.
 </Warning>
 
 **To update your communication email:**
@@ -50,6 +65,7 @@ Qovery uses your communication email to share important updates about the produc
 4. Click **Save** to update
 
 **Best practices:**
+
 - Use a business email address
 - Ensure the email is monitored regularly
 - Don't use temporary or disposable email addresses
@@ -60,13 +76,15 @@ Qovery uses your communication email to share important updates about the produc
 Your **timezone** is automatically synced with your browser settings to display dates and times correctly throughout the Qovery Console.
 
 This ensures that:
+
 - Deployment times are shown in your local timezone
 - Logs timestamps match your local time
 - Scheduled tasks display correctly
 - Activity history is accurately represented
 
 <Tip>
-The timezone is automatically detected and updated based on your browser. No manual configuration is needed.
+  The timezone is automatically detected and updated based on your browser. No
+  manual configuration is needed.
 </Tip>
 
 ## Why Account Settings Matter
@@ -74,6 +92,7 @@ The timezone is automatically detected and updated based on your browser. No man
 ### Stay Informed
 
 By maintaining accurate communication email settings, you'll receive:
+
 - **Product updates** - New features and improvements
 - **Service notifications** - Important system announcements
 - **Security alerts** - Account and security-related updates
@@ -82,6 +101,7 @@ By maintaining accurate communication email settings, you'll receive:
 ### Accurate Timestamps
 
 Proper timezone configuration ensures:
+
 - Deployment schedules align with your team's working hours
 - Log analysis uses correct timestamps
 - Collaboration across distributed teams is easier
@@ -97,6 +117,7 @@ Proper timezone configuration ensures:
     2. Update your profile name
     3. Log out and back into Qovery
     4. Your updated name will be reflected
+
   </Accordion>
 
   <Accordion title="How do I change my account email?">
@@ -106,6 +127,7 @@ Proper timezone configuration ensures:
     2. Ensure the new email is verified
     3. Log out and back into Qovery
     4. The new email will be used for your account
+
   </Accordion>
 
   <Accordion title="I'm not receiving communication emails">
@@ -116,6 +138,7 @@ Proper timezone configuration ensures:
     3. Ensure your email server isn't blocking emails from Qovery
     4. Add Qovery's email domain to your safe senders list
     5. Contact support if the issue persists
+
   </Accordion>
 
   <Accordion title="My timezone is incorrect">
@@ -127,6 +150,7 @@ Proper timezone configuration ensures:
     4. Refresh the Qovery Console
 
     The timezone should update automatically when you refresh the page.
+
   </Accordion>
 </AccordionGroup>
 
@@ -137,13 +161,21 @@ Proper timezone configuration ensures:
     Manage organization-level settings
   </Card>
 
-  <Card title="Members & RBAC" icon="users" href="/configuration/organization/members-rbac">
-    Manage team members and permissions
-  </Card>
-
-  <Card title="SSO Configuration" icon="shield" href="/configuration/organization/sso">
-    Set up single sign-on
-  </Card>
+<Card
+  title="Members & RBAC"
+  icon="users"
+  href="/configuration/organization/members-rbac"
+>
+  Manage team members and permissions
+</Card>
+
+<Card
+  title="SSO Configuration"
+  icon="shield"
+  href="/configuration/organization/sso"
+>
+  Set up single sign-on
+</Card>
 
   <Card title="API Tokens" icon="key" href="/configuration/organization/api-token">
     Generate API tokens
diff --git a/docs/copilot/mcp-server.mdx b/docs/copilot/mcp-server.mdx
index 8715e76..78321ed 100644
--- a/docs/copilot/mcp-server.mdx
+++ b/docs/copilot/mcp-server.mdx
@@ -31,7 +31,7 @@ The Qovery MCP Server lets you interact with your Qovery infrastructure from any
   </Step>
 
   <Step title="Navigate to Settings">
-    Click on the settings icon in your organization
+    Click on your organization name in the top left, then go to the **Settings** tab
   </Step>
 
   <Step title="Access API Tokens">
diff --git a/docs/docs.json b/docs/docs.json
index bb472ed..e6cdc3a 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -410,8 +410,7 @@
                 "pages": [
                   "configuration/integrations/iac/overview",
                   "configuration/integrations/iac/terraform",
-                  "configuration/integrations/iac/cloudformation",
-                  "configuration/integrations/iac/lifecycle-job-tutorial"
+                  "configuration/integrations/iac/cloudformation"
                 ]
               }
             ]
diff --git a/docs/getting-started/guides/advanced-tutorials/aws-iam-roles.mdx b/docs/getting-started/guides/advanced-tutorials/aws-iam-roles.mdx
index 7242bc0..f19e3f2 100644
--- a/docs/getting-started/guides/advanced-tutorials/aws-iam-roles.mdx
+++ b/docs/getting-started/guides/advanced-tutorials/aws-iam-roles.mdx
@@ -20,12 +20,14 @@ First, deploy a simple Debian container that will need S3 access:
 
 ### Get Kubernetes Namespace Name
 
-1. Access your container variables
-2. Locate `QOVERY_KUBERNETES_NAMESPACE_NAME`
-3. This value represents the namespace where the container runs
+1. Access your container variables and locate `QOVERY_KUBERNETES_NAMESPACE_NAME`
+2. This value represents the namespace where the container runs
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/debian_namespace.png" alt="Get Kubernetes namespace from container variables" />
+  <img
+    src="/images/aws-iam-assume-role/debian_namespace.png"
+    alt="Get Kubernetes namespace from container variables"
+  />
 </Frame>
 
 ---
@@ -38,7 +40,10 @@ First, deploy a simple Debian container that will need S3 access:
 2. Copy the OpenID Connect provider URL
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/eks_oidc.png" alt="EKS OIDC provider URL" />
+  <img
+    src="/images/aws-iam-assume-role/eks_oidc.png"
+    alt="EKS OIDC provider URL"
+  />
 </Frame>
 
 ### Create Identity Provider
@@ -51,7 +56,10 @@ First, deploy a simple Debian container that will need S3 access:
 6. Create the provider
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/oidc_connect.png" alt="Create OIDC identity provider" />
+  <img
+    src="/images/aws-iam-assume-role/oidc_connect.png"
+    alt="Create OIDC identity provider"
+  />
 </Frame>
 
 ---
@@ -65,7 +73,10 @@ First, deploy a simple Debian container that will need S3 access:
 3. Set **Identity provider** and **Audience** to `sts.amazonaws.com`
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/role_create_step1.png" alt="Create IAM role step 1" />
+  <img
+    src="/images/aws-iam-assume-role/role_create_step1.png"
+    alt="Create IAM role step 1"
+  />
 </Frame>
 
 ### Add Role Permissions
@@ -92,6 +103,7 @@ First, deploy a simple Debian container that will need S3 access:
     Replace placeholders:
     - `kubernetes_namespace`: Your Qovery environment namespace
     - `service_account_name`: Define a service account name (e.g., `my-s3-role`)
+
   </Tab>
 
   <Tab title="Cluster-Scoped Role">
@@ -107,11 +119,15 @@ First, deploy a simple Debian container that will need S3 access:
     ```
 
     This allows the service account to be used across all namespaces starting with `z`.
+
   </Tab>
 </Tabs>
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/role_trusted_entities_default.png" alt="Configure trusted entities" />
+  <img
+    src="/images/aws-iam-assume-role/role_trusted_entities_default.png"
+    alt="Configure trusted entities"
+  />
 </Frame>
 
 Save the **role ARN** for later use.
@@ -126,10 +142,10 @@ Save the **role ARN** for later use.
 apiVersion: v1
 kind: ServiceAccount
 metadata:
- name: $SERVICE_ACCOUNT_NAME
- namespace: $QOVERY_KUBERNETES_NAMESPACE_NAME
- annotations:
-   eks.amazonaws.com/role-arn: $AWS_ROLE_ARN
+  name: $SERVICE_ACCOUNT_NAME
+  namespace: $QOVERY_KUBERNETES_NAMESPACE_NAME
+  annotations:
+    eks.amazonaws.com/role-arn: $AWS_ROLE_ARN
 ```
 
 ### Deploy with Helm
@@ -137,25 +153,36 @@ metadata:
 We'll use a Helm chart to deploy the service account:
 
 **Chart Configuration:**
+
 - Helm source: Helm repository
 - Chart name: `qovery-sa-helper`
 - Version: `0.1.0`
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/create_sa.png" alt="Create service account" />
+  <img
+    src="/images/aws-iam-assume-role/create_sa.png"
+    alt="Create service account"
+  />
 </Frame>
 
 **Repository Details:**
+
 1. Repository name: `Qovery Service Account Helper`
 2. Kind: `HTTPS`
 3. URL: `https://qovery.github.io/create_service_account/`
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/helm_sa_1.png" alt="Helm service configuration" />
+  <img
+    src="/images/aws-iam-assume-role/helm_sa_1.png"
+    alt="Helm service configuration"
+  />
 </Frame>
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/set-helm-repo.png" alt="Set Helm repository" />
+  <img
+    src="/images/aws-iam-assume-role/set-helm-repo.png"
+    alt="Set Helm repository"
+  />
 </Frame>
 
 **Override Arguments:**
@@ -164,17 +191,26 @@ We'll use a Helm chart to deploy the service account:
 2. `awsRoleArn`: Your role ARN
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/helm_sa_2.png" alt="Override service account name" />
+  <img
+    src="/images/aws-iam-assume-role/helm_sa_2.png"
+    alt="Override service account name"
+  />
 </Frame>
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/helm_sa_3.png" alt="Override AWS role ARN" />
+  <img
+    src="/images/aws-iam-assume-role/helm_sa_3.png"
+    alt="Override AWS role ARN"
+  />
 </Frame>
 
 Deploy the Helm service and verify it completes successfully:
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/helm_sa_logs.png" alt="Service account creation logs" />
+  <img
+    src="/images/aws-iam-assume-role/helm_sa_logs.png"
+    alt="Service account creation logs"
+  />
 </Frame>
 
 ---
@@ -188,7 +224,10 @@ Deploy the Helm service and verify it completes successfully:
 3. Deploy using the **Deploy now** button
 
 <Frame>
-  <img src="/images/aws-iam-assume-role/debian_sa.png" alt="Set service account on application" />
+  <img
+    src="/images/aws-iam-assume-role/debian_sa.png"
+    alt="Set service account on application"
+  />
 </Frame>
 
 ### Validate Access
@@ -239,13 +278,21 @@ Initial setup requires multiple configuration steps across AWS and Kubernetes. O
     Learn about EKS cluster management
   </Card>
 
-  <Card title="Advanced Settings" icon="sliders" href="/configuration/service-advanced-settings">
-    Configure service advanced settings
-  </Card>
-
-  <Card title="Environment Variables" icon="key" href="/configuration/environment-variables">
-    Manage environment variables and secrets
-  </Card>
+<Card
+  title="Advanced Settings"
+  icon="sliders"
+  href="/configuration/service-advanced-settings"
+>
+  Configure service advanced settings
+</Card>
+
+<Card
+  title="Environment Variables"
+  icon="key"
+  href="/configuration/environment-variables"
+>
+  Manage environment variables and secrets
+</Card>
 
   <Card title="Helm Services" icon="/images/logos/helm-icon.svg" href="/configuration/helm">
     Deploy applications with Helm
diff --git a/docs/getting-started/guides/getting-started/connect-database.mdx b/docs/getting-started/guides/getting-started/connect-database.mdx
index 3ad5537..cfdc202 100644
--- a/docs/getting-started/guides/getting-started/connect-database.mdx
+++ b/docs/getting-started/guides/getting-started/connect-database.mdx
@@ -38,11 +38,13 @@ Qovery supports the following managed databases on AWS:
   </Step>
 
   <Step title="Add Database">
-    Click the **Add Database** button.
+    Click the **New Service** button, then either:
+    - Select **Database** from the service type list, or
+    - Search directly for the database you want (e.g., "MySQL", "PostgreSQL")
   </Step>
 
   <Step title="Configure Basic Settings">
-    Select and configure your database:
+    Configure your database:
 
     - **Database Type**: PostgreSQL, MySQL, MongoDB, or Redis
     - **Name**: Give your database a name
diff --git a/docs/getting-started/guides/getting-started/deploy-your-first-application.mdx b/docs/getting-started/guides/getting-started/deploy-your-first-application.mdx
index 5e2fa79..6d4eebe 100644
--- a/docs/getting-started/guides/getting-started/deploy-your-first-application.mdx
+++ b/docs/getting-started/guides/getting-started/deploy-your-first-application.mdx
@@ -25,21 +25,11 @@ This guide covers Git Repository and Container Registry deployments. For Helm ch
 
 [Projects](/configuration/project) organize your applications and environments.
 
-**Two ways to create a project:**
-
-**Option A - From Project Selector (Quick):**
-1. In [Qovery Console](https://console.qovery.com), click the **Project selector** in the header
-2. Click **New** button
+1. Go to [Qovery Console](https://console.qovery.com) and open your organization overview
+2. Click the **New Project** button
 3. Enter a project name (e.g., "My First Project")
 4. Click **Create**
 
-**Option B - From Organization Settings:**
-1. Go to **Organization Settings**
-2. Navigate to the **Projects** section
-3. Click **Create Project**
-4. Enter project details
-5. Click **Create**
-
 <Frame>
   <img src="/images/configuration/project/project_creation.png" alt="Create a new project in Qovery" />
 </Frame>
diff --git a/docs/getting-started/installation/azure.mdx b/docs/getting-started/installation/azure.mdx
index e94185d..8a437a3 100644
--- a/docs/getting-started/installation/azure.mdx
+++ b/docs/getting-started/installation/azure.mdx
@@ -94,7 +94,7 @@ Qovery needs credentials to manage resources in your Azure subscription. We use
 <Steps>
   <Step title="Start Cluster Creation">
     1. Go to [Qovery Console](https://console.qovery.com)
-    2. Click **Clusters** in the left sidebar
+    2. Go to your organization overview and click on the **Clusters** tab
     3. Click **Create Cluster**
     4. Select **Azure** as the cloud provider
   </Step>
diff --git a/docs/getting-started/installation/gcp.mdx b/docs/getting-started/installation/gcp.mdx
index be4d065..19869aa 100644
--- a/docs/getting-started/installation/gcp.mdx
+++ b/docs/getting-started/installation/gcp.mdx
@@ -88,7 +88,7 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
 <Steps>
   <Step title="Start Cluster Creation">
     1. Go to [Qovery Console](https://console.qovery.com)
-    2. Click **Clusters** in the left sidebar
+    2. Go to your organization overview and click on the **Clusters** tab
     3. Click **Create Cluster**
     4. Select **GCP** as the cloud provider
   </Step>
@@ -105,7 +105,7 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
 
     The command will look like:
     ```bash
-    curl https://hub.qovery.com/files/create_credentials_gcp.sh | bash -s -- YOUR_PROJECT_ID qovery_role qovery-service-account
+    curl https://setup.qovery.com/create_credentials_gcp.sh | bash -s -- YOUR_PROJECT_ID qovery_role qovery-service-account
     ```
 
     <Info>
diff --git a/docs/getting-started/installation/scaleway.mdx b/docs/getting-started/installation/scaleway.mdx
index fd3f346..cd5b427 100644
--- a/docs/getting-started/installation/scaleway.mdx
+++ b/docs/getting-started/installation/scaleway.mdx
@@ -152,7 +152,7 @@ Qovery needs API credentials to manage resources in your Scaleway account. We us
 <Steps>
   <Step title="Start Cluster Creation">
     1. Go to [Qovery Console](https://console.qovery.com)
-    2. Click **Clusters** in the left sidebar
+    2. Go to your organization overview and click on the **Clusters** tab
     3. Click **Create Cluster**
     4. Select **Scaleway** as the cloud provider
   </Step>
diff --git a/docs/getting-started/security-and-compliance/audit-logs.mdx b/docs/getting-started/security-and-compliance/audit-logs.mdx
index b1b000a..e089138 100644
--- a/docs/getting-started/security-and-compliance/audit-logs.mdx
+++ b/docs/getting-started/security-and-compliance/audit-logs.mdx
@@ -9,15 +9,19 @@ This feature enables you to track all changes to your organizational configurati
 
 ## Access
 
-Navigate to the `Audit logs` section from the left navigation bar in the Qovery Console.
+Navigate to the `Audit logs` section from the top navigation bar in the Qovery Console.
 
 <Frame>
-  <img src="/images/configuration/audit-logs/audit-logs-access.png" alt="Access audit logs from left navigation" />
+  <img
+    src="/images/configuration/audit-logs/audit-logs-access.png"
+    alt="Access audit logs from left navigation"
+  />
 </Frame>
 
 ## Event Retention
 
 The event retention depends on your plan:
+
 - **User**: 3 days
 - **Team**: 7 days
 - **Business**: 30 days
@@ -59,7 +63,7 @@ You can filter audit logs by:
     - selecting a specific environment
     - selecting a target service
   - For an Environment: you can fine tune your research by
-    - selecting a specific project 
+    - selecting a specific project
     - selecting a target environment
   - For other types: you can filter on a specific target
 - **User** - Select a specific user
@@ -70,7 +74,10 @@ You can filter audit logs by:
 Throughout the Qovery Console, you'll find quick access to audit logs via the **"See Events"** button in the 3-dot submenus. This allows you to quickly filter and view events for specific resources.
 
 <Frame>
-  <img src="/images/configuration/audit-logs/see-events.png" alt="View event details in JSON format" />
+  <img
+    src="/images/configuration/audit-logs/see-events.png"
+    alt="View event details in JSON format"
+  />
 </Frame>
 
 ---
@@ -82,9 +89,13 @@ Throughout the Qovery Console, you'll find quick access to audit logs via the **
     Configure role-based access control
   </Card>
 
-  <Card title="API Tokens" icon="key" href="/configuration/organization/api-token">
-    Manage API access tokens
-  </Card>
+<Card
+  title="API Tokens"
+  icon="key"
+  href="/configuration/organization/api-token"
+>
+  Manage API access tokens
+</Card>
 
   <Card title="Security Overview" icon="shield" href="/getting-started/security-and-compliance/overview">
     Comprehensive security practices
diff --git a/docs/images/alias.png b/docs/images/alias.png
index db79997..ce47e0a 100644
Binary files a/docs/images/alias.png and b/docs/images/alias.png differ
diff --git a/docs/images/aws-iam-assume-role/create_sa.png b/docs/images/aws-iam-assume-role/create_sa.png
index 78cb05a..62c9d0d 100644
Binary files a/docs/images/aws-iam-assume-role/create_sa.png and b/docs/images/aws-iam-assume-role/create_sa.png differ
diff --git a/docs/images/aws-iam-assume-role/debian_namespace.png b/docs/images/aws-iam-assume-role/debian_namespace.png
index c9b80f9..cf0f808 100644
Binary files a/docs/images/aws-iam-assume-role/debian_namespace.png and b/docs/images/aws-iam-assume-role/debian_namespace.png differ
diff --git a/docs/images/aws-iam-assume-role/debian_sa.png b/docs/images/aws-iam-assume-role/debian_sa.png
index a3d639a..72b4dcf 100644
Binary files a/docs/images/aws-iam-assume-role/debian_sa.png and b/docs/images/aws-iam-assume-role/debian_sa.png differ
diff --git a/docs/images/aws-iam-assume-role/helm_sa_1.png b/docs/images/aws-iam-assume-role/helm_sa_1.png
index 52eb8ec..42b71e8 100644
Binary files a/docs/images/aws-iam-assume-role/helm_sa_1.png and b/docs/images/aws-iam-assume-role/helm_sa_1.png differ
diff --git a/docs/images/aws-iam-assume-role/helm_sa_2.png b/docs/images/aws-iam-assume-role/helm_sa_2.png
index 0772275..9f78f62 100644
Binary files a/docs/images/aws-iam-assume-role/helm_sa_2.png and b/docs/images/aws-iam-assume-role/helm_sa_2.png differ
diff --git a/docs/images/aws-iam-assume-role/helm_sa_3.png b/docs/images/aws-iam-assume-role/helm_sa_3.png
index 26721c3..12b2335 100644
Binary files a/docs/images/aws-iam-assume-role/helm_sa_3.png and b/docs/images/aws-iam-assume-role/helm_sa_3.png differ
diff --git a/docs/images/aws-iam-assume-role/helm_sa_logs.png b/docs/images/aws-iam-assume-role/helm_sa_logs.png
index 5d91710..306b43b 100644
Binary files a/docs/images/aws-iam-assume-role/helm_sa_logs.png and b/docs/images/aws-iam-assume-role/helm_sa_logs.png differ
diff --git a/docs/images/aws-iam-assume-role/set-helm-repo.png b/docs/images/aws-iam-assume-role/set-helm-repo.png
index ddc5485..6de3ca5 100644
Binary files a/docs/images/aws-iam-assume-role/set-helm-repo.png and b/docs/images/aws-iam-assume-role/set-helm-repo.png differ
diff --git a/docs/images/aws-vpc-peering-with-qovery/custom-cidr.png b/docs/images/aws-vpc-peering-with-qovery/custom-cidr.png
index 2d912aa..2f74972 100644
Binary files a/docs/images/aws-vpc-peering-with-qovery/custom-cidr.png and b/docs/images/aws-vpc-peering-with-qovery/custom-cidr.png differ
diff --git a/docs/images/aws-vpc-peering-with-qovery/qovery-rt-added.png b/docs/images/aws-vpc-peering-with-qovery/qovery-rt-added.png
index 85f4575..bd8c2d8 100644
Binary files a/docs/images/aws-vpc-peering-with-qovery/qovery-rt-added.png and b/docs/images/aws-vpc-peering-with-qovery/qovery-rt-added.png differ
diff --git a/docs/images/aws-vpc-peering-with-qovery/qovery-rt.png b/docs/images/aws-vpc-peering-with-qovery/qovery-rt.png
index 5e1b7e1..3be33fe 100644
Binary files a/docs/images/aws-vpc-peering-with-qovery/qovery-rt.png and b/docs/images/aws-vpc-peering-with-qovery/qovery-rt.png differ
diff --git a/docs/images/blue-green-rds/update-version.png b/docs/images/blue-green-rds/update-version.png
index b03838c..8d44c0f 100644
Binary files a/docs/images/blue-green-rds/update-version.png and b/docs/images/blue-green-rds/update-version.png differ
diff --git a/docs/images/certificate_management_for_multi_tenant_infrastructure/custom_domain.png b/docs/images/certificate_management_for_multi_tenant_infrastructure/custom_domain.png
index 865040f..8ffe65b 100644
Binary files a/docs/images/certificate_management_for_multi_tenant_infrastructure/custom_domain.png and b/docs/images/certificate_management_for_multi_tenant_infrastructure/custom_domain.png differ
diff --git a/docs/images/certificate_management_for_multi_tenant_infrastructure/edit_port.png b/docs/images/certificate_management_for_multi_tenant_infrastructure/edit_port.png
index 634ad33..75329ef 100644
Binary files a/docs/images/certificate_management_for_multi_tenant_infrastructure/edit_port.png and b/docs/images/certificate_management_for_multi_tenant_infrastructure/edit_port.png differ
diff --git a/docs/images/certificate_management_for_multi_tenant_infrastructure/list_variables.png b/docs/images/certificate_management_for_multi_tenant_infrastructure/list_variables.png
index e692a5c..698bc8e 100644
Binary files a/docs/images/certificate_management_for_multi_tenant_infrastructure/list_variables.png and b/docs/images/certificate_management_for_multi_tenant_infrastructure/list_variables.png differ
diff --git a/docs/images/certificate_management_for_multi_tenant_infrastructure/tenant_port.png b/docs/images/certificate_management_for_multi_tenant_infrastructure/tenant_port.png
index 3c3d5e2..a7d3c5c 100644
Binary files a/docs/images/certificate_management_for_multi_tenant_infrastructure/tenant_port.png and b/docs/images/certificate_management_for_multi_tenant_infrastructure/tenant_port.png differ
diff --git a/docs/images/cloudflare/10.png b/docs/images/cloudflare/10.png
index ca3cab4..bd2531e 100644
Binary files a/docs/images/cloudflare/10.png and b/docs/images/cloudflare/10.png differ
diff --git a/docs/images/cloudflare/12.png b/docs/images/cloudflare/12.png
index 28fbcf8..478cdad 100644
Binary files a/docs/images/cloudflare/12.png and b/docs/images/cloudflare/12.png differ
diff --git a/docs/images/cloudflare/13.png b/docs/images/cloudflare/13.png
index 23c9c69..87d0678 100644
Binary files a/docs/images/cloudflare/13.png and b/docs/images/cloudflare/13.png differ
diff --git a/docs/images/cloudflare/2.png b/docs/images/cloudflare/2.png
index 07d1b4f..2231767 100644
Binary files a/docs/images/cloudflare/2.png and b/docs/images/cloudflare/2.png differ
diff --git a/docs/images/cloudflare/3.png b/docs/images/cloudflare/3.png
index f9e6107..1b4e5ed 100644
Binary files a/docs/images/cloudflare/3.png and b/docs/images/cloudflare/3.png differ
diff --git a/docs/images/cloudflare/8.png b/docs/images/cloudflare/8.png
index 1e929e8..50c1a95 100644
Binary files a/docs/images/cloudflare/8.png and b/docs/images/cloudflare/8.png differ
diff --git a/docs/images/cloudflare/9.png b/docs/images/cloudflare/9.png
index 6377438..881be89 100644
Binary files a/docs/images/cloudflare/9.png and b/docs/images/cloudflare/9.png differ
diff --git a/docs/images/configuration/advanced-settings/advanced_settings.png b/docs/images/configuration/advanced-settings/advanced_settings.png
index f12b9ab..fc04181 100644
Binary files a/docs/images/configuration/advanced-settings/advanced_settings.png and b/docs/images/configuration/advanced-settings/advanced_settings.png differ
diff --git a/docs/images/configuration/advanced-settings/settings.png b/docs/images/configuration/advanced-settings/settings.png
index 6507f69..c35bb53 100644
Binary files a/docs/images/configuration/advanced-settings/settings.png and b/docs/images/configuration/advanced-settings/settings.png differ
diff --git a/docs/images/configuration/application/app-16.png b/docs/images/configuration/application/app-16.png
index 9f2ef0b..1b4e5ed 100644
Binary files a/docs/images/configuration/application/app-16.png and b/docs/images/configuration/application/app-16.png differ
diff --git a/docs/images/configuration/application/cluster-keda-activation.png b/docs/images/configuration/application/cluster-keda-activation.png
index b0bc875..e9c0b73 100644
Binary files a/docs/images/configuration/application/cluster-keda-activation.png and b/docs/images/configuration/application/cluster-keda-activation.png differ
diff --git a/docs/images/configuration/application/domain_check.png b/docs/images/configuration/application/domain_check.png
index b3cb9dd..33bac39 100644
Binary files a/docs/images/configuration/application/domain_check.png and b/docs/images/configuration/application/domain_check.png differ
diff --git a/docs/images/configuration/application/domain_check_error.png b/docs/images/configuration/application/domain_check_error.png
index 4ea0fb8..781fe54 100644
Binary files a/docs/images/configuration/application/domain_check_error.png and b/docs/images/configuration/application/domain_check_error.png differ
diff --git a/docs/images/configuration/audit-logs/audit-logs-access.png b/docs/images/configuration/audit-logs/audit-logs-access.png
index 3ff9fe3..a793cd2 100644
Binary files a/docs/images/configuration/audit-logs/audit-logs-access.png and b/docs/images/configuration/audit-logs/audit-logs-access.png differ
diff --git a/docs/images/configuration/audit-logs/see-events.png b/docs/images/configuration/audit-logs/see-events.png
index b9ce0b2..cb4de27 100644
Binary files a/docs/images/configuration/audit-logs/see-events.png and b/docs/images/configuration/audit-logs/see-events.png differ
diff --git a/docs/images/configuration/clusters/cluster-advanced-settings-console.png b/docs/images/configuration/clusters/cluster-advanced-settings-console.png
index f0e97b3..7ee64b2 100644
Binary files a/docs/images/configuration/clusters/cluster-advanced-settings-console.png and b/docs/images/configuration/clusters/cluster-advanced-settings-console.png differ
diff --git a/docs/images/configuration/clusters/cluster-overview.png b/docs/images/configuration/clusters/cluster-overview.png
index c8fe9f5..9454c92 100644
Binary files a/docs/images/configuration/clusters/cluster-overview.png and b/docs/images/configuration/clusters/cluster-overview.png differ
diff --git a/docs/images/configuration/clusters/cluster-shell-access.png b/docs/images/configuration/clusters/cluster-shell-access.png
index aad9e13..8591683 100644
Binary files a/docs/images/configuration/clusters/cluster-shell-access.png and b/docs/images/configuration/clusters/cluster-shell-access.png differ
diff --git a/docs/images/configuration/clusters/cluster_actions.png b/docs/images/configuration/clusters/cluster_actions.png
index 243be78..056b2f4 100644
Binary files a/docs/images/configuration/clusters/cluster_actions.png and b/docs/images/configuration/clusters/cluster_actions.png differ
diff --git a/docs/images/configuration/clusters/cluster_logs_access.png b/docs/images/configuration/clusters/cluster_logs_access.png
index f657a82..8e01a64 100644
Binary files a/docs/images/configuration/clusters/cluster_logs_access.png and b/docs/images/configuration/clusters/cluster_logs_access.png differ
diff --git a/docs/images/configuration/clusters/cluster_section_access.png b/docs/images/configuration/clusters/cluster_section_access.png
index 25e6822..e1df8e1 100644
Binary files a/docs/images/configuration/clusters/cluster_section_access.png and b/docs/images/configuration/clusters/cluster_section_access.png differ
diff --git a/docs/images/configuration/clusters/cluster_status_unavailable.png b/docs/images/configuration/clusters/cluster_status_unavailable.png
index 4b662c6..4b6152e 100644
Binary files a/docs/images/configuration/clusters/cluster_status_unavailable.png and b/docs/images/configuration/clusters/cluster_status_unavailable.png differ
diff --git a/docs/images/configuration/clusters/cluster_statuses.png b/docs/images/configuration/clusters/cluster_statuses.png
index 45d7a0a..e528339 100644
Binary files a/docs/images/configuration/clusters/cluster_statuses.png and b/docs/images/configuration/clusters/cluster_statuses.png differ
diff --git a/docs/images/configuration/clusters/error-infra-logs.jpg b/docs/images/configuration/clusters/error-infra-logs.jpg
index 22568a3..f1e3694 100644
Binary files a/docs/images/configuration/clusters/error-infra-logs.jpg and b/docs/images/configuration/clusters/error-infra-logs.jpg differ
diff --git a/docs/images/configuration/clusters/ok-infra-logs.jpg b/docs/images/configuration/clusters/ok-infra-logs.jpg
index c4e1f04..32c6bcb 100644
Binary files a/docs/images/configuration/clusters/ok-infra-logs.jpg and b/docs/images/configuration/clusters/ok-infra-logs.jpg differ
diff --git a/docs/images/configuration/cronjob/app-1.png b/docs/images/configuration/cronjob/app-1.png
index 091620f..0aa173b 100644
Binary files a/docs/images/configuration/cronjob/app-1.png and b/docs/images/configuration/cronjob/app-1.png differ
diff --git a/docs/images/configuration/cronjob/clone_service.png b/docs/images/configuration/cronjob/clone_service.png
index 87bb7ad..20e4649 100644
Binary files a/docs/images/configuration/cronjob/clone_service.png and b/docs/images/configuration/cronjob/clone_service.png differ
diff --git a/docs/images/configuration/cronjob/cronjob_recap.png b/docs/images/configuration/cronjob/cronjob_recap.png
index 750567d..b328641 100644
Binary files a/docs/images/configuration/cronjob/cronjob_recap.png and b/docs/images/configuration/cronjob/cronjob_recap.png differ
diff --git a/docs/images/configuration/cronjob/service_creation.png b/docs/images/configuration/cronjob/service_creation.png
index a2478ee..bcaff96 100644
Binary files a/docs/images/configuration/cronjob/service_creation.png and b/docs/images/configuration/cronjob/service_creation.png differ
diff --git a/docs/images/configuration/cronjob/settings.png b/docs/images/configuration/cronjob/settings.png
index 6507f69..d8191a7 100644
Binary files a/docs/images/configuration/cronjob/settings.png and b/docs/images/configuration/cronjob/settings.png differ
diff --git a/docs/images/configuration/cronjob/variables.png b/docs/images/configuration/cronjob/variables.png
index 7fbc342..d5961a7 100644
Binary files a/docs/images/configuration/cronjob/variables.png and b/docs/images/configuration/cronjob/variables.png differ
diff --git a/docs/images/configuration/database/db-1.png b/docs/images/configuration/database/db-1.png
index 5d8c6de..535d116 100644
Binary files a/docs/images/configuration/database/db-1.png and b/docs/images/configuration/database/db-1.png differ
diff --git a/docs/images/configuration/database/db-2.png b/docs/images/configuration/database/db-2.png
index a00e892..c5c806b 100644
Binary files a/docs/images/configuration/database/db-2.png and b/docs/images/configuration/database/db-2.png differ
diff --git a/docs/images/configuration/database/db-3.png b/docs/images/configuration/database/db-3.png
index 24d7703..1586cf9 100644
Binary files a/docs/images/configuration/database/db-3.png and b/docs/images/configuration/database/db-3.png differ
diff --git a/docs/images/configuration/database/db-4.png b/docs/images/configuration/database/db-4.png
index 118bd57..576ee06 100644
Binary files a/docs/images/configuration/database/db-4.png and b/docs/images/configuration/database/db-4.png differ
diff --git a/docs/images/configuration/database/delete.png b/docs/images/configuration/database/delete.png
index fab895d..43ec2d2 100644
Binary files a/docs/images/configuration/database/delete.png and b/docs/images/configuration/database/delete.png differ
diff --git a/docs/images/configuration/database/settings.png b/docs/images/configuration/database/settings.png
index bf75ca6..b1b6afd 100644
Binary files a/docs/images/configuration/database/settings.png and b/docs/images/configuration/database/settings.png differ
diff --git a/docs/images/configuration/deployment-rule/deployment_rules_project.png b/docs/images/configuration/deployment-rule/deployment_rules_project.png
index 15520b0..9cacac9 100644
Binary files a/docs/images/configuration/deployment-rule/deployment_rules_project.png and b/docs/images/configuration/deployment-rule/deployment_rules_project.png differ
diff --git a/docs/images/configuration/deployment-rule/ordering_deployment_rule.png b/docs/images/configuration/deployment-rule/ordering_deployment_rule.png
index c35fcbc..f030468 100644
Binary files a/docs/images/configuration/deployment-rule/ordering_deployment_rule.png and b/docs/images/configuration/deployment-rule/ordering_deployment_rule.png differ
diff --git a/docs/images/configuration/environment-variable/database_alias.png b/docs/images/configuration/environment-variable/database_alias.png
index 8d768c2..7c87af2 100644
Binary files a/docs/images/configuration/environment-variable/database_alias.png and b/docs/images/configuration/environment-variable/database_alias.png differ
diff --git a/docs/images/configuration/environment-variable/env_file.png b/docs/images/configuration/environment-variable/env_file.png
index 397679c..0b167ca 100644
Binary files a/docs/images/configuration/environment-variable/env_file.png and b/docs/images/configuration/environment-variable/env_file.png differ
diff --git a/docs/images/configuration/environment-variable/env_key_value.png b/docs/images/configuration/environment-variable/env_key_value.png
index c3948e1..36cb778 100644
Binary files a/docs/images/configuration/environment-variable/env_key_value.png and b/docs/images/configuration/environment-variable/env_key_value.png differ
diff --git a/docs/images/configuration/environment-variable/host_alias.png b/docs/images/configuration/environment-variable/host_alias.png
index 8357151..ed98adc 100644
Binary files a/docs/images/configuration/environment-variable/host_alias.png and b/docs/images/configuration/environment-variable/host_alias.png differ
diff --git a/docs/images/configuration/environment-variable/var_creation_1.png b/docs/images/configuration/environment-variable/var_creation_1.png
index b59fc67..6a6affe 100644
Binary files a/docs/images/configuration/environment-variable/var_creation_1.png and b/docs/images/configuration/environment-variable/var_creation_1.png differ
diff --git a/docs/images/configuration/environment-variable/var_creation_2.png b/docs/images/configuration/environment-variable/var_creation_2.png
index 746c79d..3bf6d82 100644
Binary files a/docs/images/configuration/environment-variable/var_creation_2.png and b/docs/images/configuration/environment-variable/var_creation_2.png differ
diff --git a/docs/images/configuration/environment-variable/var_delete.png b/docs/images/configuration/environment-variable/var_delete.png
index ca87adb..d3f7f86 100644
Binary files a/docs/images/configuration/environment-variable/var_delete.png and b/docs/images/configuration/environment-variable/var_delete.png differ
diff --git a/docs/images/configuration/environment-variable/var_edit.png b/docs/images/configuration/environment-variable/var_edit.png
index d2a2b07..67a3653 100644
Binary files a/docs/images/configuration/environment-variable/var_edit.png and b/docs/images/configuration/environment-variable/var_edit.png differ
diff --git a/docs/images/configuration/environment/clone_environment.png b/docs/images/configuration/environment/clone_environment.png
index bf95d85..cca26b0 100644
Binary files a/docs/images/configuration/environment/clone_environment.png and b/docs/images/configuration/environment/clone_environment.png differ
diff --git a/docs/images/configuration/environment/clone_environment_modal.png b/docs/images/configuration/environment/clone_environment_modal.png
index db5bcf4..0974eba 100644
Binary files a/docs/images/configuration/environment/clone_environment_modal.png and b/docs/images/configuration/environment/clone_environment_modal.png differ
diff --git a/docs/images/configuration/environment/create_environment_1.png b/docs/images/configuration/environment/create_environment_1.png
index 8afd99e..a103641 100644
Binary files a/docs/images/configuration/environment/create_environment_1.png and b/docs/images/configuration/environment/create_environment_1.png differ
diff --git a/docs/images/configuration/environment/create_environment_2.png b/docs/images/configuration/environment/create_environment_2.png
index 36974bb..c90b529 100644
Binary files a/docs/images/configuration/environment/create_environment_2.png and b/docs/images/configuration/environment/create_environment_2.png differ
diff --git a/docs/images/configuration/environment/create_service.png b/docs/images/configuration/environment/create_service.png
index 1c51e7d..65d4daa 100644
Binary files a/docs/images/configuration/environment/create_service.png and b/docs/images/configuration/environment/create_service.png differ
diff --git a/docs/images/configuration/environment/deployment_pipeline.png b/docs/images/configuration/environment/deployment_pipeline.png
index afb4538..734acc8 100644
Binary files a/docs/images/configuration/environment/deployment_pipeline.png and b/docs/images/configuration/environment/deployment_pipeline.png differ
diff --git a/docs/images/configuration/environment/environment_settings.png b/docs/images/configuration/environment/environment_settings.png
index 715ad61..698b2f7 100644
Binary files a/docs/images/configuration/environment/environment_settings.png and b/docs/images/configuration/environment/environment_settings.png differ
diff --git a/docs/images/configuration/environment/preview_environment.png b/docs/images/configuration/environment/preview_environment.png
index 0e308e8..cba6ff7 100644
Binary files a/docs/images/configuration/environment/preview_environment.png and b/docs/images/configuration/environment/preview_environment.png differ
diff --git a/docs/images/configuration/helm/clone_service.png b/docs/images/configuration/helm/clone_service.png
index 87bb7ad..d13a6dc 100644
Binary files a/docs/images/configuration/helm/clone_service.png and b/docs/images/configuration/helm/clone_service.png differ
diff --git a/docs/images/configuration/helm/helm_creation_recap.png b/docs/images/configuration/helm/helm_creation_recap.png
index 11362ca..00e0cb4 100644
Binary files a/docs/images/configuration/helm/helm_creation_recap.png and b/docs/images/configuration/helm/helm_creation_recap.png differ
diff --git a/docs/images/configuration/job/job_output.png b/docs/images/configuration/job/job_output.png
index 589ea59..cea8f80 100644
Binary files a/docs/images/configuration/job/job_output.png and b/docs/images/configuration/job/job_output.png differ
diff --git a/docs/images/configuration/lifecycle-job/cronjob_recap.png b/docs/images/configuration/lifecycle-job/cronjob_recap.png
index 750567d..b328641 100644
Binary files a/docs/images/configuration/lifecycle-job/cronjob_recap.png and b/docs/images/configuration/lifecycle-job/cronjob_recap.png differ
diff --git a/docs/images/configuration/lifecycle-job/job_output.png b/docs/images/configuration/lifecycle-job/job_output.png
index 8bd4341..cea8f80 100644
Binary files a/docs/images/configuration/lifecycle-job/job_output.png and b/docs/images/configuration/lifecycle-job/job_output.png differ
diff --git a/docs/images/configuration/lifecycle-job/service_creation.png b/docs/images/configuration/lifecycle-job/service_creation.png
index a2478ee..bcaff96 100644
Binary files a/docs/images/configuration/lifecycle-job/service_creation.png and b/docs/images/configuration/lifecycle-job/service_creation.png differ
diff --git a/docs/images/configuration/lifecycle-job/variables.png b/docs/images/configuration/lifecycle-job/variables.png
index 7fbc342..d5961a7 100644
Binary files a/docs/images/configuration/lifecycle-job/variables.png and b/docs/images/configuration/lifecycle-job/variables.png differ
diff --git a/docs/images/configuration/organization/Github_enterprise.png b/docs/images/configuration/organization/Github_enterprise.png
index 0d18488..5769ce0 100644
Binary files a/docs/images/configuration/organization/Github_enterprise.png and b/docs/images/configuration/organization/Github_enterprise.png differ
diff --git a/docs/images/configuration/organization/access_settings.png b/docs/images/configuration/organization/access_settings.png
index 60228c7..5b0ee40 100644
Binary files a/docs/images/configuration/organization/access_settings.png and b/docs/images/configuration/organization/access_settings.png differ
diff --git a/docs/images/configuration/organization/annotation_group.png b/docs/images/configuration/organization/annotation_group.png
index c790bb6..4c194f5 100644
Binary files a/docs/images/configuration/organization/annotation_group.png and b/docs/images/configuration/organization/annotation_group.png differ
diff --git a/docs/images/configuration/organization/annotations_labels_settings.png b/docs/images/configuration/organization/annotations_labels_settings.png
index 528c951..0b088fb 100644
Binary files a/docs/images/configuration/organization/annotations_labels_settings.png and b/docs/images/configuration/organization/annotations_labels_settings.png differ
diff --git a/docs/images/configuration/organization/change_organization.png b/docs/images/configuration/organization/change_organization.png
index 0b3296b..0926cda 100644
Binary files a/docs/images/configuration/organization/change_organization.png and b/docs/images/configuration/organization/change_organization.png differ
diff --git a/docs/images/configuration/organization/cloud-credentials.png b/docs/images/configuration/organization/cloud-credentials.png
index 63c78aa..1c220d5 100644
Binary files a/docs/images/configuration/organization/cloud-credentials.png and b/docs/images/configuration/organization/cloud-credentials.png differ
diff --git a/docs/images/configuration/organization/container_1.png b/docs/images/configuration/organization/container_1.png
index b11aff1..58b7785 100644
Binary files a/docs/images/configuration/organization/container_1.png and b/docs/images/configuration/organization/container_1.png differ
diff --git a/docs/images/configuration/organization/container_creation.png b/docs/images/configuration/organization/container_creation.png
index dadc23d..3ea757a 100644
Binary files a/docs/images/configuration/organization/container_creation.png and b/docs/images/configuration/organization/container_creation.png differ
diff --git a/docs/images/configuration/organization/container_edit.png b/docs/images/configuration/organization/container_edit.png
index ba86a9b..87fa832 100644
Binary files a/docs/images/configuration/organization/container_edit.png and b/docs/images/configuration/organization/container_edit.png differ
diff --git a/docs/images/configuration/organization/create_organization_after_signing_up.png b/docs/images/configuration/organization/create_organization_after_signing_up.png
index 249a24c..bab8aab 100644
Binary files a/docs/images/configuration/organization/create_organization_after_signing_up.png and b/docs/images/configuration/organization/create_organization_after_signing_up.png differ
diff --git a/docs/images/configuration/organization/helm_repository_1.png b/docs/images/configuration/organization/helm_repository_1.png
index 0c02e44..e41650b 100644
Binary files a/docs/images/configuration/organization/helm_repository_1.png and b/docs/images/configuration/organization/helm_repository_1.png differ
diff --git a/docs/images/configuration/organization/helm_repository_creation.png b/docs/images/configuration/organization/helm_repository_creation.png
index 171fa47..112b503 100644
Binary files a/docs/images/configuration/organization/helm_repository_creation.png and b/docs/images/configuration/organization/helm_repository_creation.png differ
diff --git a/docs/images/configuration/organization/helm_repository_edit.png b/docs/images/configuration/organization/helm_repository_edit.png
index c8bdfa3..e4a1087 100644
Binary files a/docs/images/configuration/organization/helm_repository_edit.png and b/docs/images/configuration/organization/helm_repository_edit.png differ
diff --git a/docs/images/configuration/organization/label_group.png b/docs/images/configuration/organization/label_group.png
index e80a385..4321a6c 100644
Binary files a/docs/images/configuration/organization/label_group.png and b/docs/images/configuration/organization/label_group.png differ
diff --git a/docs/images/configuration/organization/members.png b/docs/images/configuration/organization/members.png
index 9c2a9eb..f269db3 100644
Binary files a/docs/images/configuration/organization/members.png and b/docs/images/configuration/organization/members.png differ
diff --git a/docs/images/configuration/organization/token_api_access.png b/docs/images/configuration/organization/token_api_access.png
index 1b0351b..7a2826f 100644
Binary files a/docs/images/configuration/organization/token_api_access.png and b/docs/images/configuration/organization/token_api_access.png differ
diff --git a/docs/images/configuration/project/project_creation.png b/docs/images/configuration/project/project_creation.png
index 97efb18..436f131 100644
Binary files a/docs/images/configuration/project/project_creation.png and b/docs/images/configuration/project/project_creation.png differ
diff --git a/docs/images/configuration/project/project_delete.png b/docs/images/configuration/project/project_delete.png
index b549aa2..02a76b6 100644
Binary files a/docs/images/configuration/project/project_delete.png and b/docs/images/configuration/project/project_delete.png differ
diff --git a/docs/images/configuration/project/project_update.png b/docs/images/configuration/project/project_update.png
index eed00fe..61a8466 100644
Binary files a/docs/images/configuration/project/project_update.png and b/docs/images/configuration/project/project_update.png differ
diff --git a/docs/images/configuration/terraform/terraform-action-menu.png b/docs/images/configuration/terraform/terraform-action-menu.png
index 8633574..4f6fb5f 100644
Binary files a/docs/images/configuration/terraform/terraform-action-menu.png and b/docs/images/configuration/terraform/terraform-action-menu.png differ
diff --git a/docs/images/configuration/terraform/terraform-arguments.png b/docs/images/configuration/terraform/terraform-arguments.png
index 164ab1d..46b9e96 100644
Binary files a/docs/images/configuration/terraform/terraform-arguments.png and b/docs/images/configuration/terraform/terraform-arguments.png differ
diff --git a/docs/images/configuration/terraform/terraform-variables-configuration.png b/docs/images/configuration/terraform/terraform-variables-configuration.png
index 514fe46..7636195 100644
Binary files a/docs/images/configuration/terraform/terraform-variables-configuration.png and b/docs/images/configuration/terraform/terraform-variables-configuration.png differ
diff --git a/docs/images/configuration/user-account/access_user_account.png b/docs/images/configuration/user-account/access_user_account.png
index bf669b8..aa87b88 100644
Binary files a/docs/images/configuration/user-account/access_user_account.png and b/docs/images/configuration/user-account/access_user_account.png differ
diff --git a/docs/images/copilot/console-copilot-button.png b/docs/images/copilot/console-copilot-button.png
new file mode 100644
index 0000000..7664e0f
Binary files /dev/null and b/docs/images/copilot/console-copilot-button.png differ
diff --git a/docs/images/deploy-jupyterhub-qovery/deploy.png b/docs/images/deploy-jupyterhub-qovery/deploy.png
index 111c3fa..0453e3b 100644
Binary files a/docs/images/deploy-jupyterhub-qovery/deploy.png and b/docs/images/deploy-jupyterhub-qovery/deploy.png differ
diff --git a/docs/images/deploy-jupyterhub-qovery/link.png b/docs/images/deploy-jupyterhub-qovery/link.png
index 2df6f9b..9fb3348 100644
Binary files a/docs/images/deploy-jupyterhub-qovery/link.png and b/docs/images/deploy-jupyterhub-qovery/link.png differ
diff --git a/docs/images/deployment/access_logs.png b/docs/images/deployment/access_logs.png
index 8ad9c30..4d35bf5 100644
Binary files a/docs/images/deployment/access_logs.png and b/docs/images/deployment/access_logs.png differ
diff --git a/docs/images/deployment/auto-deploy-creation-flow.png b/docs/images/deployment/auto-deploy-creation-flow.png
index 63875aa..df6fd4d 100644
Binary files a/docs/images/deployment/auto-deploy-creation-flow.png and b/docs/images/deployment/auto-deploy-creation-flow.png differ
diff --git a/docs/images/deployment/auto-deploy-settings.png b/docs/images/deployment/auto-deploy-settings.png
index 06deed4..fea9aa5 100644
Binary files a/docs/images/deployment/auto-deploy-settings.png and b/docs/images/deployment/auto-deploy-settings.png differ
diff --git a/docs/images/deployment/deploy_latest_version.png b/docs/images/deployment/deploy_latest_version.png
index 828e9ae..e87f6f2 100644
Binary files a/docs/images/deployment/deploy_latest_version.png and b/docs/images/deployment/deploy_latest_version.png differ
diff --git a/docs/images/deployment/deploy_other_version.png b/docs/images/deployment/deploy_other_version.png
index 025034d..528e30d 100644
Binary files a/docs/images/deployment/deploy_other_version.png and b/docs/images/deployment/deploy_other_version.png differ
diff --git a/docs/images/deployment/deployment_actions.png b/docs/images/deployment/deployment_actions.png
index 4621338..fd6b979 100644
Binary files a/docs/images/deployment/deployment_actions.png and b/docs/images/deployment/deployment_actions.png differ
diff --git a/docs/images/deployment/deployment_history.png b/docs/images/deployment/deployment_history.png
index c36c4c1..edfcdaa 100644
Binary files a/docs/images/deployment/deployment_history.png and b/docs/images/deployment/deployment_history.png differ
diff --git a/docs/images/deployment/deployment_logs_view.png b/docs/images/deployment/deployment_logs_view.png
index 6aa6a9a..eea1a85 100644
Binary files a/docs/images/deployment/deployment_logs_view.png and b/docs/images/deployment/deployment_logs_view.png differ
diff --git a/docs/images/deployment/deployment_restrictions.png b/docs/images/deployment/deployment_restrictions.png
index 8906443..399dd0e 100644
Binary files a/docs/images/deployment/deployment_restrictions.png and b/docs/images/deployment/deployment_restrictions.png differ
diff --git a/docs/images/deployment/deployment_status.png b/docs/images/deployment/deployment_status.png
index c820d2f..52b2a10 100644
Binary files a/docs/images/deployment/deployment_status.png and b/docs/images/deployment/deployment_status.png differ
diff --git a/docs/images/deployment/live_logs.png b/docs/images/deployment/live_logs.png
index 7fd5682..091de8f 100644
Binary files a/docs/images/deployment/live_logs.png and b/docs/images/deployment/live_logs.png differ
diff --git a/docs/images/deployment/live_logs_filtered.png b/docs/images/deployment/live_logs_filtered.png
index 191e6af..32cf0f9 100644
Binary files a/docs/images/deployment/live_logs_filtered.png and b/docs/images/deployment/live_logs_filtered.png differ
diff --git a/docs/images/deployment/mirror-registry.png b/docs/images/deployment/mirror-registry.png
index c6b251b..d451184 100644
Binary files a/docs/images/deployment/mirror-registry.png and b/docs/images/deployment/mirror-registry.png differ
diff --git a/docs/images/deployment/pipeline_view.png b/docs/images/deployment/pipeline_view.png
index 08e10cb..b95448c 100644
Binary files a/docs/images/deployment/pipeline_view.png and b/docs/images/deployment/pipeline_view.png differ
diff --git a/docs/images/deployment/run_deployment_statuses.png b/docs/images/deployment/run_deployment_statuses.png
index 6e56d0b..ffc73ee 100644
Binary files a/docs/images/deployment/run_deployment_statuses.png and b/docs/images/deployment/run_deployment_statuses.png differ
diff --git a/docs/images/doppler/api-token.png b/docs/images/doppler/api-token.png
index e3003ce..817a9b7 100644
Binary files a/docs/images/doppler/api-token.png and b/docs/images/doppler/api-token.png differ
diff --git a/docs/images/e2e-with-github-actions-and-qovery/blueprint-environment.png b/docs/images/e2e-with-github-actions-and-qovery/blueprint-environment.png
index ce50792..17190ac 100644
Binary files a/docs/images/e2e-with-github-actions-and-qovery/blueprint-environment.png and b/docs/images/e2e-with-github-actions-and-qovery/blueprint-environment.png differ
diff --git a/docs/images/email/email-notification-channel-setup.png b/docs/images/email/email-notification-channel-setup.png
index 1511665..62c060b 100644
Binary files a/docs/images/email/email-notification-channel-setup.png and b/docs/images/email/email-notification-channel-setup.png differ
diff --git a/docs/images/heroku/heroku-1.png b/docs/images/heroku/heroku-1.png
index 9ced0a7..52b35c2 100644
Binary files a/docs/images/heroku/heroku-1.png and b/docs/images/heroku/heroku-1.png differ
diff --git a/docs/images/how-to-use-lifecycle-job/1.png b/docs/images/how-to-use-lifecycle-job/1.png
deleted file mode 100644
index a8a0777..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/1.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/10.png b/docs/images/how-to-use-lifecycle-job/10.png
deleted file mode 100644
index 4814ecc..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/10.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/11.png b/docs/images/how-to-use-lifecycle-job/11.png
deleted file mode 100644
index 3128f9d..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/11.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/12.png b/docs/images/how-to-use-lifecycle-job/12.png
deleted file mode 100644
index 37dfc8b..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/12.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/13.png b/docs/images/how-to-use-lifecycle-job/13.png
deleted file mode 100644
index dd06e92..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/13.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/14.png b/docs/images/how-to-use-lifecycle-job/14.png
deleted file mode 100644
index dfce54c..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/14.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/15.png b/docs/images/how-to-use-lifecycle-job/15.png
deleted file mode 100644
index 5061352..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/15.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/16.png b/docs/images/how-to-use-lifecycle-job/16.png
deleted file mode 100644
index 200a47a..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/16.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/2.png b/docs/images/how-to-use-lifecycle-job/2.png
deleted file mode 100644
index 95be050..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/2.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/3.png b/docs/images/how-to-use-lifecycle-job/3.png
deleted file mode 100644
index afef24e..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/3.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/4.png b/docs/images/how-to-use-lifecycle-job/4.png
deleted file mode 100644
index 57c3c8b..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/4.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/5.png b/docs/images/how-to-use-lifecycle-job/5.png
deleted file mode 100644
index ee3d83d..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/5.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/6.png b/docs/images/how-to-use-lifecycle-job/6.png
deleted file mode 100644
index 6b82c98..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/6.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/7.png b/docs/images/how-to-use-lifecycle-job/7.png
deleted file mode 100644
index b0fbfce..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/7.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/8.png b/docs/images/how-to-use-lifecycle-job/8.png
deleted file mode 100644
index 5f5eb21..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/8.png and /dev/null differ
diff --git a/docs/images/how-to-use-lifecycle-job/9.png b/docs/images/how-to-use-lifecycle-job/9.png
deleted file mode 100644
index f4f885e..0000000
Binary files a/docs/images/how-to-use-lifecycle-job/9.png and /dev/null differ
diff --git a/docs/images/install-qovery/aws/create-credentials.png b/docs/images/install-qovery/aws/create-credentials.png
index c3a195f..c5282e3 100644
Binary files a/docs/images/install-qovery/aws/create-credentials.png and b/docs/images/install-qovery/aws/create-credentials.png differ
diff --git a/docs/images/install-qovery/common/add-cluster.png b/docs/images/install-qovery/common/add-cluster.png
index dfa9e1a..df7bc16 100644
Binary files a/docs/images/install-qovery/common/add-cluster.png and b/docs/images/install-qovery/common/add-cluster.png differ
diff --git a/docs/images/install-qovery/common/list-azure-clusters.png b/docs/images/install-qovery/common/list-azure-clusters.png
index cd1d883..204d8c7 100644
Binary files a/docs/images/install-qovery/common/list-azure-clusters.png and b/docs/images/install-qovery/common/list-azure-clusters.png differ
diff --git a/docs/images/install-qovery/common/list-clusters.png b/docs/images/install-qovery/common/list-clusters.png
index 24456f2..c24f3a3 100644
Binary files a/docs/images/install-qovery/common/list-clusters.png and b/docs/images/install-qovery/common/list-clusters.png differ
diff --git a/docs/images/integration/webhook/webhook_access.png b/docs/images/integration/webhook/webhook_access.png
index 7b80da1..382b70a 100644
Binary files a/docs/images/integration/webhook/webhook_access.png and b/docs/images/integration/webhook/webhook_access.png differ
diff --git a/docs/images/integrations/ci-cd/github-actions/step-1.png b/docs/images/integrations/ci-cd/github-actions/step-1.png
index 4976031..9388107 100644
Binary files a/docs/images/integrations/ci-cd/github-actions/step-1.png and b/docs/images/integrations/ci-cd/github-actions/step-1.png differ
diff --git a/docs/images/integrations/ci-cd/github-actions/step-2.png b/docs/images/integrations/ci-cd/github-actions/step-2.png
index d9eaa4a..090e00a 100644
Binary files a/docs/images/integrations/ci-cd/github-actions/step-2.png and b/docs/images/integrations/ci-cd/github-actions/step-2.png differ
diff --git a/docs/images/kubecost/add-port.png b/docs/images/kubecost/add-port.png
index be06e32..a064166 100644
Binary files a/docs/images/kubecost/add-port.png and b/docs/images/kubecost/add-port.png differ
diff --git a/docs/images/kubecost/link.png b/docs/images/kubecost/link.png
index 93518f8..c698425 100644
Binary files a/docs/images/kubecost/link.png and b/docs/images/kubecost/link.png differ
diff --git a/docs/images/kubecost/service-name.png b/docs/images/kubecost/service-name.png
deleted file mode 100644
index 9d88b2a..0000000
Binary files a/docs/images/kubecost/service-name.png and /dev/null differ
diff --git a/docs/images/kubernetes-observability-and-monitoring-with-datadog/datadog-pods.png b/docs/images/kubernetes-observability-and-monitoring-with-datadog/datadog-pods.png
index ab8fad5..ff0a437 100644
Binary files a/docs/images/kubernetes-observability-and-monitoring-with-datadog/datadog-pods.png and b/docs/images/kubernetes-observability-and-monitoring-with-datadog/datadog-pods.png differ
diff --git a/docs/images/kubernetes-observability-and-monitoring-with-datadog/datadog-secret.png b/docs/images/kubernetes-observability-and-monitoring-with-datadog/datadog-secret.png
index f955dc8..7216d7e 100644
Binary files a/docs/images/kubernetes-observability-and-monitoring-with-datadog/datadog-secret.png and b/docs/images/kubernetes-observability-and-monitoring-with-datadog/datadog-secret.png differ
diff --git a/docs/images/kubernetes-observability-and-monitoring-with-datadog/deploy.png b/docs/images/kubernetes-observability-and-monitoring-with-datadog/deploy.png
index f84b715..1096059 100644
Binary files a/docs/images/kubernetes-observability-and-monitoring-with-datadog/deploy.png and b/docs/images/kubernetes-observability-and-monitoring-with-datadog/deploy.png differ
diff --git a/docs/images/micro/micros-1.png b/docs/images/micro/micros-1.png
index 547255a..90ca32e 100644
Binary files a/docs/images/micro/micros-1.png and b/docs/images/micro/micros-1.png differ
diff --git a/docs/images/observability/alert-conditions-configuration.png b/docs/images/observability/alert-conditions-configuration.png
index 34bec4b..d1dcb28 100644
Binary files a/docs/images/observability/alert-conditions-configuration.png and b/docs/images/observability/alert-conditions-configuration.png differ
diff --git a/docs/images/observability/alerts-overview.png b/docs/images/observability/alerts-overview.png
index 1dda4d9..6030e88 100644
Binary files a/docs/images/observability/alerts-overview.png and b/docs/images/observability/alerts-overview.png differ
diff --git a/docs/images/observability/create-alert.png b/docs/images/observability/create-alert.png
index a6ba11b..48d97d5 100644
Binary files a/docs/images/observability/create-alert.png and b/docs/images/observability/create-alert.png differ
diff --git a/docs/images/observability/events.png b/docs/images/observability/events.png
index 5828da4..48535a3 100644
Binary files a/docs/images/observability/events.png and b/docs/images/observability/events.png differ
diff --git a/docs/images/observability/issues-overview.png b/docs/images/observability/issues-overview.png
index 6365245..db54713 100644
Binary files a/docs/images/observability/issues-overview.png and b/docs/images/observability/issues-overview.png differ
diff --git a/docs/images/observability/network.png b/docs/images/observability/network.png
index fb50eec..6c024e3 100644
Binary files a/docs/images/observability/network.png and b/docs/images/observability/network.png differ
diff --git a/docs/images/observability/overview.png b/docs/images/observability/overview.png
index 09bc38a..874f414 100644
Binary files a/docs/images/observability/overview.png and b/docs/images/observability/overview.png differ
diff --git a/docs/images/observability/resources.png b/docs/images/observability/resources.png
index ad1670b..30a5605 100644
Binary files a/docs/images/observability/resources.png and b/docs/images/observability/resources.png differ
diff --git a/docs/images/open-env-var.png b/docs/images/open-env-var.png
index 0dd1ac1..f9f9a94 100644
Binary files a/docs/images/open-env-var.png and b/docs/images/open-env-var.png differ
diff --git a/docs/images/qovery_cloud_shell.png b/docs/images/qovery_cloud_shell.png
index e368ea1..b9227d6 100644
Binary files a/docs/images/qovery_cloud_shell.png and b/docs/images/qovery_cloud_shell.png differ
diff --git a/docs/images/rust/rust.png b/docs/images/rust/rust.png
index c8d962e..7d4db98 100644
Binary files a/docs/images/rust/rust.png and b/docs/images/rust/rust.png differ
diff --git a/docs/images/scaleway-credentials/create-credentials.png b/docs/images/scaleway-credentials/create-credentials.png
index 722beec..fbfdd34 100644
Binary files a/docs/images/scaleway-credentials/create-credentials.png and b/docs/images/scaleway-credentials/create-credentials.png differ
diff --git a/docs/images/slack/notification-channel-setup.png b/docs/images/slack/notification-channel-setup.png
index f5bb662..5b0bb4a 100644
Binary files a/docs/images/slack/notification-channel-setup.png and b/docs/images/slack/notification-channel-setup.png differ
diff --git a/docs/images/troubleshoot/custom-domain-configuration.png b/docs/images/troubleshoot/custom-domain-configuration.png
index 81ec32c..030eb54 100644
Binary files a/docs/images/troubleshoot/custom-domain-configuration.png and b/docs/images/troubleshoot/custom-domain-configuration.png differ
diff --git a/docs/images/troubleshoot/domain_check_error.png b/docs/images/troubleshoot/domain_check_error.png
index 20b19c6..781fe54 100644
Binary files a/docs/images/troubleshoot/domain_check_error.png and b/docs/images/troubleshoot/domain_check_error.png differ
diff --git a/docs/snippets/aws-credentials.mdx b/docs/snippets/aws-credentials.mdx
new file mode 100644
index 0000000..593941f
--- /dev/null
+++ b/docs/snippets/aws-credentials.mdx
@@ -0,0 +1,13 @@
+import AwsCredentialsSts from "/snippets/aws-credentials-sts.mdx";
+import AwsCredentialsStatic from "/snippets/aws-credentials-static.mdx";
+
+Qovery needs credentials to manage resources in your AWS account. Choose your preferred method:
+
+<Tabs>
+  <Tab title="STS Assume Role (Recommended)">
+    <AwsCredentialsSts />
+  </Tab>
+  <Tab title="Static Keys">
+    <AwsCredentialsStatic />
+  </Tab>
+</Tabs>
diff --git a/docs/snippets/azure-credentials.mdx b/docs/snippets/azure-credentials.mdx
index c51e40d..0f29bc8 100644
--- a/docs/snippets/azure-credentials.mdx
+++ b/docs/snippets/azure-credentials.mdx
@@ -34,7 +34,7 @@ Qovery needs credentials to manage resources in your Azure subscription. We use
 <Steps>
   <Step title="Start Cluster Creation">
     1. Go to [Qovery Console](https://console.qovery.com)
-    2. Click **Clusters** in the left sidebar
+    2. Go to your organization overview and click on the **Clusters** tab
     3. Click **Create Cluster**
     4. Select **Azure** as the cloud provider
   </Step>
diff --git a/docs/snippets/gcp-credentials.mdx b/docs/snippets/gcp-credentials.mdx
index 17643de..7dbf318 100644
--- a/docs/snippets/gcp-credentials.mdx
+++ b/docs/snippets/gcp-credentials.mdx
@@ -15,6 +15,7 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
     <Tip>
     Use a dedicated project for Qovery to keep resources organized and costs trackable.
     </Tip>
+
   </Step>
 
   <Step title="Note Your Project ID">
@@ -25,6 +26,7 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
     <Info>
     You'll need this Project ID in the next steps.
     </Info>
+
   </Step>
 </Steps>
 
@@ -33,7 +35,7 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
 <Steps>
   <Step title="Start Cluster Creation">
     1. Go to [Qovery Console](https://console.qovery.com)
-    2. Click **Clusters** in the left sidebar
+    2. Go to **Clusters** tab
     3. Click **Create Cluster**
     4. Select **GCP** as the cloud provider
   </Step>
@@ -43,6 +45,7 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
     2. Click **Next**
 
     Qovery will generate a secure installation command for you.
+
   </Step>
 
   <Step title="Copy the Command">
@@ -50,12 +53,13 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
 
     The command will look like:
     ```bash
-    curl https://hub.qovery.com/files/create_credentials_gcp.sh | bash -s -- YOUR_PROJECT_ID qovery_role qovery-service-account
+    curl https://setup.qovery.com/create_credentials_gcp.sh | bash -s -- YOUR_PROJECT_ID qovery_role qovery-service-account
     ```
 
     <Info>
     This script creates a service account with minimal required permissions.
     </Info>
+
   </Step>
 </Steps>
 
@@ -70,6 +74,7 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
     <Frame>
       <img src="/images/gcp-credentials/cloud-shell.png" alt="Open Google Cloud Shell" />
     </Frame>
+
   </Step>
 
   <Step title="Run the Command">
@@ -96,6 +101,7 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
     created key [abc123...] of type [json] as [key.json]
     ✓ Credentials configured successfully
     ```
+
   </Step>
 
   <Step title="Download the Key File">
@@ -111,6 +117,7 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
     <Warning>
     **Keep this JSON key file secure!** It provides access to your GCP project. Never commit it to version control.
     </Warning>
+
   </Step>
 
   <Step title="Upload to Qovery">
@@ -125,6 +132,7 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
     <Tip>
     You can reuse these credentials for multiple clusters in the same GCP project.
     </Tip>
+
   </Step>
 </Steps>
 
@@ -140,12 +148,16 @@ Qovery needs credentials to manage resources in your GCP project. We use a secur
     - **Cloud Run**: Manage serverless deployments (optional)
 
     The installation script automatically assigns the minimum required roles to the service account.
-  </Accordion>
 
-  <Accordion title="Can I use a custom service account?">
-    Yes! You can create a service account manually with custom permissions. However, ensure it has all the roles required for managing GKE, Compute Engine, and networking resources. Contact support for the minimal permissions list.
   </Accordion>
 
+<Accordion title="Can I use a custom service account?">
+  Yes! You can create a service account manually with custom permissions.
+  However, ensure it has all the roles required for managing GKE, Compute
+  Engine, and networking resources. Contact support for the minimal permissions
+  list.
+</Accordion>
+
   <Accordion title="How do I rotate credentials?">
     To rotate GCP credentials:
     1. In GCP Console, go to **IAM & Admin** → **Service Accounts**
diff --git a/docs/snippets/scaleway-credentials.mdx b/docs/snippets/scaleway-credentials.mdx
index b134600..ce2516f 100644
--- a/docs/snippets/scaleway-credentials.mdx
+++ b/docs/snippets/scaleway-credentials.mdx
@@ -88,7 +88,7 @@ Qovery needs API credentials to manage resources in your Scaleway account. We us
 <Steps>
   <Step title="Start Cluster Creation">
     1. Go to [Qovery Console](https://console.qovery.com)
-    2. Click **Clusters** in the left sidebar
+    2. Go to your organization overview and click on the **Clusters** tab
     3. Click **Create Cluster**
     4. Select **Scaleway** as the cloud provider
   </Step>