Refactor documentation and update client references for clarity

- Updated multiple documentation files to replace references to the old Pomerium CLI and Desktop client links with the new consolidated guide at /docs/deploy/clients.
- Revised links in various sections to ensure accurate navigation for TCP and UDP connections, enhancing user guidance on non-HTTP protocols.
- Removed outdated client documentation files and images, streamlining the resource structure for better accessibility.
- Improved overall clarity and consistency in documentation formatting and terminology.

These changes enhance the usability and coherence of the documentation, providing users with a more organized resource for managing Pomerium's capabilities.

Author: desimone

.pre-commit-config.yaml

@@ -4,7 +4,7 @@ repos:
     hooks:
       - id: prettier
         additional_dependencies:
-          - "prettier@3.4.2"
+          - 'prettier@3.4.2'
         files: ^content\/.*$
         exclude: content/docs/deploy/k8s/reference.md
   - repo: https://github.com/streetsidesoftware/cspell-cli

content/docs/capabilities/kubernetes-access.mdx

@@ -83,7 +83,7 @@ rules:
 
 2. A [route's policy](/docs/reference/routes/policy) is created for the API server and [configured](/docs/reference/routes/kubernetes-service-account-token) to use the service account token
 3. Kubernetes RoleBindings operate against IdP Users and Group subjects
-4. Users access the protected cluster through their standard tools, using [pomerium-cli](/docs/capabilities/non-http/client) as an auth provider in `~/.kube/config`
+4. Users access the protected cluster through their standard tools, using [pomerium-cli](/docs/deploy/clients) as an auth provider in `~/.kube/config`
 5. Pomerium authorizes requests and passes the user identity to the API server for fine grained RBAC
 
 </TabItem>
@@ -215,7 +215,7 @@ Then, your user should be authorized:
 
 ## Kubeconfig Setup
 
-Edit your kubeconfig to use [pomerium-cli](/docs/capabilities/non-http/client) as a [credential plugin](https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins):
+Edit your kubeconfig to use [pomerium-cli](/docs/deploy/clients) as a [credential plugin](https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins):
 
 ```yaml
 apiVersion: v1

content/docs/capabilities/non-http/client.mdx

@@ -21,7 +21,7 @@ This example assumes you've already [created a TCP route](/docs/capabilities/non
 
  ## Basic Connection
 
- 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/capabilities/non-http/client) or the Pomerium Desktop client:
+ 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/deploy/clients) or the Pomerium Desktop client:
 
     <Tabs>
     <TabItem value="pomerium-cli" label="pomerium-cli">

content/docs/capabilities/non-http/examples/_service-template.mdx

@@ -23,7 +23,7 @@ This example assumes you've already [created a TCP route](/docs/capabilities/non
 
  ## Basic Connection
 
- 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/capabilities/non-http/client) or the Pomerium Desktop client. These examples use Git connections over SSH:
+ 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/deploy/clients) or the Pomerium Desktop client. These examples use Git connections over SSH:
 
     <Tabs>
     <TabItem value="pomerium-cli" label="pomerium-cli">

content/docs/capabilities/non-http/examples/git.mdx

@@ -26,7 +26,7 @@ This example assumes you've already [created a TCP route](/docs/capabilities/non
 
  ## Basic Connection
 
- 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/capabilities/non-http/client) or the Pomerium Desktop client:
+ 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/deploy/clients) or the Pomerium Desktop client:
 
     <Tabs>
     <TabItem value="pomerium-cli" label="pomerium-cli">

content/docs/capabilities/non-http/examples/img/factorio-ticks.png

@@ -23,7 +23,7 @@ This example assumes you've already [created a TCP route](/docs/capabilities/non
 
  ## Basic Connection
 
- 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/capabilities/non-http/client) or the Pomerium Desktop client:
+ 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/deploy/clients) or the Pomerium Desktop client:
 
     <Tabs>
     <TabItem value="pomerium-cli" label="pomerium-cli">

content/docs/capabilities/non-http/examples/ms-sql.mdx

@@ -11,7 +11,7 @@ PostgreSQL is a popular relational database used in many modern applications. Th
 
 ## Basic Connection
 
-1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/capabilities/non-http/client) or the Pomerium Desktop client:
+1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/deploy/clients) or the Pomerium Desktop client:
 
 <Tabs>
 <TabItem label="pomerium-cli" value="pomerium-cli">

content/docs/capabilities/non-http/examples/mysql.mdx

@@ -24,7 +24,7 @@ This example assumes you've already [created a TCP route](/docs/capabilities/non
 
 ## Basic Connection
 
-1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/capabilities/non-http/client) or the Pomerium Desktop client:
+1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/deploy/clients) or the Pomerium Desktop client:
 
     <Tabs>
     <TabItem value="pomerium-cli" label="pomerium-cli">

content/docs/capabilities/non-http/examples/postgres.mdx

@@ -23,7 +23,7 @@ This example assumes you've already [created a TCP route](/docs/capabilities/non
 
 ## Basic Connection
 
- 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/capabilities/non-http/client) or the Pomerium Desktop client:
+ 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/deploy/clients) or the Pomerium Desktop client:
 
     <Tabs>
     <TabItem value="pomerium-cli" label="pomerium-cli">

content/docs/capabilities/non-http/examples/rdp.mdx

@@ -30,7 +30,7 @@ This example assumes you've already [created a TCP route](/docs/capabilities/non
 
  ## Basic Connection
 
- 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/capabilities/non-http/client) or the Pomerium Desktop client:
+ 1. Create a TCP tunnel, using either [`pomerium-cli`](/docs/deploy/clients) or the Pomerium Desktop client:
 
     <Tabs>
     <TabItem value="pomerium-cli" label="pomerium-cli">

content/docs/capabilities/non-http/examples/redis.mdx

@@ -25,7 +25,7 @@ import LongLivedConnections from '@site/content/docs/admonitions/_long-lived-con
 
 # TCP over HTTP Support
 
-In addition to managing HTTP based applications, Pomerium can be used to protect non-HTTP systems with the same consistent authorization policy. This is achieved by tunneling TCP over HTTP with the help of a client side command built into [`pomerium-cli`](/docs/capabilities/non-http/client).
+In addition to managing HTTP based applications, Pomerium can be used to protect non-HTTP systems with the same consistent authorization policy. This is achieved by tunneling TCP over HTTP with the help of a client side command built into [`pomerium-cli`](/docs/deploy/clients).
 
 Operations and engineering teams frequently require access to lower level administrative and data protocols such as SSH, RDP, Postgres, MySQL, Redis, etc.
 
@@ -66,7 +66,7 @@ When creating TCP routes, note the following:
 
 ## Connect to TCP Routes
 
-While HTTP routes can be consumed with just a normal browser, `pomerium-cli` or Pomerium Desktop must serve as a proxy for TCP routes. See [Pomerium Desktop and CLI Clients](/docs/capabilities/non-http/client) for more information.
+While HTTP routes can be consumed with just a normal browser, `pomerium-cli` or Pomerium Desktop must serve as a proxy for TCP routes. See [Pomerium Desktop and CLI Clients](/docs/deploy/clients) for more information.
 
 To connect, you normally need just the external hostname and port of your TCP route:
 

content/docs/capabilities/non-http/examples/ssh.mdx

@@ -20,7 +20,7 @@ import CLIClientCertificates from './_cli-client-certificates.mdx';
 
 # UDP over HTTP Support
 
-Starting in v0.29, Pomerium can be used to protect UDP systems with the same consistent authorization policy. This is achieved by tunneling UDP over HTTP with the help of a client side command built into [`pomerium-cli`](/docs/capabilities/non-http/client).
+Starting in v0.29, Pomerium can be used to protect UDP systems with the same consistent authorization policy. This is achieved by tunneling UDP over HTTP with the help of a client side command built into [`pomerium-cli`](/docs/deploy/clients).
 
 Internally, Pomerium uses [`CONNECT-UDP`](https://datatracker.ietf.org/doc/html/rfc9298) to establish the UDP tunnel.