reorg May 28, part 1

mjang · mjang · commit d3b5cade9c7f · 2025-05-28T11:14:57.000-07:00
diff --git a/content/nginx-one/changelog.md b/content/nginx-one/changelog.md
@@ -84,7 +84,7 @@ You can:
 
 For more information, including warnings about risks, see our documentation on how you can:
 - [Add a file]({{< ref "/nginx-one/nginx-configs/add-file.md" >}})
-- [Manage certificates]({{< ref "/nginx-one/certificates/manage-certificates.md" >}})
+- [Manage certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}})
 
 ### Revert a configuration
 
@@ -108,15 +108,15 @@ From the NGINX One Console you can now:
 - Ensure that your certificates are current and correct.
 - Manage your certificates from a central location. This can help you simplify operations and remotely update, rotate, and deploy those certificates.
 
-For more information, see the full documentation on how you can [Manage Certificates]({{< ref "/nginx-one/certificates/manage-certificates.md" >}}).
+For more information, see the full documentation on how you can [Manage Certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}}).
 
 ## August 22, 2024
 
 ### Config Sync Groups
 
 Config Sync Groups are now available in the F5 NGINX One Console. This feature allows you to manage and synchronize NGINX configurations across multiple instances as a single entity, ensuring consistency and simplifying the management of your NGINX environment.
 
-For more information, see the full documentation on [Managing Config Sync Groups]({{< ref "/nginx-one/config-sync-groups/manage-config-sync-groups.md" >}}).
+For more information, see the full documentation on [Managing Config Sync Groups]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}).
 
 ## August 8, 2024
 
diff --git a/content/nginx-one/connect-instances/_index.md b/content/nginx-one/connect-instances/_index.md
@@ -0,0 +1,6 @@
+---
+description:
+title: Connect your instances to the console
+weight: 700
+url: /nginx-one/connect-instances/
+---
diff --git a/content/nginx-one/connect-instances/containers/_index.md b/content/nginx-one/connect-instances/containers/_index.md
diff --git a/content/nginx-one/connect-instances/containers/connect-nginx-plus-container-images-to-nginx-one.md b/content/nginx-one/connect-instances/containers/connect-nginx-plus-container-images-to-nginx-one.md
@@ -19,7 +19,7 @@ This guide explains how to set up an F5 NGINX Plus Docker container with NGINX A
 Before you start, make sure you have:
 
 - A valid JSON Web Token (JWT) for your NGINX subscription.
-- [A data plane key from NGINX One]({{< ref "/nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md" >}}).
+- [A data plane key from NGINX One]({{< ref "/nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md" >}}).
 - Docker installed and running on your system.
 
 #### Download your JWT license from MyF5
diff --git a/content/nginx-one/connect-instances/data-plane-keys/_index.md b/content/nginx-one/connect-instances/data-plane-keys/_index.md
diff --git a/content/nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md b/content/nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md
diff --git a/content/nginx-one/connect-instances/settings/_index.md b/content/nginx-one/connect-instances/settings/_index.md
diff --git a/content/nginx-one/getting-started.md b/content/nginx-one/getting-started.md
@@ -43,9 +43,9 @@ To generate a data plane key:
 {{<call-out "caution" "Data plane key guidelines" "fas fa-key" >}}
 Data plane keys are displayed only once and cannot be retrieved later. Be sure to copy and store this key securely.
 
-Data plane keys expire after one year. You can change this expiration date later by [editing the key]({{< ref "nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md#change-expiration-date" >}}).
+Data plane keys expire after one year. You can change this expiration date later by [editing the key]({{< ref "nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md#change-expiration-date" >}}).
 
-[Revoking a data plane key]({{< ref "nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md#revoke-data-plane-key" >}}) disconnects all instances that were registered with that key.
+[Revoking a data plane key]({{< ref "nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md#revoke-data-plane-key" >}}) disconnects all instances that were registered with that key.
 {{</call-out>}}
 
 
diff --git a/content/nginx-one/glossary.md b/content/nginx-one/glossary.md
@@ -14,7 +14,7 @@ This glossary defines terms used in the F5 NGINX One Console and F5 Distributed
 {{<bootstrap-table "table table-striped table-bordered">}}
 | Term        | Definition |
 |-------------|-------------|
