Docs - V1: Update Overview

docs/content/en/docs-v1.0.x/overview/_index.md

@@ -6,7 +6,7 @@ description: >
   Overview about PipeCD.
 ---
 
-![](/images/pipecd-explanation.png)
+![PipeCD explaination](/images/pipecd-explanation.png)
 <p style="text-align: center;">
 PipeCD - a GitOps style continuous delivery solution
 </p>
@@ -20,7 +20,8 @@ PipeCD provides a unified continuous delivery solution for multiple application
 ## Why PipeCD?
 
 - Simple, unified and easy to use but powerful pipeline definition to construct your deployment
-- Same deployment interface to deploy applications of any platform, including Kubernetes, Terraform, GCP Cloud Run, AWS Lambda, AWS ECS
+- Same deployment interface to deploy applications of any platform, including Kubernetes, Terraform, GCP Cloud Run, AWS Lambda, AWS ECS and more.
+- Offers extensibility with a plugin-architecture, allowing users to create plugins and deploy custom applications
 - No CRD or applications' manifest changes are required; Only need a pipeline definition along with your application manifests
 - No deployment credentials are exposed or required outside the application cluster
 - Built-in deployment analysis as part of the deployment pipeline to measure impact based on metrics, logs, emitted requests
@@ -31,26 +32,30 @@ PipeCD provides a unified continuous delivery solution for multiple application
 ## PipeCD's Characteristics in detail
 
 **Visibility**
+
 - Deployment pipeline UI shows clarify what is happening
 - Separate logs viewer for each individual deployment
 - Realtime visualization of application state
 - Deployment notifications to slack, webhook endpoints
 - Insights show metrics like lead time, deployment frequency, MTTR and change failure rate to measure delivery performance
 
 **Automation**
+
 - Automated deployment analysis to measure deployment impact based on metrics, logs, emitted requests
 - Automatically roll back to the previous state as soon as analysis or a pipeline stage fails
 - Automatically detect configuration drift to notify and render the changes
 - Automatically trigger a new deployment when a defined event has occurred (e.g. container image pushed, helm chart published, etc)
 
 **Safety and Security**
+
 - Support single sign-on and role-based access control
 - Credentials are not exposed outside the cluster and not saved in the Control Plane
 - Piped makes only outbound requests and can run inside a restricted network
 - Built-in secrets management
 
 **Multi-provider & Multi-Tenancy**
-- Support multiple application kinds on multi-cloud including Kubernetes, Terraform, Cloud Run, AWS Lambda, Amazon ECS
+
+- Support multiple application kinds on multi-cloud including Kubernetes, Terraform, Cloud Run, AWS Lambda, Amazon ECS and more with plugins.
 - Support multiple analysis providers including Prometheus, Datadog, Stackdriver, and more
 - Easy to operate multi-cluster, multi-tenancy by separating Control Plane and Piped
 
@@ -62,17 +67,21 @@ PipeCD provides a unified continuous delivery solution for multiple application
 ## Where should I go next?
 
 For a good understanding of the PipeCD's components.
+
 - [Concepts](../concepts): describes each components.
 - [FAQ](../faq): describes the difference between PipeCD and other tools.
 
 If you are an **operator** wanting to install and configure PipeCD for other developers.
+
 - [Quickstart](../quickstart/)
 - [Managing Control Plane](../user-guide/managing-controlplane/)
 - [Managing Piped](../user-guide/managing-piped/)
 
 If you are a **user** using PipeCD to deploy your application/infrastructure:
+
 - [User Guide](../user-guide/)
 - [Examples](../user-guide/examples)
 
 If you want to be a **contributor**:
+
 - [Contributor Guide](../contribution-guidelines/)