Table class updates

docs/reference/spaces-helm-reference.md

@@ -18,6 +18,8 @@ This reference provides detailed documentation on the Upbound Space Helm chart.
 
 ## Values
 
+<div class="helm-table">
+
 | Key | Type | Default | Description |
 |-----|------|---------|-------------|
 | account | string | `"notdemo"` | The Upbound organization this installation is associated with. |
@@ -401,6 +403,7 @@ This reference provides detailed documentation on the Upbound Space Helm chart.
 | space.labels | object | `{}` | Labels that are applied to all Deployments, Pods, Services, and StatefulSets managed by the Space. |
 | version | string | `""` | Overall artifact version that affects xpkgs and related components. |
 
+</div>
 
 <!-- vale on -->
 

docs/reference/uxp-helm-reference.md

@@ -12,6 +12,8 @@ This reference provides detailed documentation on the UXP Helm chart. This Helm
 
 ## Values
 
+<div class="helm-table">
+
 | Key | Type | Default | Description |
 |-----|------|---------|-------------|
 | affinity | object | `{}` | Add `affinities` to the Crossplane pod deployment. |
@@ -98,6 +100,8 @@ This reference provides detailed documentation on the UXP Helm chart. This Helm
 | webhooks.enabled | bool | `true` | Enable webhooks for Crossplane and installed Provider packages. |
 | webhooks.port | string | `""` | The port the webhook server listens on. |
 
+</div>
+
 <!-- vale on -->
 
 <!-- end-table-no -->

src/css/custom.css

@@ -411,20 +411,27 @@ html[data-theme="dark"] .planBadge {
 article table,
 .theme-doc-markdown table,
 table {
+    border-collapse: collapse;
+    border-radius: 0.75rem;
+    margin: 0;
+    box-shadow: var(--upbound-card-shadow);
+    border: 1px solid var(--upbound-border-color);
+    background-color: var(--ifm-background-color);
+    font-size: 0.9rem;
+    width: fit-content;
+}
+
+/* Helm tables with scroll behavior */
+.helm-table table {
     display: block;
     width: auto;
     min-width: 50%;
     max-width: 100%;
     border-collapse: separate;
     border-spacing: 0;
-    border-radius: 0.75rem;
     overflow-x: auto;
     -webkit-overflow-scrolling: touch;
-    margin: 1.5rem 0;
-    box-shadow: var(--upbound-card-shadow);
-    border: 1px solid var(--upbound-border-color);
-    background-color: var(--ifm-background-color);
-    font-size: 0.9rem;
+    margin: 1rem 0;
 }
 
 /* Scrollable table wrapper - use with <ScrollTable> component */

static/cli/up_resource_count.md

@@ -8,13 +8,13 @@ Count Crossplane resources in a cluster.
 The `up resource count` command counts Crossplane resources in a Kubernetes cluster,
 providing a summary of managed resources, composite resources, claims, and composed resources.
 
-## Usage
+#### Usage
 
 ```bash
 up resource count [flags]
 ```
 
-### Examples
+#### Examples
 
 ```bash
 # Count resources using the current kubeconfig context
@@ -33,7 +33,7 @@ up resource count --format json
 up resource count --format yaml
 ```
 
-## Resource Types
+#### Resource Types
 
 The command counts the following Crossplane resource types:
 
@@ -43,7 +43,7 @@ The command counts the following Crossplane resource types:
 - **Composed Resources**: Resources that are part of a composite resource's composition
 - **Total Resources**: Sum of all counted resources
 
-## Notes
+#### Notes
 
 - Resources are deduplicated to avoid double-counting
 - ProviderConfig and related resources are excluded from the count

static/cli/up_support-bundle_collect.md

@@ -8,13 +8,13 @@ Collect a support bundle from the current kube context.
 The `up support-bundle collect` command allows you to collect diagnostic information from
 your Kubernetes cluster or control plane for troubleshooting purposes.
 
-## Usage
+#### Usage
 
 ```bash
 up support-bundle collect [flags]
 ```
 
-### Examples
+#### Examples
 
 ```bash
 # Collect a support bundle with default settings
@@ -44,7 +44,7 @@ up support-bundle collect --exclude-namespaces upbound-*
 up support-bundle collect --crossplane-resources-only
 ```
 
-## Configuration File
+#### Configuration File
 
 You can provide a custom SupportBundle configuration file using the `--config` flag.
 The configuration file can include both the SupportBundle spec and Redactors in a
@@ -64,7 +64,7 @@ up support-bundle template > my-config.yaml
 up support-bundle collect --config my-config.yaml
 ```
 
-## Security
+#### Security
 
 All sensitive information is automatically redacted from the support bundle,
 including:

static/cli/up_support-bundle_serve.md

@@ -12,13 +12,13 @@ Kubernetes tools like `kubectl` or `k9s`.
 
 Note: This runs only the API server for viewing collected data, no workloads are actually running.
 
-## Usage
+#### Usage
 
 ```bash
 up support-bundle serve [path] [flags]
 ```
 
-### Examples
+#### Examples
 
 ```bash
 # Serve a support bundle tar.gz file
@@ -31,7 +31,7 @@ up support-bundle serve --port 9090
 up support-bundle serve --kubeconfig-path ./my-kubeconfig
 ```
 
-## Viewing the Bundle
+#### Viewing the Bundle
 
 Once the server is running, you can use standard Kubernetes tools to view the bundle contents:
 

static/cli/up_support-bundle_template.md

@@ -8,13 +8,13 @@ Output the default SupportBundle YAML configuration template.
 The `up support-bundle template` command outputs the default SupportBundle YAML configuration
 template that can be used as a starting point for custom support bundle configurations.
 
-## Usage
+#### Usage
 
 ```bash
 up support-bundle template [flags]
 ```
 
-### Examples
+#### Examples
 
 ```bash
 # Output the default support bundle template