clean up client install/configure and add sidebar cta

manage/resources/private/alias.mdx

@@ -3,6 +3,12 @@ title: "Aliases"
 description: "Set a friendly alias hostname that resolves to a host"
 ---
 
+import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
+
+<PangolinCloudTocCta />
+
+
+
 Aliases provide a secondary, user-friendly address for any of your Resources, allowing users to access the Resource using this alternate name in addition to the original address.
 
 For instance, a router with the address `10.0.0.1` could be assigned the alias `router.internal`, and users could connect using either. Aliases are accessible to anyone who has access to the Resource, and they are exclusively accessible when connected with a Pangolin client, meaning they function without requiring any external DNS record setup. Furthermore, aliases are protocol agnostic, which means they will work with any network protocol, essentially acting as a pseudo-A record for an address that is only functional within the Pangolin environment.

manage/resources/private/authentication.mdx

@@ -3,6 +3,12 @@ title: "Authentication"
 description: "Only allow access to Resources to specific users, roles, and machines"
 ---
 
+import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
+
+<PangolinCloudTocCta />
+
+
+
 When a client connects into an organization they will **NOT** have access to any Resources by default. Access must be explicitly granted to users, roles, or machines for a WireGuard tunnel to be established to the site hosting the Resource. The Client will show no peers unless access is granted.
 
 Access can be granted in several ways:

manage/resources/private/destinations.mdx

@@ -3,6 +3,12 @@ title: "Destinations"
 description: "Understand connection options to the remote network"
 ---
 
+import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
+
+<PangolinCloudTocCta />
+
+
+
 A Resource's **destination** can be defined in several ways:
 
 * **Fully Qualified Domain Name (FQDN):** For example, `host.autoco.internal`.

manage/resources/public/authentication.mdx

@@ -3,6 +3,12 @@ title: "Authentication"
 description: "Create identity and context aware rules to allow access"
 ---
 
+import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
+
+<PangolinCloudTocCta />
+
+
+
 Though public resources are public and accessible to via a web browser, admins can create rules to enable a layer of authenticated protection in front of public resources. By default, all public resources have Pangolin auth (Platform SSO) enabled, but a number of other authentication methods are available.
 
 When an unauthenticated user visits a resource in their web browser, they will be redirected to a Pangolin-controlled authentication page where they must complete authentication.

manage/resources/public/healthchecks-failover.mdx

@@ -3,6 +3,12 @@ title: "Health Checks"
 description: "Configure automated health monitoring and failover for resources"
 ---
 
+import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
+
+<PangolinCloudTocCta />
+
+
+
 Pangolin provides automated health checking for targets to ensure traffic is only routed to healthy services. Health checks are essential for building highly available services, as they automatically remove unhealthy targets from traffic routing and load balancing.
 
 ## How Health Checks Work

manage/resources/public/maintenance.mdx

@@ -3,6 +3,12 @@ title: "Maintenance Page"
 description: "Show a maintenance page to users when a resources is down for maintenance or targets are unhealthy"
 ---
 
+import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
+
+<PangolinCloudTocCta />
+
+
+
 <Note>
 Maintenance pages are only available in [Enterprise Edition](/self-host/enterprise-edition).
 </Note>

manage/resources/public/raw-resources.mdx

@@ -3,6 +3,12 @@ title: "TCP & UDP"
 description: "Configure raw TCP and UDP traffic through Pangolin tunnels"
 ---
 
+import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
+
+<PangolinCloudTocCta />
+
+
+
 <Note>
 This feature is only available in self-hosted Pangolin instances. If you're using Pangolin Cloud, you will need to deploy a remote node.
 </Note>

manage/resources/public/targets.mdx

@@ -3,6 +3,12 @@ title: "Targets"
 description: "Configure destination endpoints for resource routing and load balancing"
 ---
 
+import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
+
+<PangolinCloudTocCta />
+
+
+
 When you create a resource in Pangolin, you define different targets that specify where traffic should be routed within your network. Each target represents a specific destination that the resource can proxy to when handling incoming requests.
 
 ## How Targets Work

manage/resources/understanding-resources.mdx

@@ -3,6 +3,12 @@ title: "Understanding Resources"
 description: "Resources are any network address you want to make available to users"
 ---
 
+import PangolinCloudTocCta from "/snippets/pangolin-cloud-toc-cta.mdx";
+
+<PangolinCloudTocCta />
+
+
+
 Resources represent the applications, hosts, or ranges you make available for remote access to users. Resources exist on the remote networks of your sites. Users only ever think about connecting to resources and not specific sites.
 
 By default, no resources are made available on sites. Admins must define resources with backend targets, and assign specific access policies before any users can gain access.