Init PipeCD Docs for PipeCD v1

docs/config.toml

@@ -167,6 +167,10 @@ no = 'Sorry to hear that. Please <a href="https://github.com/pipe-cd/pipecd/issu
   githubbranch = "master"
   url = "/docs-dev/"
 
+[[params.versions]]
+  version = "v1.0.x"
+  url = "/docs-v1.0.x/"
+
 [[params.versions]]
   version = "v0.55.x"
   url = "/docs-v0.55.x/"

docs/content/en/_index.html

@@ -10,7 +10,7 @@
         The One CD for All {applications, platforms, operations}
     </p>
     <p class="h5 long-description">
-        A GitOps style continuous delivery platform that provides <br/> consistent deployment and operations experience for any applications
+        A GitOps style continuous delivery platform that provides <br/> consistent deployment and operations experience for any application.
     </p>
 </div>
 
@@ -24,11 +24,15 @@
 	<a class="btn btn-lg btn-secondary mr-3 mb-4" target="_blank" href="https://github.com/pipe-cd/pipecd">
 		GitHub <i class="fab fa-github ml-2 "></i>
 	</a>
+    <!-- <a class="btn btn-lg btn-primary mr-3 mb-4" href="https://pipecd.dev/docs-v1.0.x/">
+    Learn about PipeCD v1 <i class="fas fa-arrow-alt-circle-right ml-2"></i>
+</a> -->
+
 </div>
 
 <div class="mx-auto">
 	<a class="release-panel" target="_blank" href="https://github.com/pipe-cd/pipecd/releases">
-		PipeCD <span class="bolder">{{< blocks/latest_version >}}</span> is now available
+		PipeCD <span class="bolder">{{< blocks/latest_version >}}</span> is now available! Check out the release notes <i class="fas fa-arrow-alt-circle-right ml-2"></i>
 	</a>
 </div>
 {{< /blocks/cover >}}

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

@@ -0,0 +1,5 @@
+---
+title: "Welcome to PipeCD"
+linkTitle: "Documentation [v1.0.x]"
+type: docs
+---

docs/content/en/docs-v1.0.x/contribution-guidelines/_index.md

@@ -0,0 +1,7 @@
+---
+title: "Contributor Guide"
+linkTitle: "Contributor Guide"
+weight: 6
+description: >
+  This guide is for anyone who want to contribute to PipeCD project. We are so excited to have you!
+---

docs/content/en/docs-v1.0.x/contribution-guidelines/architectural-overview.md

@@ -0,0 +1,36 @@
+---
+title: "Architectural overview"
+linkTitle: "Architectural overview"
+weight: 3
+description: >
+  This page describes the architecture of PipeCD.
+---
+
+![](/images/architecture-overview.png)
+<p style="text-align: center;">
+Component Architecture
+</p>
+
+### Piped
+
+A single binary component runs in your cluster, your local network to handle the deployment tasks.
+It can be run inside a Kubernetes cluster by simply starting a Pod or a Deployment.
+This component is designed to be stateless, so it can also be run in a single VM or even your local machine.
+
+### Control Plane
+
+A centralized component manages deployment data and provides gRPC API for connecting `piped`s as well as all web-functionalities of PipeCD such as
+authentication, showing deployment list/details, application list/details, delivery insights...
+
+Control Plane contains the following components:
+- `server`: a service to provide api for piped, web and serve static assets for web.
+- `ops`: a service to provide administrative features for Control Plane owner like adding/managing projects.
+- `cache`: a redis cache service for caching internal data.
+- `datastore`: data storage for storing deployment, application data
+  - this can be a fully-managed service such as `Firestore`, `Cloud SQL`...
+  - or a self-managed such as `MySQL`
+- `filestore`: file storage for storing logs, application states
+  - this can a fully-managed service such as `GCS`, `S3`...
+  - or a self-managed service such as `Minio`
+
+For more information, see [Architecture overview of Control Plane](../../user-guide/managing-controlplane/architecture-overview/).

docs/content/en/docs-v1.0.x/contribution-guidelines/contributing.md

