[SSL] Fix unnecessary overviews (#16883)

* First pass adding all hideIndex: true

* Rename custom-origin-trust-store.mdx and delete empty folder

* Rename page with TroubleshootingList component

* Re-org  AOP setup: hide index and move extra content to new page

* Add DirectoryListing to index.mdx in aop/set-up

Author: RebeccaTamachiro

src/content/docs/ssl/edge-certificates/additional-options/index.mdx

@@ -3,6 +3,8 @@ pcx_content_type: navigation
 title: Additional options
 sidebar:
   order: 11
+  group:
+    hideIndex: true
 
 ---
 

src/content/docs/ssl/edge-certificates/troubleshooting/index.mdx

@@ -3,6 +3,8 @@ pcx_content_type: navigation
 title: Troubleshooting
 sidebar:
   order: 12
+  group:
+    hideIndex: true
 head:
   - tag: title
     content: Troubleshooting edge certificates

src/content/docs/ssl/keyless-ssl/configuration/index.mdx

@@ -3,6 +3,8 @@ title: Get started
 pcx_content_type: navigation
 sidebar:
   order: 1
+  group:
+    hideIndex: true
 head:
   - tag: title
     content: Get started with Keyless SSL

src/content/docs/ssl/keyless-ssl/reference/index.mdx

@@ -3,6 +3,8 @@ title: Reference
 pcx_content_type: navigation
 sidebar:
   order: 5
+  group:
+    hideIndex: true
 head:
   - tag: title
     content: Reference — Keyless SSL

src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/index.mdx

@@ -2,57 +2,15 @@
 pcx_content_type: how-to
 title: Setup
 sidebar:
-  order: 2
+  order: 3
+  group:
+    hideIndex: true
 head:
   - tag: title
     content: Set up Authenticated Origin Pulls
 
 ---
 
-import { Render } from "~/components"
+import { DirectoryListing } from "~/components"
 
-To set up Authenticated Origin Pulls - which help ensure requests to your origin server come from the Cloudflare network - choose whether to enable them on [all hostnames in your zone](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) or on a [per-hostname basis](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/).
-
-:::caution
- <Render file="aop-per-hostname-cert-requirement" /> 
-:::
-
-***
-
-## Other situations
-
-### Use specialized certificates
-
-To apply different client certificates simultaneously at both the zone and hostname level, you can combine zone-level and per-hostname custom certificates.
-
-First set up [zone-level pulls](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) using a certificate. Then, upload multiple, specialized certificates for [individual hostnames](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/).
-
-:::note[Note]
-
-
-Since per-hostname certificates are more specific, they take precedence over zone certificates.
-
-
-:::
-
-### Delete a certificate
-
-Client certificates are not deleted from Cloudflare upon expiration unless a [delete](/api/operations/zone-level-authenticated-origin-pulls-delete-certificate) or [replace](/api/operations/zone-level-authenticated-origin-pulls-upload-certificate) request is sent to the Cloudflare API.
-
-However, requests are dropped at your origin if your origin only accepts a valid client certificate.
-
-### Replace a client cert (without downtime)
-
-For hostname:
-
-1. [Upload the new certificate](/api/operations/per-hostname-authenticated-origin-pull-upload-a-hostname-client-certificate).
-
-2. [Enable Authenticated Origin Pulls for that specific hostname](/api/operations/per-hostname-authenticated-origin-pull-enable-or-disable-a-hostname-for-client-authentication).
-
-For global:
-
-1. [Upload the new certificate](/api/operations/zone-level-authenticated-origin-pulls-upload-certificate).
-
-2. [Check whether new certificate is Active](/api/operations/zone-level-authenticated-origin-pulls-get-certificate-details).
-
-3. Once certificate is active, [delete the previous certificate](/api/operations/zone-level-authenticated-origin-pulls-delete-certificate).
+<DirectoryListing />

src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/manage-certificates.mdx

@@ -0,0 +1,48 @@
+---
+pcx_content_type: how-to
+title: Manage certificates
+sidebar:
+  order: 3
+head:
+  - tag: title
+    content: Set up Authenticated Origin Pulls
+
+---
+
+Refer to the following sections to learn how to manage certificates used with the different Authenticated Origin Pulls setups.
+
+## Use specialized certificates
+
+To apply different client certificates simultaneously at both the zone and hostname level, you can combine zone-level and per-hostname custom certificates.
+
+First set up [zone-level pulls](/ssl/origin-configuration/authenticated-origin-pull/set-up/zone-level/) using a certificate. Then, upload multiple, specialized certificates for [individual hostnames](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/).
+
+:::note[Note]
+
+
+Since per-hostname certificates are more specific, they take precedence over zone certificates.
+
+
+:::
+
+## Delete a certificate
+
+Client certificates are not deleted from Cloudflare upon expiration unless a [delete](/api/operations/zone-level-authenticated-origin-pulls-delete-certificate) or [replace](/api/operations/zone-level-authenticated-origin-pulls-upload-certificate) request is sent to the Cloudflare API.
+
+However, requests are dropped at your origin if your origin only accepts a valid client certificate.
+
+## Replace a client cert (without downtime)
+
+For hostname:
+
+1. [Upload the new certificate](/api/operations/per-hostname-authenticated-origin-pull-upload-a-hostname-client-certificate).
+
+2. [Enable Authenticated Origin Pulls for that specific hostname](/api/operations/per-hostname-authenticated-origin-pull-enable-or-disable-a-hostname-for-client-authentication).
+
+For global:
+
+1. [Upload the new certificate](/api/operations/zone-level-authenticated-origin-pulls-upload-certificate).
+
+2. [Check whether new certificate is Active](/api/operations/zone-level-authenticated-origin-pulls-get-certificate-details).
+
+3. Once certificate is active, [delete the previous certificate](/api/operations/zone-level-authenticated-origin-pulls-delete-certificate).

src/content/docs/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname.mdx

@@ -13,15 +13,18 @@ import { AvailableNotifications, Render } from "~/components"
 
 When you enable Authenticated Origin Pulls per hostname, all proxied traffic to the specified hostname is authenticated at the origin web server. You can use client certificates from your Private PKI to authenticate connections from Cloudflare.
 
-<Render file="aop-per-hostname-cert-requirement" /><br />
+
+:::caution[Warning]
+ <Render file="aop-per-hostname-cert-requirement" />
+:::
 
 ## 1. Upload custom certificate
 
 First, follow the API instructions to [upload a custom certificate to Cloudflare](/ssl/edge-certificates/custom-certificates/uploading/#upload-a-custom-certificate), but use the [`/origin_tls_client_auth/hostnames/certificates` endpoint](/api/operations/per-hostname-authenticated-origin-pull-upload-a-hostname-client-certificate).
 
 :::note
 
-You must upload a [leaf certificate](/ssl/concepts/#chain-of-trust). If you upload a root CA instead, the API will return a `missing leaf certificate` error. 
+You must upload a [leaf certificate](/ssl/concepts/#chain-of-trust). If you upload a root CA instead, the API will return a `missing leaf certificate` error.
 :::
 
 In the API response, save the certificate `id` since it will be required in step 4.

src/content/docs/ssl/origin-configuration/custom-origin-trust-store/index.mdx renamed to src/content/docs/ssl/origin-configuration/custom-origin-trust-store.mdx

@@ -3,6 +3,8 @@ title: Origin server
 pcx_content_type: navigation
 sidebar:
   order: 5
+  group:
+    hideIndex: true
 
 ---
 

src/content/docs/ssl/origin-configuration/index.mdx

@@ -3,6 +3,8 @@ title: Reference
 pcx_content_type: navigation
 sidebar:
   order: 10
+  group:
+    hideIndex: true
 
 ---