docs: Add transport docs

aklinker1 · aklinker1 · commit 8c2cfa59de10 · 2026-03-14T15:20:42.000-05:00
diff --git a/docs/content/server/mounting.md b/docs/content/server/mounting.md
@@ -1,7 +1,7 @@
 ---
 title: Mount Fetch Functions
 description: Zeta is WinterCG compliant, meaning you can mount other standard server-side fetch functions on your app.
-weight: 6
+weight: 7
 ---
 
 ## Overview
diff --git a/docs/content/server/transports.md b/docs/content/server/transports.md
@@ -0,0 +1,54 @@
+---
+title: Transports
+description: Transports provide access to runtime-specific APIs.
+weight: 6
+---
+
+By default, Zeta uses `createFetchTransport`. It detects your runtime and provides a minimal transport that supports Bun and Deno.
+
+## Runtime-specific Decorations
+
+The default fetch transport not provide access to runtime-specific APIs. For example, in Bun, you use the `server` arg to setup websockets or get the request IP address:
+
+```ts
+Bun.serve({
+  fetch: (request, server) => {
+    const ip = server.requestIP(request);
+    // ...
+  },
+});
+```
+
+To access the same object, you need to provide a custom `transport` then transport-specific APIs will be available in the request context:
+
+```ts
+import { createApp } from "@aklinker1/zeta";
+import { createBunTransport } from "@aklinker1/zeta/transports/bun-transport";
+
+const app = createApp({
+  transport: createBunTransport(),
+}).get(({ request, server }) => {
+  const ip = server.requestIP(request);
+  // ...
+});
+```
+
+You only have to add the transport once, to your top-level app, and any runtime-specific decorations will be made available in all child-apps as well!
+
+## Transport Options
+
+Some transports also support passing custom options:
+
+```ts
+import { createBunTransport } from "@aklinker1/zeta/transports/bun-transport";
+
+const transport = createBunTransport({
+  websocket: {
+    // ...
+  },
+});
+
+const app = createApp({
+  transport,
+});
+```
