Add next&previous links in each page

Signed-off-by: t-kikuc <[email protected]>

Author: t-kikuc

content/en/10-overview/README.md

@@ -36,4 +36,8 @@ PipeCD is made up of two components - **Control Plane** and **Piped (Agent)**.
 ## See Also
 
 - [Docs > Overview](https://pipecd.dev/docs/overview/)
-- [Docs > Concepts](https://pipecd.dev/docs/concepts/)
+- [Docs > Concepts](https://pipecd.dev/docs/concepts/)
+
+---
+
+[Next: Prerequisites >](../20-prerequisites/README.md)

content/en/20-prerequisites/README.md

@@ -26,3 +26,9 @@ To perform this tutorial, you need the following:
       - function’s execution role
   - for **Terraform**:
     - You can execute [`terraform` commands](https://developer.hashicorp.com/terraform/cli/commands) on local.
+
+---
+
+[Next: Install >](../30-install/README.md)
+
+[< Previous: Mechanism Overview](../10-overview/README.md)

content/en/30-install/01-git.md

@@ -24,3 +24,8 @@ It contains configs for the installation and deployments.
     ```
 
 
+---
+
+[Next: 2. Install Control Plane >](02-control-plane.md)
+
+[< Previous: Install](README.md)

content/en/30-install/02-control-plane.md

@@ -47,4 +47,10 @@ In this page, you will install a Control Plane on local by `docker-compose`.
 
 - [Architecture Overview](https://pipecd.dev/docs/user-guide/managing-controlplane/architecture-overview/)
 - [Managing Control Plane](https://pipecd.dev/docs/user-guide/managing-controlplane/)
-- [Installing Control Plane on Kubernetes](https://pipecd.dev/docs/installation/install-control-plane/installing-controlplane-on-k8s/)
+- [Installing Control Plane on Kubernetes](https://pipecd.dev/docs/installation/install-control-plane/installing-controlplane-on-k8s/)
+
+---
+
+[Next: 3. Install Piped >](03-piped.md)
+
+[< Previous: 1. Setup Git Repository](01-git.md)

content/en/30-install/03-piped.md

@@ -17,7 +17,7 @@ In this page, you will run a Piped agent on local as a single binary.
    1-4. You will see the Piped's ID and Key. **You will use them in the following steps.**
     ![Piped is registered](/images/install/piped-registered.png)
 
-2. Move on to the directory you cloned in [1. Setup Git Repository](git.md).
+2. Move on to the directory you cloned in [1. Setup Git Repository](01-git.md).
 
    ```console
    cd <YOUR_CLONED_TUTORIAL_DIR>
@@ -94,3 +94,9 @@ In this page, you will run a Piped agent on local as a single binary.
 [^1]: Do **NOT** push a Piped Key to remote because it is a credential. In actual use, you should store it and `piped.yaml` in a secret management tool.
 
 [^2]: `--insecure` option disables TLS of the communication from the Piped to the Control Plane. (cf. [Piped's Runtime Options](https://pipecd.dev/docs/user-guide/managing-piped/runtime-options/))
+
+---
+
+[Next: Deploy >](../40-deploy/README.md)
+
+[< Previous: 2. Install Control Plane](02-control-plane.md)

content/en/30-install/README.md

@@ -3,4 +3,16 @@
 In this chapter, you will run a Control Plane and a Piped locally.
 
 ![Installation flow](/images/install/installation-flow.svg)
-<p align="center">Installation flow</p>
+<p align="center">Installation flow</p>
+
+---
+
+[Next: Setup Git Repository >](01-git.md)
+
+[< Previous: Prerequisites](../20-prerequisites/README.md)
+
+---
+
+[Next: 1. Setup Git Repository >](01-git.md)
+
+[< Previous: Prerequisites](../20-prerequisites/README.md)

content/en/40-deploy/01-simply.md

@@ -86,3 +86,9 @@ In this page, you will deploy an application to your platform in a simple way.
 4-3. Go to the deployments page again. [http://localhost:8080/deployments](http://localhost:8080/deployments)
 
 4-4. A new deployment will start in a few minutes.
+
+---
+
+[Next: Deploy with a Customized Pipeline >](02-pipeline.md)
+
+[< Previous: Deploy](README.md)

content/en/40-deploy/02-pipeline.md

@@ -2,7 +2,7 @@
 
 In this page, you will deploy with a customized pipeline like Canary release.
 
-_The process is almost the same as [1. Deploy Simply](deploy.md). Only the config files (essentially only `app.pipecd.yaml`) are different._
+_The process is almost the same as [1. Deploy Simply](01-simply.md). Only the config files (essentially only `app.pipecd.yaml`) are different._
 
 ## 1. Prepare config files
 
@@ -72,3 +72,7 @@ _The process is almost the same as [1. Deploy Simply](deploy.md). Only the confi
 - [Configuration examples](https://github.com/pipe-cd/examples)
 - [Customizing deployment](https://pipecd.dev/docs/user-guide/managing-application/customizing-deployment/)
 - [Configuration Reference > Stage options](https://pipecd.dev/docs/user-guide/configuration-reference/#stageoptions)
+
+---
+
+[< Previous: 1. Deploy Simply](01-simply.md)

content/en/40-deploy/README.md

@@ -10,4 +10,10 @@ The deployment flow is like this:
 4. Your Piped deploys.
 
 ![deployment flow](/images/deploy/deployment-flow.svg)
-<p align="center">Deployment flow</p>
+<p align="center">Deployment flow</p>
+
+---
+
+[Next: 1. Deploy Simply >](01-simply.md)
+
+[< Previous: 3. Install Piped](../30-install/03-piped.md)