nginx · ADubhlaoich · Jun 4, 2025 · May 26, 2025 · May 26, 2025 · May 29, 2025
diff --git a/content/ngf/changelog.md b/content/ngf/changelog.md
@@ -1,11 +1,10 @@
 ---
 title: Changelog
-description: "NGINX Gateway Fabric releases."
-weight: 900
 toc: true
-type: reference
-product: NGF
-docs: "DOCS-1359"
+weight: 900
+nd-content-type: reference
+nd-product: NGF
+nd-docs: "DOCS-1359"
 ---
 
 See the NGINX Gateway Fabric changelog page:

diff --git a/content/ngf/get-started.md b/content/ngf/get-started.md
@@ -2,9 +2,9 @@
 title: Get started
 weight: 200
 toc: true
-type: how-to
-product: NGF
-docs: DOCS-000
+nd-content-type: how-to
+nd-product: NGF
+nd-docs: DOCS-000
 ---
 
 {{< important >}}
@@ -21,8 +21,6 @@ This is a guide for getting started with NGINX Gateway Fabric. It explains how t
 
 By following the steps in order, you will finish with a functional NGINX Gateway Fabric cluster.
 
----
-
 ## Before you begin
 
 To complete this guide, you need the following prerequisites installed:
@@ -84,8 +82,6 @@ make create-kind-cluster
 
 {{< /note >}}
 
----
-
 ## Install NGINX Gateway Fabric
 
 ### Add Gateway API resources
@@ -104,8 +100,6 @@ customresourcedefinition.apiextensions.k8s.io/httproutes.gateway.networking.k8s.
 customresourcedefinition.apiextensions.k8s.io/referencegrants.gateway.networking.k8s.io created
 ```
 
----
-
 ### Install the Helm chart
 
 Use `helm` to install NGINX Gateway Fabric, specifying the NodePort configuration that will be set on the 
@@ -128,8 +122,6 @@ REVISION: 1
 TEST SUITE: None
 ```
 
----
-
 ## Create an example application
 
 In the previous section, you deployed NGINX Gateway Fabric to a local cluster. This section shows you how to deploy a simple web application to test that NGINX Gateway Fabric works.