@@ -0,0 +1,9 @@
+---
+title: "Contributing"
+linkTitle: "Contributing"
+weight: 1
+description: >
+  This page describes how to contribute to PipeCD.
+---
+
+PipeCD is an open source project that anyone in the community can use, improve, and enjoy. We'd love you to join us! [Contributing to PipeCD](https://github.com/pipe-cd/pipecd/tree/master/CONTRIBUTING.md) is the best place to start with.

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

@@ -0,0 +1,66 @@
+---
+title: "FAQ"
+linkTitle: "FAQ"
+weight: 10
+description: >
+  List of frequently asked questions.
+---
+
+If you have any other questions, please feel free to create the issue in the [pipe-cd/pipecd](https://github.com/pipe-cd/pipecd/issues/new/choose) repository or contact us on [Cloud Native Slack](https://slack.cncf.io) (channel [#pipecd](https://app.slack.com/client/T08PSQ7BQ/C01B27F9T0X)).
+
+### 1. What kind of application (platform provider) will be supported?
+
+Currently, PipeCD can be used to deploy `Kubernetes`, `ECS`, `Terraform`, `CloudRun`, `Lambda` applications.
+
+In the near future we also want to support `Crossplane`...
+
+### 2. What kind of templating methods for Kubernetes application will be supported?
+
+Currently, PipeCD is supporting `Helm` and `Kustomize` as templating method for Kubernetes applications.
+
+### 3. Istio is supported now?
+
+Yes, you can use PipeCD for both mesh (Istio, SMI) applications and non-mesh applications.
+
+### 4. What are the differences between PipeCD and FluxCD?
+
+- Not just Kubernetes applications, PipeCD also provides a unified interface for other cloud services (CloudRun, AWS Lamda...) and Terraform
+- One tool for both GitOps sync and progressive deployment
+- Supports multiple Git repositories
+- Has web UI for better visibility
+    - Log viewer for each deployment
+    - Visualization of application component/state in realtime
+    - Show configuration drift in realtime
+- Also supports Canary and BlueGreen for non-mesh applications
+- Has built-in secrets management
+- Shows the delivery performance  insights
+
+### 5. What are the differences between PipeCD and ArgoCD?
+
+- Not just Kubernetes applications, PipeCD also provides a unified interface for other cloud services (GCP CloudRun, AWS Lamda...) and Terraform
+- One tool for both GitOps sync and progressive deployment
+- Don't need another CRD or changing the existing manifests for doing Canary/BlueGreen. PipeCD just uses the standard Kubernetes deployment object
+- Easier and safer to operate multi-tenancy, multi-cluster for multiple teams (even some teams are running in a private/restricted network)
+- Has built-in secrets management
+- Shows the delivery performance  insights
+
+### 6. What should I do if I lost my Piped key?
+
+You can create a new Piped key. Go to the `Piped` tab at `Settings` page, and click the vertical ellipsis of the Piped that you would like to create the new Piped key. Don't forget deleting the old Key, too.
+
+### 7. What is the strong point if PipeCD is used only for Kubernetes?
+
+- Simple interface, easy to understand no extra CRD required
+- Easy to install, upgrade, and manage (both the ControlPlane and the agent Piped)
+- Not strict depend on any Kubernetes API, not being part of issues for your Kubernetes cluster versioning upgrade
+- Easy to interact with any CI; Plan preview feature gives you an early look at what will be changed in your cluster even before manifests update
+- Insights show metrics like lead time, deployment frequency, MTTR, and change failure rate to measure delivery performance
+
+### 8. Is it open source?
+
+Yes, PipeCD is fully open source project with APACHE LICENSE, VERSION 2.0!!
+
+### 9. How should I investigate high CPU usage or memory usage in piped, or when OOM occurs?
+
+If you're noticing high CPU usage, memory usage, or facing OOM issues in Piped, you can use the built-in support for `pprof`, a tool for visualization and analysis of profiling data.  
+`pprof` can help you identify the parts of your application that are consuming the most resources. For more detailed information and examples of how to use `pprof` in Piped, please refer to our [Using Pprof in Piped guide](../managing-piped/using-pprof-in-piped).