WIP: pending changes — docs, webhook, nav/footer (committed per Sami request, not yet reviewed)

src/app/docs/integrations/page.tsx

@@ -0,0 +1,41 @@
+import Navbar from '@/components/Navbar';
+import Footer from '@/components/Footer';
+import DocsLayout from '@/components/docs/DocsLayout';
+
+export default function DocsIntegrationsPage() {
+  return (
+    <div className="flex min-h-screen flex-col bg-surface-950 text-surface-50">
+      <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."
+      >
+        <h2>Docker</h2>
+        <p>
+          Docker is the runtime foundation for deployment workflows, container lifecycle actions, and app-template based launches.
+        </p>
+
+        <h2>Caddy</h2>
+        <p>
+          Caddy is the reverse proxy and HTTPS publication layer. DashCaddy relies on the Caddy Admin API to manage routes and exposure.
+        </p>
+
+        <h2>Technitium DNS</h2>
+        <p>
+          Technitium DNS is the documented DNS automation target for record creation and removal.
+        </p>
+
+        <h2>DashCA</h2>
+        <p>
+          DashCA is the certificate distribution system that makes internal HTTPS practical by letting users trust the local CA across devices.
+        </p>
+
+        <h2>Private access layers</h2>
+        <p>
+          DashCaddy also fits well into private/internal access patterns where services should not be directly exposed to the public internet.
+        </p>
+      </DocsLayout>
+      <Footer />
+    </div>
+  );
+}