@@ -138,8 +130,6 @@ In the previous section, you deployed NGINX Gateway Fabric to a local cluster. T
 The YAML code in the following sections can be found in the [cafe-example folder](https://github.com/nginx/nginx-gateway-fabric/tree/main/examples/cafe-example) of the GitHub repository.
 {{< /note >}}
 
----
-
 ### Create the application resources
 
 Create the file _cafe.yaml_ with the following contents:
@@ -171,8 +161,6 @@ coffee-676c9f8944-k2bmd   1/1     Running   0          9s
 tea-6fbfdcb95d-9lhbj      1/1     Running   0          9s
 ```
 
----
-
 ### Create Gateway and HTTPRoute resources
 
 Create the file _gateway.yaml_ with the following contents:
@@ -217,8 +205,6 @@ httproute.gateway.networking.k8s.io/coffee created
 httproute.gateway.networking.k8s.io/tea created
 ```
 
----
-
 ### Verify the configuration
 
 You can check that all of the expected services are available using `kubectl get`:
@@ -431,8 +417,6 @@ Status:
 Events:       <none>
 ```
 
----
-
 ## Test NGINX Gateway Fabric
 
 By configuring the cluster with the port `31437`, there is implicit port forwarding from your local machine to NodePort, allowing for direct communication to the NGINX Gateway Fabric service.
@@ -463,8 +447,6 @@ URI: /tea
 Request ID: 1b5c8f3a4532ea7d7510cf14ffeb27af
 ```
 
----
-
 ## Next steps
 
 - [Install NGINX Gateway Fabric]({{< ref "/ngf/install/" >}}), for additional ways to install NGINX Gateway Fabric

diff --git a/content/ngf/install/build-image.md b/content/ngf/install/build-image.md
@@ -2,17 +2,15 @@
 title: Build NGINX Gateway Fabric
 weight: 400
 toc: true
-type: how-to
-product: NGF
-docs: DOCS-1431
+nd-content-type: how-to
+nd-product: NGF
+nd-docs: DOCS-1431
 ---
 
 ## Overview
 
 While most users will install NGINX Gateway Fabric [with Helm]({{< ref "/ngf/install/helm.md" >}}) or [Kubernetes manifests]({{< ref "/ngf/install/manifests.md" >}}), manually building the [NGINX Gateway Fabric and NGINX images]({{< ref "/ngf/overview/gateway-architecture.md#the-nginx-gateway-fabric-pod" >}}) can be helpful for testing and development purposes. Follow the steps in this document to build the NGINX Gateway Fabric and NGINX images.
 
----
-
 ## Before you begin
 
 Before you can build the NGINX Gateway Fabric and NGINX images, make sure you have the following software
@@ -25,7 +23,6 @@ installed on your machine:
 
 If building the NGINX Plus image, you will also need a valid NGINX Plus license certificate (`nginx-repo.crt`) and key (`nginx-repo.key`) in the root of the repo.
 
----
 
 ## Steps
 

diff --git a/content/ngf/install/deploy-data-plane.md b/content/ngf/install/deploy-data-plane.md
@@ -2,9 +2,9 @@
 title: Deploy a Gateway for data plane instances
 weight: 600
 toc: true
-type: how-to
-product: NGF
-docs: DOCS-000
+nd-content-type: how-to
+nd-product: NGF
+nd-docs: DOCS-000
 ---
 
 ## Overview
@@ -236,7 +236,7 @@ Annotations:              annotationKey: annotationValue
 
 For more guides on routing traffic to applications and more information on Data Plane configuration, check out the following resources:
 
-- [Routing traffic to applications]({{< ref "/ngf/traffic-management/routing-traffic-to-your-app.md" >}})
+- [Routing traffic to applications]({{< ref "/ngf/traffic-management/basic-routing.md" >}})
 - [Application routes using HTTP matching conditions]({{< ref "/ngf/traffic-management/advanced-routing.md" >}})
 - [Data plane configuration]({{< ref "/ngf/how-to/data-plane-configuration.md" >}})
 - [API reference]({{< ref "/ngf/reference/api.md" >}})
diff --git a/content/ngf/install/helm.md b/content/ngf/install/helm.md
@@ -4,7 +4,7 @@ weight: 200
 toc: true
 nd-content-type: how-to
 nd-product: NGF
-docs: DOCS-1430
+nd-docs: DOCS-1430
 ---
 
 ## Overview
@@ -18,7 +18,7 @@ To complete this guide, you will need:
 
 - [kubectl](https://kubernetes.io/docs/tasks/tools/), a command-line tool for managing Kubernetes clusters.
 - [Helm 3.0 or later](https://helm.sh/docs/intro/install/), for deploying and managing applications on Kubernetes.
-- [Add certificates for secure authentication]({{< ref "/ngf/install/control-plane-certs.md" >}}) in a production environment.
+- [Add certificates for secure authentication]({{< ref "/ngf/install/secure-certificates.md" >}}) in a production environment.
 
 {{< important >}} If you’d like to use NGINX Plus, some additional setup is also required: {{</ important >}}
 
@@ -192,6 +192,6 @@ Follow these steps to uninstall NGINX Gateway Fabric and Gateway API from your K
 ## Next steps
 
 - [Deploy a Gateway for data plane instances]({{< ref "/ngf/install/deploy-data-plane.md" >}})
-- [Routing traffic to applications]({{< ref "/ngf/traffic-management/routing-traffic-to-your-app.md" >}})
+- [Routing traffic to applications]({{< ref "/ngf/traffic-management/basic-routing.md" >}})
 
 For a full list of the Helm Chart configuration parameters, read [the NGINX Gateway Fabric Helm Chart](https://github.com/nginx/nginx-gateway-fabric/blob/v{{< version-ngf >}}/charts/nginx-gateway-fabric/README.md#configuration).
diff --git a/content/ngf/install/manifests.md b/content/ngf/install/manifests.md
@@ -2,9 +2,9 @@
 title: Install NGINX Gateway Fabric with Manifests
 weight: 200
 toc: true
-type: how-to
-product: NGF
-docs: DOCS-1429
+nd-content-type: how-to
+nd-product: NGF
+nd-docs: DOCS-1429
 ---
 
 ## Overview
@@ -16,7 +16,7 @@ Learn how to install, upgrade, and uninstall NGINX Gateway Fabric using Kubernet
 To complete this guide, you'll need to install:
 
 - [kubectl](https://kubernetes.io/docs/tasks/tools/), a command-line interface for managing Kubernetes clusters.
-- [Add certificates for secure authentication]({{< ref "/ngf/install/control-plane-certs.md" >}}) in a production environment.
+- [Add certificates for secure authentication]({{< ref "/ngf/install/secure-certificates.md" >}}) in a production environment.
 
 {{< important >}} If you’d like to use NGINX Plus, some additional setup is also required: {{</ important >}}
 
@@ -213,4 +213,4 @@ Follow these steps to uninstall NGINX Gateway Fabric and Gateway API from your K
 ## Next steps
 
 - [Deploy a Gateway for data plane instances]({{< ref "/ngf/install/deploy-data-plane.md" >}})
-- [Routing traffic to applications]({{< ref "/ngf/traffic-management/routing-traffic-to-your-app.md" >}})
+- [Routing traffic to applications]({{< ref "/ngf/traffic-management/basic-routing.md" >}})
diff --git a/content/ngf/install/nginx-plus.md b/content/ngf/install/nginx-plus.md
@@ -2,9 +2,9 @@
 title: Install NGINX Gateway Fabric with NGINX Plus
 weight: 300
 toc: true
-type: how-to
-product: NGF
-docs: DOCS-000
+nd-content-type: how-to
+nd-product: NGF
+nd-docs: DOCS-000
 ---
 
 ## Overview
@@ -17,22 +17,16 @@ The JWT is required for validating your subscription and reporting telemetry dat
 
 {{< note >}} The following Secrets should be created in the same namespace as the NGINX Gateway Fabric control plane (default: nginx-gateway). The control plane will copy these Secrets into any namespaces where NGINX gets deployed. If you need to update the Secrets, update the originals that you created in the control plane namespace, and the control plane will propagate those updates to all duplicated Secrets. {{< /note >}}
 
----
-
 ## Set up the JWT
 
 The JWT needs to be configured before deploying NGINX Gateway Fabric. The JWT will be stored in two Kubernetes Secrets: one for downloading the NGINX Plus container image, and the other for running NGINX Plus.
 
 {{< include "/ngf/installation/jwt-password-note.md" >}}
 
----
-
 ### Download the JWT from MyF5
 
 {{< include "/ngf/installation/nginx-plus/download-jwt.md" >}}
 
----
-
 ### Docker Registry Secret
 
 {{< include "/ngf/installation/nginx-plus/docker-registry-secret.md" >}}
@@ -55,8 +49,6 @@ Specify the Secret name in the `nginx-docker-secret` command-line argument of th
 
 {{</tabs>}}
 
----
-
 ### NGINX Plus Secret
 
 {{< include "/ngf/installation/nginx-plus/nginx-plus-secret.md" >}}
@@ -81,8 +73,6 @@ Specify the Secret name in the `--usage-report-secret` command-line flag on the
 
 {{< note >}} If you are reporting to the default licensing endpoint, then you can now proceed with [installing NGINX Gateway Fabric]({{< ref "/ngf/install/" >}}). Otherwise, follow the steps below to configure reporting to NGINX Instance Manager. {{< /note >}}
 
----
-
 ### Reporting to NGINX Instance Manager {#nim}
 
 If you are deploying NGINX Gateway Fabric in an environment where you need to report to NGINX Instance Manager instead of the default licensing endpoint, a few extra steps may be required.
@@ -105,8 +95,6 @@ Specify the endpoint in the `--usage-report-endpoint` command-line flag on the `
 
 {{</tabs>}}
 
----
-
 #### CA and Client certificate/key {#nim-cert}
 
 To configure a CA cert and/or client certificate and key, a few extra steps are needed.
@@ -143,8 +131,6 @@ Specify the CA Secret name in the `--usage-report-ca-secret` command-line flag o
 
 {{< note >}} Once these Secrets are created and configuration options are set, you can now [install NGINX Gateway Fabric]({{< ref "/ngf/install/" >}}). {{< /note >}}
 
----
-
 ## Installation flags to configure usage reporting {#flags}
 
 When installing NGINX Gateway Fabric, the following flags can be specified to configure usage reporting to fit your needs:
@@ -167,8 +153,6 @@ If using manifests, the following command-line options should be set as necessar
 - `--usage-report-ca-secret` is the name of the Secret containing the NGINX Instance Manager CA certificate. Must exist in the same namespace that the NGINX Gateway Fabric control plane is running in (default namespace: nginx-gateway).
 - `--usage-report-client-ssl-secret` is the name of the Secret containing the client certificate and key for authenticating with NGINX Instance Manager. Must exist in the same namespace that the NGINX Gateway Fabric control plane is running in (default namespace: nginx-gateway).
 
----
-
 ## What’s reported and how it’s protected {#telemetry}
 
 NGINX Plus reports the following data every hour by default:
@@ -184,8 +168,6 @@ NGINX Plus reports the following data every hour by default:
 - **Usage report timestamps**: Start and end times for each usage report.
 - **Kubernetes node details**: Information about Kubernetes nodes.
 
----
-
 ### Security and privacy of reported data
 
 All communication between your NGINX Plus instances, NGINX Instance Manager, and F5’s licensing endpoint (`product.connect.nginx.com`) is protected using **SSL/TLS** encryption.
@@ -219,4 +201,4 @@ There are alternative ways to get an NGINX Plus image for NGINX Gateway Fabric:
 ## Next steps
 
 - [Deploy a Gateway for data plane instances]({{< ref "/ngf/install/deploy-data-plane.md" >}})
-- [Routing traffic to applications]({{< ref "/ngf/traffic-management/routing-traffic-to-your-app.md" >}})
+- [Routing traffic to applications]({{< ref "/ngf/traffic-management/basic-routing.md" >}})
diff --git a/content/ngf/install/control-plane-certs.md → content/ngf/install/secure-certificates.md b/content/ngf/install/control-plane-certs.md → content/ngf/install/secure-certificates.md
@@ -49,7 +49,7 @@ helm install \
   --set crds.enabled=true
 ```
 
-This also enables Gateway API features for cert-manager, which can be useful for [securing your workload traffic]({{< ref "/ngf/traffic-security/integrating-cert-manager.md" >}}).
+This also enables Gateway API features for cert-manager, which can be useful for [securing your workload traffic]({{< ref "/ngf/traffic-security/integrate-cert-manager.md" >}}).
 
 ## Create the CA issuer
 

diff --git a/content/ngf/install/upgrade-version.md b/content/ngf/install/upgrade-version.md
@@ -56,14 +56,15 @@ Run the following command to upgrade the CRDs:
 kubectl apply -f https://raw.githubusercontent.com/nginx/nginx-gateway-fabric/v{{< version-ngf >}}/deploy/crds.yaml
 ```
 
-{{< note>}} Ignore the following warning, as it is expected.
+{{< note >}} 
+
+Ignore the following warning, as it is expected.
 
 ```text
 Warning: kubectl apply should be used on resource created by either kubectl create --save-config or kubectl apply.
 ```
-{{</ note >}}
-
 
+{{< /note >}}
 
 ### Upgrade NGINX Gateway Fabric release
 
@@ -183,7 +184,7 @@ For detailed instructions on how to modify these settings, refer to the [Configu
 
 - To read more on [modifying data plane configuration]({{< ref "/ngf/how-to/data-plane-configuration.md" >}}).
 - To learn more about [deploying a Gateway for data plane instances]({{< ref "/ngf/install/deploy-data-plane.md" >}}).
-- To adding secure [authentication to control plane and data planes]({{< ref "/ngf/install/control-plane-certs.md" >}}).
+- To adding secure [authentication to control plane and data planes]({{< ref "/ngf/install/secure-certificates.md" >}}).
 - To read more about [architecture changes]({{< ref "/ngf/overview/gateway-architecture.md" >}}).
 - For detailed [API reference]({{< ref "/ngf/reference/api.md" >}}).