-| **Config Sync 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. For more information, see this explanation of [Important considerations]({{< ref "/nginx-one/config-sync-groups/manage-config-sync-groups.md#important-considerations" >}}) |
+| **Config Sync 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. For more information, see this explanation of [Important considerations]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md#important-considerations" >}}) |
 | **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, 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>/` |
diff --git a/content/nginx-one/how-to/_index.md b/content/nginx-one/how-to/_index.md
diff --git a/content/nginx-one/nginx-configs/_index.md b/content/nginx-one/nginx-configs/_index.md
@@ -1,6 +1,6 @@
 ---
 description:
-title: Add and manage your NGINX instances
+title: Manage your NGINX instances
 weight: 300
 url: /nginx-one/nginx-configs
 ---
diff --git a/content/nginx-one/nginx-configs/add-file.md b/content/nginx-one/nginx-configs/add-file.md
@@ -3,7 +3,6 @@ docs: null
 title: Add a file to an instance
 toc: true
 weight: 400
-aliases: /nginx-one/how-to/nginx-configs/add-file/
 type:
 - how-to
 ---
@@ -22,7 +21,7 @@ Before you add files in your configuration, ensure:
 ## Important considerations
 
 If your instance is a member of a Config Sync Group, changes that you make may be synchronized to other instances in that group.
-For more information, see how you can [Manage Config Sync Groups]({{< ref "/nginx-one/config-sync-groups/manage-config-sync-groups.md" >}}).
+For more information, see how you can [Manage Config Sync Groups]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}}).
 
 ## Add a file
 
@@ -63,6 +62,6 @@ Enter the name of the desired configuration file, such as `abc.conf` and select
 
 ## See also
 
-- [Create and manage data plane keys]({{< ref "/nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md" >}})
+- [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md" >}})
 - [Add an NGINX instance]({{< ref "/nginx-one/nginx-configs/add-instance.md" >}})
-- [Manage certificates]({{< ref "/nginx-one/certificates/manage-certificates.md" >}})
+- [Manage certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}})
diff --git a/content/nginx-one/nginx-configs/add-instance.md b/content/nginx-one/nginx-configs/add-instance.md
@@ -3,7 +3,6 @@ description: ''
 title: Add an NGINX instance
 toc: true
 weight: 100
-aliases: /nginx-one/how-to/nginx-configs/add-instance/
 type:
 - how-to
 ---
@@ -20,9 +19,9 @@ Before you add an instance to NGINX One Console, ensure:
 - You have [administrator access]({{< ref "/nginx-one/rbac/roles.md" >}}) to NGINX One Console.
 - You have [configured instances of NGINX]({{< ref "/nginx-one/getting-started.md#add-your-nginx-instances-to-nginx-one" >}}) that you want to manage through NGINX One Console.
 - You have or are ready to configure a [data plane key]({{< ref "/nginx-one/getting-started.md#generate-data-plane-key" >}}).
-- You have or are ready to set up [managed certificates]({{< ref "/nginx-one/certificates/manage-certificates.md" >}}).
+- You have or are ready to set up [managed certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}}).
 
-{{< note >}}If this is the first time an instance is being added to a Config Sync Group, and you have not yet defined the configuration for that Config Sync Group, that instance provides the template for that group. For more information, see [Configuration management]({{< ref "nginx-one/config-sync-groups/manage-config-sync-groups#configuration-management" >}}).{{< /note >}}
+{{< note >}}If this is the first time an instance is being added to a Config Sync Group, and you have not yet defined the configuration for that Config Sync Group, that instance provides the template for that group. For more information, see [Configuration management]({{< ref "nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups#configuration-management" >}}).{{< /note >}}
 
 ## Add an instance
 
@@ -54,5 +53,5 @@ Once you've completed the process, NGINX One reassigns this as a managed certifi
 
 ## Add an instance to a Config Sync Group
 
-When you [Manage Config Sync Group membership]({{< ref "nginx-one/config-sync-groups/manage-config-sync-groups#manage-config-sync-group-membership" >}}), you can add an existing or new instance to the group of your choice.
+When you [Manage Config Sync Group membership]({{< ref "nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups#manage-config-sync-group-membership" >}}), you can add an existing or new instance to the group of your choice.
 That instance inherits the setup of that Config Sync Group.
diff --git a/content/nginx-one/nginx-configs/certificates/_index.md b/content/nginx-one/nginx-configs/certificates/_index.md
diff --git a/content/nginx-one/nginx-configs/certificates/manage-certificates.md b/content/nginx-one/nginx-configs/certificates/manage-certificates.md
@@ -35,7 +35,7 @@ From the NGINX One Console you can:
 You can manage the certificates for:
 
 - [Unique instances]({{< ref "/nginx-one/nginx-configs/add-file.md#new-ssl-certificate-or-ca-bundle" >}})
-- For all instances that are members of a [Config Sync Group]({{< ref "/nginx-one/config-sync-groups/manage-config-sync-groups/#configuration-management" >}})
+- For all instances that are members of a [Config Sync Group]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups/#configuration-management" >}})
 
 
 {{< tip >}}
@@ -193,6 +193,6 @@ To convert these cerificates to managed, start with the Certificates menu, and s
 
 ## See also
 
-- [Create and manage data plane keys]({{< ref "/nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md" >}})
+- [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md" >}})
 - [Add an instance]({{< ref "/nginx-one/nginx-configs/add-instance.md" >}})
 - [Add a file in a configuration]({{< ref "/nginx-one/nginx-configs/add-file.md" >}})
diff --git a/content/nginx-one/nginx-configs/clean-up-unavailable-instances.md b/content/nginx-one/nginx-configs/clean-up-unavailable-instances.md
@@ -4,7 +4,6 @@ docs: null
 title: Clean up unavailable NGINX instances
 toc: true
 weight: 200
-aliases: /nginx-one/how-to/nginx-configs/clean-up-unavailable-instances/
 type:
 - how-to
 ---
diff --git a/content/nginx-one/nginx-configs/config-sync-groups/_index.md b/content/nginx-one/nginx-configs/config-sync-groups/_index.md
diff --git a/content/nginx-one/nginx-configs/config-sync-groups/add-file-csg.md b/content/nginx-one/nginx-configs/config-sync-groups/add-file-csg.md
@@ -59,10 +59,10 @@ Enter the name of the desired configuration file, such as `abc.conf` and select
 ### Existing SSL Certificate or CA Bundle
 
 {{< include "nginx-one/add-file/existing-ssl-bundle.md" >}}
-With this option, You can incorporate [Managed certificates]({{< ref "/nginx-one/certificates/manage-certificates.md#managed-and-unmanaged-certificates" >}}).
+With this option, You can incorporate [Managed certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md#managed-and-unmanaged-certificates" >}}).
 
 ## See also
 
-- [Create and manage data plane keys]({{< ref "/nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md" >}})
+- [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md" >}})
 - [Add an NGINX instance]({{< ref "/nginx-one/nginx-configs/add-instance.md" >}})
-- [Manage certificates]({{< ref "/nginx-one/certificates/manage-certificates.md" >}})
+- [Manage certificates]({{< ref "/nginx-one/nginx-configs/certificates/manage-certificates.md" >}})
diff --git a/content/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md b/content/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md
@@ -3,7 +3,6 @@ docs: null
 title: Manage Config Sync Groups
 toc: true
 weight: 300
-aliases: /nginx-one/how-to/config-sync-groups/manage-config-sync-groups/
 type:
 - how-to
 ---
@@ -183,7 +182,7 @@ When adding a new NGINX instance that is not yet registered with NGINX One, you
 
 Data plane keys are required for registering NGINX instances with the NGINX One Console. These keys serve as secure tokens, ensuring that only authorized instances can connect and communicate with NGINX One.
 
-For more details on creating and managing data plane keys, see [Create and manage data plane keys]({{<ref "/nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md" >}}).
+For more details on creating and managing data plane keys, see [Create and manage data plane keys]({{<ref "/nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md" >}}).
 
 {{</call-out>}}
 
@@ -258,5 +257,5 @@ Monitor the **Config Sync Status** column. It can help you ensure that your conf
 
 ## See also
 
-- [Create and manage data plane keys]({{< ref "/nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md" >}})
+- [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md" >}})
 - [Add an NGINX instance]({{< ref "/nginx-one/nginx-configs/add-instance.md" >}})
diff --git a/content/nginx-one/nginx-configs/view-edit-nginx-configurations.md b/content/nginx-one/nginx-configs/view-edit-nginx-configurations.md
@@ -7,7 +7,6 @@ weight: 300
 toc: true
 # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 type: tutorial
-aliases: /nginx-one/how-to/nginx-configs/view-edit-nginx-configurations/
 # Intended for internal catalogue and search, case sensitive:
 product: NGINX One
 ---
@@ -29,4 +28,4 @@ Alternatively, you can select **Save Changes As**. In the window that appears, y
 
 ## See also
 
-- [Manage Config Sync Groups]({{< ref "/nginx-one/config-sync-groups/manage-config-sync-groups.md" >}})
+- [Manage Config Sync Groups]({{< ref "/nginx-one/nginx-configs/config-sync-groups/manage-config-sync-groups.md" >}})
diff --git a/content/nginx-one/proxy-setup/_index.md b/content/nginx-one/proxy-setup/_index.md
diff --git a/content/nginx-one/proxy-setup/set-up-nginx-proxy-for-nginx-one.md b/content/nginx-one/proxy-setup/set-up-nginx-proxy-for-nginx-one.md
@@ -17,7 +17,7 @@ This guide explains how to set up NGINX as a proxy for other NGINX instances to
 ## Before you start
 
 - [Install NGINX Open Source or NGINX Plus]({{< ref "/nginx/admin-guide/installing-nginx/" >}}).
-- [Get a Data Plane Key from NGINX One]({{< ref "/nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md" >}}).
+- [Get a Data Plane Key from NGINX One]({{< ref "/nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md" >}}).
 
 ---
 
@@ -61,7 +61,7 @@ In this step, we'll configure an NGINX instance to act as a proxy server for NGI
 
 ---
 
-## Configure NGINX Agent to use the proxy instance
+## Configure NGINX Agent to use the proxy
 
 To set up your other NGINX instances to use the proxy instance to connect to NGINX One, update the NGINX Agent configuration on those instances to use the proxy NGINX instance's IP address. See the example NGINX Agent configuration below.
 
@@ -95,7 +95,7 @@ To set up your other NGINX instances to use the proxy instance to connect to NGI
 
 For more information, refer to the following resources:
 
-- [Installing NGINX and NGINX Plus]({{< ref "/nginx/admin-guide/installing-nginx/" >}})
-- [Create and manage data plane keys]({{< ref "/nginx-one/how-to/data-plane-keys/create-manage-data-plane-keys.md" >}})
+- [Install NGINX and NGINX Plus]({{< ref "/nginx/admin-guide/installing-nginx/" >}})
+- [Create and manage data plane keys]({{< ref "/nginx-one/connect-instances/data-plane-keys/create-manage-data-plane-keys.md" >}})
 - [NGINX Agent Installation and upgrade](https://docs.nginx.com/nginx-agent/installation-upgrade/)
-- [NGINX Agent Configuration](https://docs.nginx.com/nginx-agent/configuration/)
+- [NGINX Agent Configuration](https://docs.nginx.com/nginx-agent/configuration/)
diff --git a/content/nginx-one/rbac/_index.md b/content/nginx-one/rbac/_index.md
@@ -1,5 +1,5 @@
 ---
-title: Organize administrators with RBAC
+title: Organize users with RBAC
 description:
 weight: 500
 url: /nginx-one/rbac
diff --git a/content/nginx-one/rbac/overview.md b/content/nginx-one/rbac/overview.md
@@ -4,7 +4,6 @@ weight: 400
 toc: true
 type: reference
 product: NGINX One
-aliases: /nginx-one/how-to/rbac/overview/
 docs: DOCS-000
 ---
 
diff --git a/content/nginx-one/rbac/rbac-api.md b/content/nginx-one/rbac/rbac-api.md
@@ -4,7 +4,6 @@ weight: 500
 toc: true
 type: reference
 product: NGINX One
-aliases: /nginx-one/how-to/rbac/rbac-api/
 docs: DOCS-000
 ---
 
diff --git a/content/nginx-one/rbac/roles.md b/content/nginx-one/rbac/roles.md
@@ -4,7 +4,6 @@ weight: 500
 toc: true
 type: reference
 product: NGINX One
-aliases: /nginx-one/how-to/rbac/roles/
 docs: DOCS-000
 ---
 
diff --git a/content/nginx-one/staged-configs/_index.md b/content/nginx-one/staged-configs/_index.md
@@ -1,6 +1,6 @@
 ---
 description:
-title: Draft new instances (Staged Configs)
+title: Draft new configurations
 weight: 200
 url: /nginx-one/how-to/staged-configs
 ---
diff --git a/content/nginx-one/staged-configs/add-staged-config.md b/content/nginx-one/staged-configs/add-staged-config.md
@@ -7,7 +7,6 @@ weight: 100
 toc: true
 # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 type: tutorial
-aliases: /nginx-one/how-to/staged-configs/add-staged-config/
 # Intended for internal catalogue and search, case sensitive:
 # Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
 product:
diff --git a/content/nginx-one/staged-configs/api-staged-config.md b/content/nginx-one/staged-configs/api-staged-config.md
@@ -7,7 +7,6 @@ weight: 300
 toc: true
 # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 type: tutorial
-aliases: /nginx-one/how-to/staged-configs/api-staged-config/
 # Intended for internal catalogue and search, case sensitive:
 product: NGINX One
 ---
diff --git a/content/nginx-one/staged-configs/edit-staged-config.md b/content/nginx-one/staged-configs/edit-staged-config.md
@@ -7,7 +7,6 @@ weight: 200
 toc: true
 # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 type: tutorial
-aliases: /nginx-one/how-to/staged-configs/edit-staged-config/
 # Intended for internal catalogue and search, case sensitive:
 product: NGINX One
 ---
diff --git a/content/nginx-one/staged-configs/import-export-staged-config.md b/content/nginx-one/staged-configs/import-export-staged-config.md
@@ -7,7 +7,6 @@ weight: 300
 toc: true
 # Types have a 1:1 relationship with Hugo archetypes, so you shouldn't need to change this
 type: how-to
-aliases: /nginx-one/how-to/staged-configs/import-export-staged-config/
 # Intended for internal catalogue and search, case sensitive:
 # Agent, N4Azure, NIC, NIM, NGF, NAP-DOS, NAP-WAF, NGINX One, NGINX+, Solutions, Unit
 product: NGINX One
