renames user guides to tasks, #3098

Signed-off-by: Eitan Suez <eitan@tetrate.io>

site/content/en/latest/contributions/DEVELOP.md

@@ -140,24 +140,24 @@ There are many other endpoints on the [Envoy admin interface][] that may be help
 ### JWT Testing
 
 An example [JSON Web Token (JWT)][jwt] and [JSON Web Key Set (JWKS)][jwks] are used for the [request authentication][]
-user guide. The JWT was created by the [JWT Debugger][], using the `RS256` algorithm. The public key from the JWTs
+task. The JWT was created by the [JWT Debugger][], using the `RS256` algorithm. The public key from the JWTs
 verify signature was copied to [JWK Creator][] for generating the JWK. The JWK Creator was configured with matching
 settings, i.e. `Signing` public key use and the `RS256` algorithm. The generated JWK was wrapped in a JWKS structure
 and is hosted in the repo.
 
-[Quickstart]: https://github.com/envoyproxy/gateway/blob/main/docs/latest/user/quickstart.md
+[Quickstart]: https://github.com/envoyproxy/gateway/blob/main/docs/latest/tasks/quickstart.md
 [make]: https://www.gnu.org/software/make/
 [Github Actions]: https://docs.github.com/en/actions
 [workflows]: https://github.com/envoyproxy/gateway/tree/main/.github/workflows
 [Kind]: https://kind.sigs.k8s.io/
 [conformance homepage]: https://gateway-api.sigs.k8s.io/concepts/conformance/
-[directly exposing]: https://kind.sigs.k8s.io/docs/user/loadbalancer/
+[directly exposing]: https://kind.sigs.k8s.io/docs/tasks/loadbalancer/
 [Kubernetes support]: https://docs.docker.com/desktop/kubernetes/
 [gateway-dev]: https://hub.docker.com/r/envoyproxy/gateway-dev/tags
 [mac_connect]: https://github.com/chipmk/docker-mac-net-connect
 [Envoy admin interface]: https://www.envoyproxy.io/docs/envoy/latest/operations/admin#operations-admin-interface
 [jwt]: https://tools.ietf.org/html/rfc7519
 [jwks]: https://tools.ietf.org/html/rfc7517
-[request authentication]: ../user/security/jwt-authentication
+[request authentication]: ../tasks/security/jwt-authentication
 [JWT Debugger]: https://jwt.io/
 [JWK Creator]: https://russelldavies.github.io/jwk-creator/

site/content/en/latest/contributions/DOCS.md

@@ -54,7 +54,7 @@ make docs-release TAG=v0.6.0
 This will update the VERSION file at the project root, which records current release version,
 and it will be used in the pages version context and binary version output. Also, this will generate
 new dir `site/content/en/v0.6.0`, which contains docs at v0.6.0 and updates artifact links to `v0.6.0`
-in all files under `site/content/en/v0.6.0/user`, like `quickstart.md`, `http-routing.md` and etc.
+in all files under `site/content/en/v0.6.0/tasks`, like `quickstart.md`, `http-routing.md` and etc.
 
 ## Publishing Docs
 

site/content/en/latest/contributions/RELEASING.md

