chore: update WAF metadata (#1580)

Author: JTorreG

content/_index.md

@@ -3,8 +3,8 @@ title: F5 NGINX Product Documentation
 description: Learn how to deliver, manage, and protect your applications using F5 NGINX products.
 ---
 
-# F5 NGINX Product Documentation 
-Learn how to deliver, manage, and protect your applications using F5 NGINX products. 
+# F5 NGINX Product Documentation
+Learn how to deliver, manage, and protect your applications using F5 NGINX products.
 
 {{<card-section showAsCards="true" title="F5 NGINX One">}}
   {{<card title="F5 NGINX One Console" titleUrl="/nginx-one-console/" brandIcon="NGINX-One-product-icon.svg" isLanding="true">}}

content/waf/_index.md

@@ -1,25 +1,16 @@
 ---
-# The title is the product name
 title: "F5 WAF for NGINX"
-# The URL is the base of the deployed path, becoming "docs.nginx.com/<url>/<other-pages>"
 url: /waf/
-# The cascade directive applies its nested parameters down the page tree until overwritten
 cascade:
-  # The logo file is resolved from the theme, in the folder /static/images/icons/
   logo: NGINX-App-Protect-WAF-product-icon.svg
-# The subtitle displays directly underneath the heading of a given page
 nd-banner:
     enabled: true
     start-date: 2025-08-30
     md: /_banners/waf-unification-notice.md
 nd-subtitle: A lightweight, high-performance web application firewall for protecting APIs and applications
-# Indicates that this is a custom landing page
 nd-landing-page: true
-# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: landing-page
-# Intended for internal catalogue and search, case sensitive:
-# Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
-nd-product: NAP-WAF
+nd-product: F5WAFN
 ---
 
 ## About

content/waf/changelog/2023.md

@@ -1,12 +1,8 @@
 ---
 title: "2023 archive"
-# Weights are assigned in increments of 100: determines sorting order
 weight: 200
-# Creates a table of contents and sidebar, useful for large documents
 toc: true
-# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: reference
-# Intended for internal catalogue and search, case sensitive:
 nd-product: F5WAFN
 ---
 
@@ -151,7 +147,7 @@ This release includes new signatures for Anti Automation (bot defense):
 
 ### **Important Notes**
 
-- Starting with this release, the `app_protect_compressed_requests_action` directive has been deprecated from the nginx configuration. Now by default the enforcer will decompress all the HTTP compressed payload request and will apply the enforcement. 
+- Starting with this release, the `app_protect_compressed_requests_action` directive has been deprecated from the nginx configuration. Now by default the enforcer will decompress all the HTTP compressed payload request and will apply the enforcement.
 
 - The F5 NGINX App Protect WAF has been enhanced to include response signature checks within the "filetypes" section. You have an option to enable the signature verification in the response by setting the `responseCheck` parameter to true. By default, this parameter is set to false. See [Restrict Response Signatures]({{< ref "/waf/policies/response-signatures.md" >}}) for more details.
 

content/waf/changelog/2024.md

@@ -1,13 +1,8 @@
 ---
 title: "2024 archive"
-# Weights are assigned in increments of 100: determines sorting order
 weight: 100
-# Creates a table of contents and sidebar, useful for large documents
 toc: true
-# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: reference
-# Intended for internal catalogue and search, case sensitive:
-# Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
 nd-product: F5WAFN
 ---
 

content/waf/changelog/_index.md

@@ -1,14 +1,9 @@
 ---
-# We use sentence case and present imperative tone
 title: "Changelog"
 url: /waf/changelog/
-# Weights are assigned in increments of 100: determines sorting order
 weight: 600
-# Creates a table of contents and sidebar, useful for large documents
 nd-landing-page: true
-# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: reference
-# Intended for internal catalogue and search, case sensitive:
 nd-product: F5WAFN
 ---
 

content/waf/configure/apreload.md

@@ -1,15 +1,9 @@
 ---
-# We use sentence case and present imperative tone
 title: "Apply security policy updates without reloading NGINX using apreload"
-# Weights are assigned in increments of 100: determines sorting order
 weight: 100
-# Creates a table of contents and sidebar, useful for large documents
 toc: true
-# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: how-to
-# Intended for internal catalogue and search, case sensitive:
-# Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
-nd-product: NAP-WAF
+nd-product: F5WAFN
 ---
 
 This document describes how to use `apreload`, a tool for updating F5 WAF for NGINX configuration without reloading NGINX.
@@ -61,7 +55,7 @@ When calling _apreload_ directly, it is possible to run it while the previous ex
 
 The new execution will will apply a new configuration, and the most recent configuration will only apply during during the execution period.
 
-In a scenario where an execution from an NGINX reload is followed by a direct _ap_reload_ call, the NGINX workers with the new NGINX configuration will be loaded as soon as the Enforcer finishes processing the existing configuration. 
+In a scenario where an execution from an NGINX reload is followed by a direct _ap_reload_ call, the NGINX workers with the new NGINX configuration will be loaded as soon as the Enforcer finishes processing the existing configuration.
 
 Once complete, the most recent F5 WAF for NGINX configuration will be loaded using with the same NGINX worker instances.
 
@@ -77,10 +71,10 @@ If you want to apply either of the two, reload NGINX instead of using _apreload_
 
 ## apreload events
 
-_apreload_ events use the same format as operation log events written in the NGINX error log, reporting `configuration_load_success` or `configuration_load_failure` with JSON formatted details. 
+_apreload_ events use the same format as operation log events written in the NGINX error log, reporting `configuration_load_success` or `configuration_load_failure` with JSON formatted details.
 
-If any of the configuration files are invalid, _apreload_ will discover that and return the proper error message in the `configuration_load_failure event`. 
+If any of the configuration files are invalid, _apreload_ will discover that and return the proper error message in the `configuration_load_failure event`.
 
-The enforcer will continue to run with the previous working configuration. 
+The enforcer will continue to run with the previous working configuration.
 
 For more information, see the [Operation logs]({{< ref "/waf/logging/operation-logs.md">}}) topic.

content/waf/configure/compiler.md

@@ -1,18 +1,14 @@
 ---
-# We use sentence case and present imperative tone
 title: "Build and use the compiler tool"
-# Weights are assigned in increments of 100: determines sorting order
 weight: 200
-# Creates a table of contents and sidebar, useful for large documents
 toc: true
-# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: how-to
 nd-product: F5WAFN
 ---
 
 This document describes how to use the F5 WAF for NGINX compiler, a tool for converting security policies and logging profiles from JSON to a bundle file that F5 WAF can process and apply.
 
-You can use it to get the latest security updates for [Attack signatures]({{< ref "/waf/policies/attack-signatures.md" >}}), Threat campaigns and Bot signatures. 
+You can use it to get the latest security updates for [Attack signatures]({{< ref "/waf/policies/attack-signatures.md" >}}), Threat campaigns and Bot signatures.
 
 The compiler is packaged as a Docker image and can executed using the Docker CLI or as part of a continuous integration/continuous delivery (CI/CD) pipeline.
 
@@ -106,7 +102,7 @@ You can can upgrade or downgrade one of the Signatures by specifying a specific
 
 You can use the Docker registry API to list the available image tags.
 
-Replace `<path-to-your-nginx-repo.key>` with the location of your client key and `<path-to-your-nginx-repo.crt>` with the location of your client certificate. 
+Replace `<path-to-your-nginx-repo.key>` with the location of your client key and `<path-to-your-nginx-repo.crt>` with the location of your client certificate.
 
 ```shell
 curl -s https://private-registry.nginx.com/v2/nap/waf-compiler/tags/list --key <path-to-your-nginx-repo.key> --cert <path-to-your-nginx-repo.crt>
@@ -150,7 +146,7 @@ Ensure that the output directory is writable, otherwise you may encounter a perm
 
 {{< /call-out >}}
 
-To use multiple policy bundles within a single NGINX configuration, you must supply a [global settings](#global-settings) JSON file. 
+To use multiple policy bundles within a single NGINX configuration, you must supply a [global settings](#global-settings) JSON file.
 
 This ensures that all bundles have a common foundation such as cookie seed and user-defined signatures.
 
@@ -184,7 +180,7 @@ docker run --rm \
  -include-source -full-export -g $(pwd)/global_settings.json -p $(pwd)/policy.json -o $(pwd)/compiled_policy.tgz
 ```
 
-This will transform any configuration that relies on external references into an inline configuration within the bundled source. 
+This will transform any configuration that relies on external references into an inline configuration within the bundled source.
 
 Additionally, when `-include-source` is combined with `-full-export`, the policy.json within the bundle will contain the entire source policy, including any default settings from the base template.
 

content/waf/configure/converters.md

@@ -1,18 +1,12 @@
 ---
-# We use sentence case and present imperative tone
 title: "Build and use the converter tools"
-# Weights are assigned in increments of 100: determines sorting order
 weight: 300
-# Creates a table of contents and sidebar, useful for large documents
 toc: true
-# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: how-to
-# Intended for internal catalogue and search, case sensitive:
-# Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
-nd-product: NAP-WAF
+nd-product: F5WAFN
 ---
 
-This document describes the tools F5 WAF for NGINX has to convert existing resources or configuration files from a BIG-IP environment for use with F5 WAF for NGINX. 
+This document describes the tools F5 WAF for NGINX has to convert existing resources or configuration files from a BIG-IP environment for use with F5 WAF for NGINX.
 
 {{< call-out "important" >}}
 
@@ -158,10 +152,10 @@ docker run -it --rm \
   waf-compiler-<version-tag>:custom \
   -i /tmp/convert/policy.xml \
   -o /tmp/convert/policy.json \
-  --full-export 
+  --full-export
 ```
 
-### Keep full configuration (retain elements that may be invalid or irrelevant):
+### Keep full configuration (retain elements that may be invalid or irrelevant)
 ```shell
 docker run -it --rm \
   -v "$(pwd)":/tmp/convert \

content/waf/configure/kubernetes-read-only.md

@@ -1,15 +1,9 @@
 ---
-# We use sentence case and present imperative tone
 title: "Add a read-only filesystem for Kubernetes  "
-# Weights are assigned in increments of 100: determines sorting order
 weight: 600
-# Creates a table of contents and sidebar, useful for large documents
 toc: true
-# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: how-to
-# Intended for internal catalogue and search, case sensitive:
-# Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
-nd-product: NAP-WAF
+nd-product: F5WAFN
 ---
 
 This page describes how to add a read-only filesystem when deploying F5 WAF for NGINX when using Kubernetes.

content/waf/configure/nginx-features.md

@@ -1,19 +1,13 @@
 ---
-# We use sentence case and present imperative tone
 title: "Configure NGINX features with F5 WAF"
-# Weights are assigned in increments of 100: determines sorting order
 weight: 700
-# Creates a table of contents and sidebar, useful for large documents
 toc: true
-# Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 nd-content-type: reference
-# Intended for internal catalogue and search, case sensitive:
-# Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
-nd-product: NAP-WAF
+nd-product: F5WAFN
 ---
-This document shows examples of how to modify your NGINX configuration to enable F5 WAF for NGINX features. 
+This document shows examples of how to modify your NGINX configuration to enable F5 WAF for NGINX features.
 
-It is intended as a reference for small, self-contained examples of how F5 WAF for NGINX can be configured. 
+It is intended as a reference for small, self-contained examples of how F5 WAF for NGINX can be configured.
 
 Important constraints when F5 WAF for NGINX is enabled:
 
@@ -24,7 +18,7 @@ For additional information on configuring NGINX, you should view the [NGINX docu
 
 ## Subrequest-based modules
 
-F5 WAF for NGINX inspects direct client-facing requests, but does not inspect internal subrequests generated by subrequest-based modules. 
+F5 WAF for NGINX inspects direct client-facing requests, but does not inspect internal subrequests generated by subrequest-based modules.
 
 Examples of subrequest-based modules: