Changed URL for NGINX One Console docs (#1442)

* Changed url for nginx one console

Author: travisamartin

.github/CODEOWNERS

@@ -53,5 +53,5 @@ content/nim/*               @nginx/nim-docs-approvers
 content/nginx/*             @nginx/plus-docs-approvers
 
 # NGINX One
-content/nginx-one/*         @nginx/one-docs-approvers
+content/nginx-one-console/*         @nginx/one-docs-approvers
 

.github/labeler.yml

@@ -55,11 +55,11 @@ product/nginx-plus:
           - 'content/nginx/**'
           - 'content/includes/nginx-plus/**'
 
-product/nginx-one:
+product/nginx-one-console:
   - changed-files:
       - any-glob-to-any-file:
-          - 'content/nginx-one/**'
-          - 'content/includes/nginx-one/**'
+          - 'content/nginx-one-console/**'
+          - 'content/includes/nginx-one-console/**'
 
 product/nginxaas-azure:
   - changed-files:

_banners/agent-v3-release.md

@@ -1,6 +1,6 @@
 {{< banner "notice" "NGINX Agent 3.0 is now available" >}}
 
-The documentation in this section is for **NGINX Agent version 2.x**. For NGINX Agent 3.x content visit the [NGINX One Console documentation]({{< ref "/nginx-one/agent/" >}})
+The documentation in this section is for **NGINX Agent version 2.x**. For NGINX Agent 3.x content visit the [NGINX One Console documentation]({{< ref "/nginx-one-console/agent/" >}})
 
 F5 NGINX Instance Manager (NIM) does not currently support NGINX Agent 3.x. NGINX Instance Manager customers can upgrade to the latest NGINX Agent 2.x version by following the [Upgrade NGINX Agent](/nginx-agent/installation-upgrade/upgrade/) guide.
 

_banners/eol-amplify.md

@@ -6,7 +6,7 @@ NGINX Amplify support ends on January 31, 2026. To continue monitoring your NGIN
 
 1. [Contact the F5 NGINX Sales team](https://www.f5.com/products/get-f5/f5-nginx-products-and-packaging) to get an NGINX One subscription, if you don’t already have one.
 2. [Uninstall the NGINX Amplify agent]({{< ref "/amplify/nginx-amplify-agent/install/uninstalling-amplify-agent.md" >}}).
-3. [Follow the NGINX One Console getting started guide]({{< ref "/nginx-one/getting-started.md" >}}).
+3. [Follow the NGINX One Console getting started guide]({{< ref "/nginx-one-console/getting-started.md" >}}).
 
 [Professional Services](https://www.f5.com/services) are available to support your transition. Additional fees may apply.
 {{</ banner >}}

content/_index.md

@@ -7,7 +7,7 @@ description: Learn how to deliver, manage, and protect your applications using F
 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/" brandIcon="NGINX-One-product-icon.svg" isLanding="true">}}
+  {{<card title="F5 NGINX One Console" titleUrl="/nginx-one-console/" brandIcon="NGINX-One-product-icon.svg" isLanding="true">}}
     Monitor your infrastructure, address security vulnerabilities, and assess the health of your NGINX fleet, all from a single console.
   {{</card >}}
   {{<card title="F5 NGINX Plus" titleUrl="/nginx/" brandIcon="NGINX-Plus-product-icon.svg" isLanding="true">}}

content/agent/contribute/dev-environment-setup.md

@@ -17,7 +17,7 @@ Ubuntu is the recommended operating system for development, as it comes with mos
 
 To begin this task, you will require the following:
 
-- A [working NGINX Agent instance]({{< ref "/nginx-one/agent/install-upgrade/" >}}).
+- A [working NGINX Agent instance]({{< ref "/nginx-one-console/agent/install-upgrade/" >}}).
 - A [Go installation](https://go.dev/dl/) of version 1.22.2 or newer.
 - A [Protocol Buffer Compiler](https://grpc.io/docs/protoc-installation/) installation.
 
@@ -29,7 +29,7 @@ git clone [email protected]:nginx/agent.git
 
 Read [Cloning a repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository) for more information
 
-Follow the steps in the [Installation]({{< ref "/nginx-one/agent/install-upgrade/" >}}) topic to install NGINX Agent.
+Follow the steps in the [Installation]({{< ref "/nginx-one-console/agent/install-upgrade/" >}}) topic to install NGINX Agent.
 
 ## Install prerequisite packages
 Depending on the operating system distribution, it may be necessary to install the following packages in order to build NGINX Agent.

content/agent/contribute/start-mock-interface.md

@@ -14,7 +14,7 @@ The mock interface is useful when developing NGINX Agent, as it allows you to vi
 
 To begin this task, you will require the following:
 
-- A [working NGINX Agent instance]({{< ref "/nginx-one/agent/install-upgrade/" >}}).
+- A [working NGINX Agent instance]({{< ref "/nginx-one-console/agent/install-upgrade/" >}}).
 - A [Go installation](https://go.dev/dl/) of version 1.22.2 or newer.
 - A [go-swagger](https://goswagger.io/go-swagger/install/) installation.
 

content/glossary/glossary.md

@@ -15,13 +15,13 @@ This glossary defines terms used in F5 NGINX.
 
 | Term        | Definition |
 | ---- | ---------- |
-| **Config Sync Group** / **Instance Group** | A group of NGINX systems (or instances) with identical configurations. They may also share the same certificates. However, the instances in a Config Sync Group could belong to different systems and even different clusters. Also known as an Instance Group in NGINX Instance Manager. For more information, see this explanation of [Important considerations]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md#important-considerations" >}}) |
+| **Config Sync Group** / **Instance Group** | A group of NGINX systems (or instances) with identical configurations. They may also share the same certificates. However, the instances in a Config Sync Group could belong to different systems and even different clusters. Also known as an Instance Group in NGINX Instance Manager. For more information, see this explanation of [Important considerations]({{< ref "/nginx-one-console/nginx-configs/config-sync-groups/manage-config-sync-groups.md#important-considerations" >}}) |
 | **Control Plane** | The control plane is the part of a network architecture that manages and controls the flow or data or traffic (the Data Plane). It is responsible for system-level tasks such as routing and traffic management. |
 | **Data Plane** | The data plane is the part of a network architecture that carries user traffic. It handles tasks like forwarding data packets between devices and managing network communication. In the context of NGINX, the data plane is responsible for tasks such as load balancing, caching, and serving web content. |
 | **Instance** | An instance is an individual system with NGINX installed. You can group the instances of your choice in a Config Sync Group. When you add an instance to NGINX One Console, you need to use a data plane key. |
 | **Namespace** | In F5 Distributed Cloud, a namespace groups a tenant's configuration objects, similar to administrative domains. Every object in a namespace must have a unique name, and each namespace must be unique to its tenant. This setup ensures isolation, preventing cross-referencing of objects between namespaces. You'll see the namespace in the NGINX One Console URL as `/namespaces/<namespace name>/`. To switch an instance between namespaces, you have to deregister an instance from an old namespace, and register it on the new namespace. |
 | **NGINX Agent**                      | A lightweight software component installed on NGINX instances to enable communication with the NGINX One console. NGINX Agent also enables communication with NGINX Instance Manager.                                     |
-| **Staged Configurations** | Also known as **Staged Configs**. Allows you to save "work in progress." You can create it from scratch, an Instance, another Staged Config, or a Config Sync Group. It does _not_ have to be a working configuration until you publish it to an instance or a Config Sync Group. You can even manage your **Staged Configurations** through our [API]({{< ref "/nginx-one/api/api-reference-guide/#tag/StagedConfigs" >}}). |
+| **Staged Configurations** | Also known as **Staged Configs**. Allows you to save "work in progress." You can create it from scratch, an Instance, another Staged Config, or a Config Sync Group. It does _not_ have to be a working configuration until you publish it to an instance or a Config Sync Group. You can even manage your **Staged Configurations** through our [API]({{< ref "/nginx-one-console/api/api-reference-guide/#tag/StagedConfigs" >}}). |
 | **Tenant** | A tenant in F5 Distributed Cloud is an entity that owns a specific set of configuration and infrastructure. It is fundamental for isolation, meaning a tenant cannot access objects or infrastructure of other tenants. Tenants can be either individual or enterprise, with the latter allowing multiple users with role-based access control (RBAC). |
 
 {{< /table >}}
@@ -62,9 +62,9 @@ It assumes you are familiar with various layer 7 (L7) hypertext transfer protoco
 
 ## NGINX Alerts
 
-To set up NGINX Alerts through the F5 Distributed Cloud, follow the procedure in [Set up security alerts]({{< ref "/nginx-one/secure-your-fleet/set-up-security-alerts/" >}}).
+To set up NGINX Alerts through the F5 Distributed Cloud, follow the procedure in [Set up security alerts]({{< ref "/nginx-one-console/secure-your-fleet/set-up-security-alerts/" >}}).
 
-{{< include "/nginx-one/alert-labels.md" >}}
+{{< include "/nginx-one-console/alert-labels.md" >}}
 
 
 ## References

content/includes/agent/about.md

@@ -1,7 +1,7 @@
 ---
 files:
    - content/agent/about.md
-   - content/nginx-one/agent/overview/about.md
+   - content/nginx-one-console/agent/overview/about.md
 ---
 
 F5 NGINX Agent is a lightweight companion daemon designed to work with NGINX One and enable remote management of NGINX instances. It also gathers performance metrics from NGINX and transmits them to the NGINX One Console for enhanced monitoring and control.
@@ -12,14 +12,14 @@ Enable Access to key NGINX One use cases:
 
    - Seamlessly integrates with essential NGINX One functionality, simplifying access to its core use cases and
      enhancing operational workflows.
-   - [Connects NGINX instances to NGINX One Console]({{< ref "/nginx-one/agent/install-upgrade/install-from-oss-repo.md#connect-an-instance-to-nginx-one-console" >}})
+   - [Connects NGINX instances to NGINX One Console]({{< ref "/nginx-one-console/agent/install-upgrade/install-from-oss-repo.md#connect-an-instance-to-nginx-one-console" >}})
 
 Real-time observability into NGINX One data plane instances:
 
    - Provides live monitoring and actionable insights into the performance, status, and health of NGINX One data plane
      instances, improving decision-making and operational efficiency.
    - NGINX Agent supports [OpenTelemetry](https://opentelemetry.io/) and the ability to
-     [export the metrics data]({{< ref "/nginx-one/agent/configure-otel-metrics.md" >}}) for use in other applications.
+     [export the metrics data]({{< ref "/nginx-one-console/agent/configure-otel-metrics.md" >}}) for use in other applications.
 
 
 

content/includes/agent/architecture.md

@@ -1,7 +1,7 @@
 ---
 files:
    - content/agent/about.md
-   - content/nginx-one/agent/overview/about.md
+   - content/nginx-one-console/agent/overview/about.md
 ---
 
 The figure shows: