ko: migrate kgo docs to ko

Author: pmalek

app/_how-tos/operator-dataplane-custom-plugins.md

@@ -1,6 +1,6 @@
 ---
-title: Deploy custom plugins with {{ site.gateway_operator_product_name }}
-description: "Package and deploy custom Kong plugins as OCI images using the {{ site.gateway_operator_product_name }} and reference them in {{site.base_gateway}} resources."
+title: Deploy custom plugins with {{ site.operator_product_name }}
+description: "Package and deploy custom Kong plugins as OCI images using the {{ site.operator_product_name }} and reference them in {{site.base_gateway}} resources."
 content_type: how_to
 
 permalink: /operator/dataplanes/how-to/deploy-custom-plugins/
@@ -35,7 +35,7 @@ prereqs:
       - kongplugininstallation
 
 tldr:
-  q: How can I deploy a custom plugin using the {{ site.gateway_operator_product_name }}?
+  q: How can I deploy a custom plugin using the {{ site.operator_product_name }}?
   a: |
     Build and push a plugin as a container image, then use a `KongPluginInstallation`
     to register it with the operator. Reference it in your `GatewayConfiguration` to
@@ -44,7 +44,7 @@ tldr:
 
 ## Plugin distribution using an OCI registry
 
-{{ site.gateway_operator_product_name }} can install Kong custom plugins packaged as container images. This guide shows how to package, install, and use a custom plugin in {{site.base_gateway}} instances managed by the {{ site.gateway_operator_product_name }}.
+{{ site.operator_product_name }} can install Kong custom plugins packaged as container images. This guide shows how to package, install, and use a custom plugin in {{site.base_gateway}} instances managed by the {{ site.operator_product_name }}.
 
 {% include_cached plugins/custom-plugin-example.md is_optional=true %}
 
@@ -70,7 +70,7 @@ Build the image:
 docker build -t myheader:1.0.0 .
 ```
 
-Next, push the image to a public or private registry available to the Kubernetes cluster where {{ site.gateway_operator_product_name }} is running.
+Next, push the image to a public or private registry available to the Kubernetes cluster where {{ site.operator_product_name }} is running.
 
 ```bash
 docker tag myheader:1.0.0 $YOUR_REGISTRY_ADDRESS/myheader:1.0.0

app/_landing_pages/operator/install.yaml

@@ -1,8 +1,8 @@
 metadata:
-  title: Install Kong Gateway Operator
+  title: Install {{ site.operator_product_name }}
   content_type: landing_page
   description: |
-    Install {{ site.gateway_operator_product_name }} using Helm
+    Install {{ site.operator_product_name }} using Helm
   products:
     - operator
   breadcrumbs:
@@ -11,11 +11,11 @@ metadata:
 rows:
   - header:
       type: h1
-      text: "Install {{site.gateway_operator_product_name}} (KGO)"
+      text: "Install {{ site.operator_product_name }} (KO)"
 
   - header:
       type: h2
-      text: How do I install {{site.gateway_operator_product_name}}?
+      text: How do I install {{ site.operator_product_name }}?
     columns:
       - blocks:
           - type: text
@@ -44,7 +44,7 @@ rows:
 
           - type: faqs
             config:
-              - q: Can {{ site.gateway_operator_product_name }} be installed with Kustomize or any other tools?
+              - q: Can {{ site.operator_product_name }} be installed with Kustomize or any other tools?
                 a: Helm is the only officially supported installation method.
               - q: How to I customize which controllers I want to run?
                 a: |
@@ -53,7 +53,7 @@ rows:
   - header:
       type: h2
       text: "Next Steps"
-      sub_text: After installing KGO, use one of the following tutorials to get started.              
+      sub_text: After installing KO, use one of the following tutorials to get started.
     columns:
       - blocks:
         - type: card
@@ -71,12 +71,12 @@ rows:
         - type: card
           config:
             icon: /assets/icons/kubernetes.svg
-            title: Deploy {{ site.kic_product_name }}
+            title: Deploy `Gateway`
             description: |
-              Deploy and manage {{ site.kic_product_name }} and {{ site.base_gateway }} automatically using Kubernetes
-              Gateway API resources such as `Gateway` and `HTTPRoute`
+              Deploy and manage `Gateway` and `HTTPRoute` resources automatically using Kubernetes
+              Gateway API resources.
             cta:
-              text: Deploy {{ site.kic_product_name }}
+              text: Deploy `Gateway`
               url: /operator/dataplanes/get-started/kic/create-gateway/
 
       - blocks:
@@ -86,7 +86,7 @@ rows:
             title: Configure {{ site.konnect_short_name }}
             description: |
               Configure your {{ site.konnect_short_name }} organization using CRDs. Create control planes and configure {{ site.base_gateway }} 
-              entities, or configure Dedicated Cloud Gateways deployments. 
+              entities, or configure Dedicated Cloud Gateways deployments.
             cta:
               text: Create and configure a Control Plane in {{ site.konnect_short_name }}
               url: /operator/konnect/crd/control-planes/hybrid/

app/operator/reference/dump-server.md

@@ -1,6 +1,6 @@
 ---
 title: Dump server
-description: 'Use the dump config server to inspect and debug Kong configurations generated by the Gateway Operator for each control plane.'
+description: 'Use the dump config server to inspect and debug Kong configurations generated by the {{site.operator_product_name}} for each control plane.'
 content_type: reference
 layout: reference
 permalink: /operator/control-planes/config-dump-server/

app/operator/support-policy.md

@@ -1,6 +1,6 @@
 ---
-title: "{{site.gateway_operator_product_name}} version support policy"
-description: "Check if your version of {{ site.gateway_operator_product_name }} is supported"
+title: "{{site.operator_product_name}} version support policy"
+description: "Check if your version of {{site.operator_product_name}} is supported"
 content_type: reference
 layout: reference
 products:
@@ -10,19 +10,18 @@ breadcrumbs:
 
 ---
 
-
 Kong primarily follows [semantic versioning](https://semver.org/) (SemVer) for its products.
 
 At Kong’s discretion a specific minor version can be marked as a LTS version. The LTS version is supported on a given distribution for the duration of the distribution’s lifecycle, or for 3 years from LTS release whichever comes sooner. LTS only receives security fixes or certain critical patches at the discretion of Kong. Kong guarantees that at any given time, there will be at least 1 active LTS Kong version.
 
-LTS versions of {{site.gateway_operator_product_name}} are supported for 3 years after release. Standard versions are supported for 1 year after release.
+LTS versions of {{site.operator_product_name}} are supported for 3 years after release. Standard versions are supported for 1 year after release.
 
 {:.info}
-> {{site.gateway_operator_product_name}} is a recently released product and does not currently provide an LTS version.
+> {{site.operator_product_name}} is a recently released product and does not currently provide an LTS version.
 
 {% support_policy operator %}
 
-> *Table 1: Version Support for {{site.gateway_operator_product_name}}*
+> *Table 1: Version Support for {{site.operator_product_name}}*
 
 {% include kong-support-policy.md %}