@@ -6,7 +6,10 @@ description: "This section tells the release process of Envoy Gateway."
 This document guides maintainers through the process of creating an Envoy Gateway release.
 
 - [Release Candidate](#release-candidate)
+  - [Prerequisites](#prerequisites)
+  - [Setup cherry picker action](#setup-cherry-picker-action)
 - [Minor Release](#minor-release)
+  - [Prerequisites](#prerequisites-1)
 - [Announce the Release](#announce-the-release)
 
 ## Release Candidate
@@ -65,7 +68,7 @@ export GITHUB_REMOTE=origin
 13. Confirm that the [release workflow][] completed successfully.
 14. Confirm that the Envoy Gateway [image][] with the correct release tag was published to Docker Hub.
 15. Confirm that the [release][] was created.
-16. Note that the [Quickstart Guide][] references are __not__ updated for release candidates. However, test
+16. Note that the [Quickstart][] references are __not__ updated for release candidates. However, test
     the quickstart steps using the release candidate by manually updating the links.
 17. [Generate][] the GitHub changelog.
 18. Ensure you check the "This is a pre-release" checkbox when editing the GitHub release.
@@ -203,7 +206,7 @@ export GITHUB_REMOTE=origin
 10. Confirm that the [release workflow][] completed successfully.
 11. Confirm that the Envoy Gateway [image][] with the correct release tag was published to Docker Hub.
 12. Confirm that the [release][] was created.
-13. Confirm that the steps in the [Quickstart Guide][] work as expected.
+13. Confirm that the steps in the [Quickstart][] work as expected.
 14. [Generate][] the GitHub changelog and include the following text at the beginning of the release page:
 
    ```console
@@ -239,7 +242,7 @@ It's important that the world knows about the release. Use the following steps t
 
 [release notes]: https://github.com/envoyproxy/gateway/tree/main/release-notes
 [Pull Request]: https://github.com/envoyproxy/gateway/pulls
-[Quickstart Guide]: https://github.com/envoyproxy/gateway/blob/main/docs/user/quickstart.md
+[Quickstart]: https://github.com/envoyproxy/gateway/blob/main/docs/tasks/quickstart.md
 [Build and Test]: https://github.com/envoyproxy/gateway/blob/main/.github/workflows/build_and_test.yaml
 [release GitHub action]: https://github.com/envoyproxy/gateway/blob/main/.github/workflows/release.yaml
 [release workflow]: https://github.com/envoyproxy/gateway/actions/workflows/release.yaml

site/content/en/latest/contributions/design/envoy-patch-policy.md

@@ -172,5 +172,5 @@ patches will work.
 [EnvoyGateway]: ../../api/extension_types#envoygateway
 [Extending the Control Plane]: ./extending-envoy-gateway
 [EnvoyFilter]: https://istio.io/latest/docs/reference/config/networking/envoy-filter
-[egctl x translate]: ../../user/operations/egctl#egctl-experimental-translate
-[Bootstrap configuration using EnvoyProxy API]: ../../user/operations/customize-envoyproxy#customize-envoyproxy-bootstrap-config
+[egctl x translate]: ../../tasks/operations/egctl#egctl-experimental-translate
+[Bootstrap configuration using EnvoyProxy API]: ../../tasks/operations/customize-envoyproxy#customize-envoyproxy-bootstrap-config

site/content/en/latest/contributions/design/extending-envoy-gateway.md

@@ -316,7 +316,7 @@ Extending Envoy Gateway by using an external extension server which makes use of
 [Envoy specific configuration (xDS)]: https://www.envoyproxy.io/docs/envoy/v1.25.1/configuration/configuration
 [v1]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1
 [rate limiting]: ./rate-limit
-[authentication]: ../../user/security/jwt-authentication
+[authentication]: ../../tasks/security/jwt-authentication
 [HTTPRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1.HTTPRoute
 [GRPCRoute]: https://gateway-api.sigs.k8s.io/reference/spec/#gateway.networking.k8s.io/v1alpha2.GRPCRoute
 [EnvoyGateway config]: ../../api/extension_types/#envoygateway

site/content/en/latest/install/custom-cert.md

@@ -5,15 +5,15 @@ weight: -70
 
 Envoy Gateway establishes a secure TLS connection for control plane communication between Envoy Gateway pods and the Envoy Proxy fleet. The TLS Certificates used here are self signed and generated using a job that runs before envoy gateway is created, and these certs and mounted on to the envoy gateway and envoy proxy pods. 
 
-In this guide, we'll walk you through configuring custom certs for control plane auth.
+This task will walk you through configuring custom certs for control plane auth.
 
 ## Before you begin
 
 We use Cert-Manager to manage the certificates. You can install it by following the [official guide](https://cert-manager.io/docs/installation/kubernetes/).
 
 ## Configure custom certs for control plane
 
-1. First you need to set up the CA issuer, in this guide, we use the `selfsigned-issuer` as an example.
+1. First you need to set up the CA issuer, in this task, we use the `selfsigned-issuer` as an example.
 
    *You should not use the self-signed issuer in production, you should use a real CA issuer.*
 

site/content/en/latest/install/install-egctl.md

@@ -10,7 +10,7 @@ weight: -80
 {{% /alert %}}
 
 
-This guide shows how to install the egctl CLI. egctl can be installed either from source, or from pre-built binary releases.
+This task shows how to install the egctl CLI. egctl can be installed either from source, or from pre-built binary releases.
 
 ### From The Envoy Gateway Project
 
@@ -52,6 +52,6 @@ curl -fsSL https://gateway.envoyproxy.io/get-egctl.sh | VERSION=latest bash
 
 {{% alert title="Next Steps" color="warning" %}}
 
-You can refer to [User Guides](../user/operations/egctl) to more details about egctl.
+You can refer to the [Use egctl task](../tasks/operations/egctl) for more details about egctl.
 
 {{% /alert %}}

site/content/en/latest/install/install-helm.md

@@ -140,5 +140,5 @@ These are the ports used by Envoy Gateway and the managed Envoy Proxy.
 | Heath Check  | 0.0.0.0     | 19001   |
 
 {{% alert title="Next Steps" color="warning" %}}
-Envoy Gateway should now be successfully installed and running, but in order to experience more abilities of Envoy Gateway, you can refer to [User Guides](../user).
+Envoy Gateway should now be successfully installed and running.  To experience more abilities of Envoy Gateway, refer to [Tasks](../tasks).
 {{% /alert %}}

site/content/en/latest/install/install-yaml.md

@@ -3,7 +3,7 @@ title = "Install with Kubernetes YAML"
 weight = -99
 +++
 
-In this guide, we'll walk you through installing Envoy Gateway in your Kubernetes cluster.
+This task walks you through installing Envoy Gateway in your Kubernetes cluster.
 
 The manual install process does not allow for as much control over configuration
 as the [Helm install method](./install-helm), so if you need more control over your Envoy Gateway
@@ -36,4 +36,4 @@ Refer to the [Developer Guide](/latest/contributions/develop) to learn more.
 
 2. Next Steps
 
-   Envoy Gateway should now be successfully installed and running, but in order to experience more abilities of Envoy Gateway, you can refer to [User Guides](/latest/user).
+   Envoy Gateway should now be successfully installed and running, but in order to experience more abilities of Envoy Gateway, you can refer to [Tasks](/latest/tasks).

site/content/en/latest/tasks/_index.md

@@ -0,0 +1,5 @@
+---
+title: "Tasks"
+weight: 2
+description: Learn Envoy Gateway hands-on through tasks
+---

site/content/en/latest/tasks/extensibility/_index.md

@@ -0,0 +1,5 @@
+---
+title: "Extensibility"
+weight: 4
+description: This section includes Extensibility tasks.
+---

site/content/en/latest/user/extensibility/envoy-patch-policy.md → site/content/en/latest/tasks/extensibility/envoy-patch-policy.md

@@ -2,7 +2,7 @@
 title: "Envoy Patch Policy"
 ---
 
-This guide explains the usage of the [EnvoyPatchPolicy][] API.
+This task explains the usage of the [EnvoyPatchPolicy][] API.
 __Note:__ This API is meant for users extremely familiar with Envoy [xDS][] semantics.
 Also before considering this API for production use cases, please be aware that this API
 is unstable and the outcome may change across versions. Use at your own risk.
@@ -22,7 +22,7 @@ not exposed by Envoy Gateway APIs today.
 
 ### Prerequisites
 
-* Follow the steps from the [Quickstart](../../quickstart) guide to install Envoy Gateway and the example manifest.
+* Follow the steps from the [Quickstart](../../quickstart) task to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
 ### Enable EnvoyPatchPolicy

site/content/en/latest/tasks/observability/_index.md

@@ -0,0 +1,5 @@
+---
+title: "Observability"
+weight: 4
+description: This section includes Observability tasks.
+---

site/content/en/latest/user/observability/gateway-api-metrics.md → site/content/en/latest/tasks/observability/gateway-api-metrics.md

@@ -7,7 +7,7 @@ The project also provides example dashboard for visualising the metrics using Gr
 
 ## Prerequisites
 
-Follow the steps from the [Quickstart Guide](../../quickstart) to install Envoy Gateway and the example manifest.
+Follow the steps from the [Quickstart](../../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
 Run the following commands to install the metrics stack, with the Gateway API State Metrics configuration, on your kubernetes cluster:

site/content/en/latest/user/observability/grafana-integration.md → site/content/en/latest/tasks/observability/grafana-integration.md

@@ -3,11 +3,11 @@ title: "Visualising metrics using Grafana"
 ---
 
 Envoy Gateway provides support for exposing Envoy Proxy metrics to a Prometheus instance.
-This guide shows you how to visualise the metrics exposed to prometheus using grafana.
+This task shows you how to visualise the metrics exposed to prometheus using grafana.
 
 ## Prerequisites
 
-Follow the steps from the [Quickstart Guide](../../quickstart) to install Envoy Gateway and the example manifest.
+Follow the steps from the [Quickstart](../../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
 Follow the steps from the [Proxy Observability](../proxy-observability#Metrics) to enable prometheus metrics.

site/content/en/latest/user/observability/proxy-observability.md → site/content/en/latest/tasks/observability/proxy-observability.md

@@ -3,11 +3,11 @@ title: "Proxy Observability"
 ---
 
 Envoy Gateway provides observability for the ControlPlane and the underlying EnvoyProxy instances.
-This guide show you how to config proxy observability, includes metrics, logs, and traces.
+This task show you how to config proxy observability, includes metrics, logs, and traces.
 
 ## Prerequisites
 
-Follow the steps from the [Quickstart Guide](../quickstart) to install Envoy Gateway and the example manifest.
+Follow the steps from the [Quickstart](../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
 [FluentBit](https://fluentbit.io/) is used to collect logs from the EnvoyProxy instances and forward them to Loki. Install FluentBit:

site/content/en/latest/tasks/operations/_index.md

@@ -0,0 +1,5 @@
+---
+title: "Operations"
+weight: 4
+description: This section includes Operations tasks.
+---

site/content/en/latest/user/operations/customize-envoyproxy.md → site/content/en/latest/tasks/operations/customize-envoyproxy.md

@@ -8,7 +8,7 @@ Service. To learn more about GatewayClass and ParametersRef, please refer to [Ga
 
 ## Installation
 
-Follow the steps from the [Quickstart Guide](../../quickstart) to install Envoy Gateway and the example manifest.
+Follow the steps from the [Quickstart](../../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
 ## Add GatewayClass ParametersRef

site/content/en/latest/user/quickstart.md → site/content/en/latest/tasks/quickstart.md

@@ -4,7 +4,7 @@ weight: 1
 description: Get started with Envoy Gateway in a few simple steps.
 ---
 
-This guide will help you get started with Envoy Gateway in a few simple steps.
+This "quick start" will help you get started with Envoy Gateway in a few simple steps.
 
 ## Prerequisites
 
@@ -85,7 +85,7 @@ curl --verbose --header "Host: www.example.com" http://$GATEWAY_HOST/get
 
 ## Clean-Up
 
-Use the steps in this section to uninstall everything from the quickstart guide.
+Use the steps in this section to uninstall everything from the quickstart.
 
 Delete the GatewayClass, Gateway, HTTPRoute and Example App:
 

site/content/en/latest/tasks/security/_index.md

@@ -0,0 +1,5 @@
+---
+title: "Security"
+weight: 2
+description: This section includes Security tasks.
+---

site/content/en/latest/user/security/backend-tls.md → site/content/en/latest/tasks/security/backend-tls.md

@@ -2,8 +2,8 @@
 title: "Backend TLS: Gateway to Backend"
 ---
 
-This guide demonstrates how TLS can be achieved between the Gateway and a backend. The guide uses a self-signed CA, so it should be used for
-testing and demonstration purposes only.
+This task demonstrates how TLS can be achieved between the Gateway and a backend.
+This task uses a self-signed CA, so it should be used for testing and demonstration purposes only.
 
 Envoy Gateway supports the Gateway-API defined [BackendTLSPolicy][].
 
@@ -13,7 +13,7 @@ Envoy Gateway supports the Gateway-API defined [BackendTLSPolicy][].
 
 ## Installation
 
-Follow the steps from the [Quickstart Guide](../../quickstart) to install Envoy Gateway and the example manifest.
+Follow the steps from the [Quickstart](../../quickstart) to install Envoy Gateway and the example manifest.
 
 ## TLS Certificates
 
@@ -235,4 +235,4 @@ Inspect the output and see that the response contains the details of the TLS han
  }
 ```
 
-[BackendTLSPolicy]: https://gateway-api.sigs.k8s.io/api-types/backendtlspolicy/
+[BackendTLSPolicy]: https://gateway-api.sigs.k8s.io/api-types/backendtlspolicy/

site/content/en/latest/user/security/basic-auth.md → site/content/en/latest/tasks/security/basic-auth.md

@@ -2,7 +2,7 @@
 title: "Basic Authentication"
 ---
 
-This guide provides instructions for configuring [HTTP Basic authentication][http Basic authentication]. 
+This task provides instructions for configuring [HTTP Basic authentication][http Basic authentication]. 
 HTTP Basic authentication checks if an incoming request has a valid username and password before routing the request to 
 a backend service.
 
@@ -12,7 +12,7 @@ This instantiated resource can be linked to a [Gateway][Gateway], [HTTPRoute][HT
 
 ## Prerequisites
 
-Follow the steps from the [Quickstart](../../quickstart) guide to install Envoy Gateway and the example manifest.
+Follow the steps from the [Quickstart](../../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
 ## Configuration
@@ -45,7 +45,7 @@ kubectl create secret tls example-cert --key=www.example.com.key --cert=www.exam
 ```
 
 ### Enable HTTPS
-Update the Gateway from the Quickstart guide to include an HTTPS listener that listens on port `443` and references the
+Update the Gateway from the Quickstart to include an HTTPS listener that listens on port `443` and references the
 `example-cert` Secret:
 
 ```shell
@@ -128,7 +128,7 @@ kubectl get securitypolicy/basic-auth-example -o yaml
 
 ## Testing
 
-Ensure the `GATEWAY_HOST` environment variable from the [Quickstart](../../quickstart) guide is set. If not, follow the
+Ensure the `GATEWAY_HOST` environment variable from the [Quickstart](../../quickstart) is set. If not, follow the
 Quickstart instructions to set the variable.
 
 ```shell
@@ -176,7 +176,7 @@ The request should be allowed and you should see the response from the backend s
 
 ## Clean-Up
 
-Follow the steps from the [Quickstart](../../quickstart) guide to uninstall Envoy Gateway and the example manifest.
+Follow the steps from the [Quickstart](../../quickstart) to uninstall Envoy Gateway and the example manifest.
 
 Delete the SecurityPolicy and the secret
 

site/content/en/latest/user/security/cors.md → site/content/en/latest/tasks/security/cors.md

@@ -2,7 +2,7 @@
 title: "CORS"
 ---
 
-This guide provides instructions for configuring [Cross-Origin Resource Sharing (CORS)][cors] on Envoy Gateway.
+This task provides instructions for configuring [Cross-Origin Resource Sharing (CORS)][cors] on Envoy Gateway.
 CORS defines a way for client web applications that are loaded in one domain to interact with resources in a different
 domain.
 
@@ -11,7 +11,7 @@ This instantiated resource can be linked to a [Gateway][Gateway], [HTTPRoute][HT
 
 ## Prerequisites
 
-Follow the steps from the [Quickstart](../../quickstart) guide to install Envoy Gateway and the example manifest.
+Follow the steps from the [Quickstart](../../quickstart) to install Envoy Gateway and the example manifest.
 Before proceeding, you should be able to query the example backend using HTTP.
 
 ## Configuration
@@ -57,7 +57,7 @@ kubectl get securitypolicy/cors-example -o yaml
 
 ## Testing
 
-Ensure the `GATEWAY_HOST` environment variable from the [Quickstart](../../quickstart) guide is set. If not, follow the
+Ensure the `GATEWAY_HOST` environment variable from the [Quickstart](../../quickstart) is set. If not, follow the
 Quickstart instructions to set the variable.
 
 ```shell
@@ -122,7 +122,7 @@ filter to work. Otherwise, the OPTIONS request won't match the routes and the CO
 
 ## Clean-Up
 
-Follow the steps from the [Quickstart](../../quickstart) guide to uninstall Envoy Gateway and the example manifest.
+Follow the steps from the [Quickstart](../../quickstart) to uninstall Envoy Gateway and the example manifest.
 
 Delete the SecurityPolicy: