Major site overhaul: reflect all current product features + logo + Stripe Payment Links

Homepage: AI-powered hero, 9 feature cards (AI Intent Router, MCP Server,
Security Center, Fleet Management, Service Discovery, Plugin System),
expanded comparison table (7→13 rows), Smart Wizard in How It Works

Features page: Complete rewrite — 8 feature sections led by AI-Powered
Self-Hosting, Free vs Premium comparison grid

Pricing page: Fixed broken Stripe checkout (was 503 stub). Subscribe
button now uses Stripe Payment Links. Core tier lists all 18 features.

All 7 docs pages: Updated to reflect current architecture (AI, MCP,
Security Center, SDK, Caddyfile-as-Code, Service Discovery, etc.)

About page: AI-Native value prop, updated tech stack, by-the-numbers

Navbar: Fixed broken #anchor links → proper routes, added DashCaddy logo

AppShowcase: 50+ → 76+ templates

Logo: Dark + light versions deployed, wired into navbar/footer/favicon

src/app/docs/integrations/page.tsx

@@ -8,32 +8,83 @@ export default function DocsIntegrationsPage() {
       <Navbar />
       <DocsLayout
         title="Infrastructure Integrations"
-        intro="DashCaddy is most valuable when its supporting integrations are healthy. This guide explains the layers it expects to work with and how they fit together."
+        intro="DashCaddy is most valuable when its supporting integrations are healthy. This guide explains each layer it expects to work with, what it does, and how the pieces fit together into a single control plane."
       >
         <h2>Docker</h2>
         <p>
-          Docker is the runtime foundation for deployment workflows, container lifecycle actions, and app-template based launches.
+          Docker (and Docker Compose) is the runtime foundation for deployment workflows, container lifecycle actions,
+          service discovery, and template-based launches. DashCaddy talks to the Docker daemon to start, stop, restart,
+          inspect, and adopt containers, and to deploy the 76+ one-click application templates. Optional Docker Swarm
+          support (Premium) extends the same model across multiple nodes.
         </p>
 
-        <h2>Caddy</h2>
+        <h2>Caddy — reverse proxy &amp; HTTPS</h2>
         <p>
-          Caddy is the reverse proxy and HTTPS publication layer. DashCaddy relies on the Caddy Admin API to manage routes and exposure.
+          Caddy is the reverse proxy and automatic HTTPS layer. DashCaddy communicates with the <strong>Caddy Admin API</strong>
+          to create, update, and remove routes, and to trigger certificate issuance. Caddy&apos;s built-in internal CA
+          auto-generates and renews certificates for every published service.
+        </p>
+
+        <h3>Caddyfile-as-Code</h3>
+        <p>
+          Instead of hand-editing Caddyfiles, DashCaddy exposes a <strong>visual Caddyfile-as-Code builder</strong>. You
+          describe the desired route — hostname, upstream, TLS options, headers, redirects — and DashCaddy generates the
+          valid Caddy configuration and applies it atomically through the Admin API. Configuration is versioned and
+          reviewable, so changes are auditable and reversible.
         </p>
 
         <h2>Technitium DNS</h2>
         <p>
-          Technitium DNS is the documented DNS automation target for record creation and removal.
+          Technitium DNS is the DNS automation target for record creation and removal. When you deploy or adopt a service,
+          DashCaddy creates the corresponding A/CNAME record through the Technitium API so the new hostname resolves
+          immediately. Removing a service cleans up the record automatically.
         </p>
 
-        <h2>DashCA</h2>
+        <h2>DashCA — internal certificate authority</h2>
         <p>
-          DashCA is the certificate distribution system that makes internal HTTPS practical by letting users trust the local CA across devices.
+          DashCA is the certificate distribution system that makes internal HTTPS practical. Caddy&apos;s internal CA
+          issues certificates automatically; DashCA provides the distribution page where you download the root
+          certificate and install it as a trusted CA across your devices. Once trusted, every internal service is served
+          over valid HTTPS with no browser warnings.
         </p>
 
-        <h2>Private access layers</h2>
+        <h2>Tailscale — private access</h2>
         <p>
-          DashCaddy also fits well into private/internal access patterns where services should not be directly exposed to the public internet.
+          DashCaddy fits naturally into private access patterns with <strong>Tailscale</strong>. Services can be published
+          only on a Tailnet, keeping them off the public internet while still benefiting from DashCaddy&apos;s DNS, proxy,
+          and TLS automation. This is ideal for home labs and internal team tools.
         </p>
+
+        <h2>Prometheus &amp; Grafana — metrics</h2>
+        <p>
+          DashCaddy exports metrics in Prometheus format at <code>/metrics</code>, including service health, container
+          status, request counts, and system indicators. Point your Prometheus scraper at the endpoint and build
+          Grafana dashboards on top for long-term observability and alerting.
+        </p>
+        <pre className="mt-4 overflow-x-auto rounded-lg border border-surface-700/50 bg-surface-950/80 p-4 text-sm"><code>{`# prometheus.yml scrape config
+scrape_configs:
+  - job_name: 'dashcaddy'
+    metrics_path: /metrics
+    static_configs:
+      - targets: ['dashcaddy-host:3000']`}</code></pre>
+
+        <h2>MCP &amp; AI assistants</h2>
+        <p>
+          The built-in <strong>MCP Server</strong> exposes DashCaddy operations to AI assistants and external automation.
+          Combined with the <strong>AI Intent Router</strong>, you can issue natural-language commands
+          (&ldquo;restart the media server&rdquo;, &ldquo;deploy the postgres template&rdquo;) and have DashCaddy execute
+          the real infrastructure action. See the <a href="/docs/api">API and Automation</a> guide for details.
+        </p>
+
+        <h2>How the layers fit together</h2>
+        <ul>
+          <li><strong>Deploy / Adopt</strong> → Docker runs the container.</li>
+          <li><strong>Publish</strong> → Caddy creates the reverse-proxy route and TLS cert.</li>
+          <li><strong>Resolve</strong> → Technitium DNS creates the hostname record.</li>
+          <li><strong>Trust</strong> → DashCA distributes the root CA for internal HTTPS.</li>
+          <li><strong>Observe</strong> → health checks + Prometheus + WebSocket live updates.</li>
+          <li><strong>Secure</strong> → Security Center aggregates events; audit logging records every change.</li>
+        </ul>
       </DocsLayout>
       <Footer />
     </div>