docs(feat): Deployment freeze CDAAS-2918

content/en/deployment/deployment-freeze/overview.md

@@ -0,0 +1,23 @@
+---
+title: How to Freeze Deployments
+linkTitle: Freeze Deployments
+weight: 10
+description: >
+  Freeze your individual deployments or deployments by account.
+---
+
+<!-- put images in this folder -->
+
+## Overview of freezing deployments
+
+CD-as-a-Service enables blocking the release of some or all applications to some or all accounts. In case of a bad change being shipped out, you  can block further deployments of specific applications to specific accounts. You have the flexibility to make sweeping changes like disabling deployments of all applications to all environments, or you could perform precision blocking, such as 2 applications on 1 production account.  You block and unblock deployments from within the CD-as-a-Service UI, thereby removing the need to actually maintain this configuration on your own. 
+
+### Key features
+
+* **Pause Deployments**: You can initiate a temporary deployment block for selected applications to selected accounts, ensuring that no updates are deployed during critical periods using the UI. 
+* **Block Accounts**: You can choose to block deployments to specific accounts so that they can continue to deploy without having to write a custom deploy file. 
+* **View Change History**: You can easily view the history of who made a change to block or unblock deployments, as well as what the change was.
+
+## How to freeze 
+
+- filter, sort

content/en/deployment/overview.md → content/en/deployment/overview/index.md

@@ -16,7 +16,7 @@ You define your CD-as-a-Service deployment configuration in a YAML file, which y
 
 ## How deployment works
 
-{{< figure src="/images/cdaas/deploy/deploy-overview.jpg" width=80%" height="80%" >}}
+{{< figure src="deploy-overview.jpg" width=80%" height="80%" >}}
 
 * CD-as-a-Service starts a deployment with an environment, such as development, that does not depend on another environment. Then deployment progresses through the steps, conditions, and environments defined in your deployment process. 
 * CD-as-a-Service deploys a new ReplicaSet every time a deployment is started. This ensures changes to resources like ConfigMap are immediately reflected and validated with your deployment strategy. 
@@ -34,7 +34,11 @@ You define your CD-as-a-Service deployment configuration in a YAML file, which y
 
 > CD-as-a-Service deploys any Kubernetes manifest to your environments without the need for any special annotations in the manifest.
 
-### How to trigger a deployment
+### Deployment freeze
+
+You can implement a deployment freeze on individual apps or all apps in an account.
+
+## How to trigger a deployment
 
 * [Use the GitHub Action]({{< ref "integrations/ci-systems/gh-action" >}}) in your GitHub workflow.
 * [Use the CLI]({{< ref "cli" >}}) with any CI system by installing the CLI natively or running it in Docker.