We need to define how we'd freeze the docs on some release of Kuadrant (and its sub-components).
Should the website support versioned docs? Only for Kuadrant? For every components? Only support latest, but of the "right" components?

Currently, we lack proper guides for AuthPolicy, while we use AuthPolicy in RLP docs (e.g. https://docs.kuadrant.io/kuadrant-operator/doc/user-guides/authenticated-rl-with-jwt-and-k8s-authnz/), in the Authorino section we use AuthConfigs, which make sense for an Authorino-only documentation but not for a Kuadrant one.

MKdocs has some support for versioning
https://squidfunk.github.io/mkdocs-material/setup/setting-up-versioning/

We should introduce versioning to our docs. However as part of this we may also need to ensure the right version of docs are being brought in from each of the different components

Based on conversation here, update docs navigation

Overview (what is currently shown in Getting Started link)
Getting Started
  - Quick Start
  - Install
Concepts and APIs
   - Gateways
   - DNSPolicy
   - TLSPolicy
   - RateLimitPolicy
   - AuthPolicy
Experimental
    - E/W stuff
Components
   - MCG
   - Authorino 
    ...

While https://docs.kuadrant.io/kuadrant-operator/doc/proposals/authpolicy-crd/ is still relevant (at least until AuthPolicy v2 is done), it is still written as a proposal, instead of an actual documentation and ideally spec specification for AuthPolicy

In Overview (https://docs.kuadrant.io/) we describe the individual components, yet in Installation (https://docs.kuadrant.io/multicluster-gateway-controller/docs/installation/control-plane-installation/ and https://docs.kuadrant.io/multicluster-gateway-controller/docs/installation/service-protection-installation/) we use new terms of Control Plane and Service Protection, which are only used in those guides. The rest of the guides use again individual component names, like Authorino, or MGC.

I would add an explanation to the Overview that explain both Control Plane and Service Protection, instead of describing individual components

What

Prior to a recent docs re-org, we used to have a simple guide to setting up an RLPv1 policy for basic rate limiting for a Gateway. The previous guide covered both the installation of Limitador, as well as a guide to setting up a simple RLP.

With our new guides on how to set up the data plane, and with our new quickstarts, we should now be able to create a simple guide to setting up a basic RateLimitPolicy, in a multi-cluster Gateway scenario. The actual docs might live in the Kuadrant operator, or somewhere else more appropriate.

Let's create a new guide to follow up after our Gateway walkthrough, to look at both simple RLP and AuthPolicy.

We have lots of content that should cover this already, e.g. https://docs.kuadrant.io/kuadrant-operator/doc/user-guides/simple-rl-for-app-developers/. We could also consider altering that guides setup steps for two routes (one via quickstart, one standalone).