moved metadata task examples to metadata

Author: D-K-P

docs/realtime/backend/subscribe.mdx

@@ -192,7 +192,7 @@ async function monitorProgress(runId: string) {
 }
 ```
 
-For more information on how to write tasks that use the metadata API, see our [run metadata docs](/runs/metadata).
+For more information on how to write tasks that use the metadata API, as well as more examples, see our [run metadata docs](/runs/metadata#more-metadata-task-examples).
 
 ### Type safety
 
@@ -223,99 +223,3 @@ async function monitorTypedProgress(runId: string) {
   }
 }
 ```
-
-### Common metadata patterns
-
-#### Progress tracking
-
-Track progress with percentage and current step:
-
-```ts
-import { task, metadata } from "@trigger.dev/sdk/v3";
-
-export const batchProcessingTask = task({
-  id: "batch-processing",
-  run: async (payload: { records: any[] }) => {
-    for (let i = 0; i < payload.records.length; i++) {
-      const record = payload.records[i];
-
-      // Update progress
-      metadata.set("progress", {
-        step: i + 1,
-        total: payload.records.length,
-        percentage: Math.round(((i + 1) / payload.records.length) * 100),
-        currentRecord: record.id,
-      });
-
-      await processRecord(record);
-    }
-  },
-});
-```
-
-#### Status updates with logs
-
-Append log entries while maintaining status:
-
-```ts
-import { task, metadata } from "@trigger.dev/sdk/v3";
-
-export const deploymentTask = task({
-  id: "deployment",
-  run: async (payload: { version: string }) => {
-    metadata.set("status", "initializing");
-    metadata.append("logs", "Starting deployment...");
-
-    // Step 1
-    metadata.set("status", "building");
-    metadata.append("logs", "Building application...");
-    await buildApplication();
-
-    // Step 2
-    metadata.set("status", "deploying");
-    metadata.append("logs", "Deploying to production...");
-    await deployToProduction();
-
-    // Step 3
-    metadata.set("status", "verifying");
-    metadata.append("logs", "Running health checks...");
-    await runHealthChecks();
-
-    metadata.set("status", "completed");
-    metadata.append("logs", "Deployment successful!");
-  },
-});
-```
-
-#### User context and notifications
-
-Store user information and notification preferences:
-
-```ts
-import { task, metadata } from "@trigger.dev/sdk/v3";
-
-export const userTask = task({
-  id: "user-task",
-  run: async (payload: { userId: string; action: string }) => {
-    // Set user context in metadata
-    metadata.set("user", {
-      id: payload.userId,
-      action: payload.action,
-      startedAt: new Date().toISOString(),
-    });
-
-    // Update status for user notifications
-    metadata.set("notification", {
-      type: "info",
-      message: `Starting ${payload.action} for user ${payload.userId}`,
-    });
-
-    await performUserAction(payload);
-
-    metadata.set("notification", {
-      type: "success",
-      message: `${payload.action} completed successfully`,
-    });
-  },
-});
-```

docs/realtime/overview.mdx

@@ -8,13 +8,9 @@ import RealtimeExamplesCards from "/snippets/realtime-examples-cards.mdx";
 
 Trigger.dev Realtime allows you to trigger, subscribe to, and get real-time updates for runs. This is useful for monitoring runs, updating UIs, and building real-time dashboards.
 
-## Authentication
-
-All Realtime subscriptions require authentication so you can securely trigger and subscribe to runs. See our [authentication guide](/realtime/auth) for more details.
-
 ## What you can do with Realtime
 
-You can subscribe to real-time updates for different scopes of runs:
+Subscribe to real-time updates for different scopes of runs:
 
 - **Specific runs** - Monitor individual run progress by run ID
 - **Runs with specific tags** - Track all runs that have certain [tags](/tags) (e.g., all runs tagged with `user:123`)
@@ -28,6 +24,10 @@ Once subscribed, you'll receive the complete [run object](/realtime/run-object)
 - **Tag changes** - When [tags](/tags) are added or removed from the run
 - **Stream data** - Real-time data chunks from your tasks, perfect for AI/LLM streaming ([React hooks](/realtime/react-hooks/streams) | [backend](/realtime/backend/streams))
 
+## Authentication
+
+All Realtime subscriptions require authentication so you can securely trigger and subscribe to runs. See our [authentication guide](/realtime/auth) for more details.
+
 ## Realtime approaches
 
 ### Frontend implementation

docs/realtime/react-hooks/subscribe.mdx

@@ -196,14 +196,11 @@ export function MyComponent({ batchId }: { batchId: string }) {
 
 See our [Realtime documentation](/realtime) for more information.
 
-## Using Metadata
+## Using metadata to show progress in your UI
 
 All realtime hooks automatically include metadata updates. Whenever your task updates metadata using `metadata.set()`, `metadata.append()`, or other metadata methods, your component will re-render with the updated data.
 
-<Note>
-  To learn how to write tasks with metadata updates, see our [writing tasks using
-  metadata](/runs/metadata) guide.
-</Note>
+<Note>To learn how to write tasks using metadata, see our [metadata](/runs/metadata) guide.</Note>
 
 ### Progress monitoring
 

docs/runs/metadata.mdx

@@ -514,6 +514,104 @@ Combined with [Realtime](/realtime), you could use this to show a live progress
   height="100%"
 />
 
+## More metadata task examples
+
+Using metadata updates in conjunction with our [Realtime React hooks](/realtime/react-hooks/overview) can be a powerful way to build real-time UIs. Here are some example tasks demonstrating how to use metadata in your tasks to track progress, status, and more:
+
+### Progress tracking
+
+Track progress with percentage and current step:
+
+```ts
+import { task, metadata } from "@trigger.dev/sdk/v3";
+
+export const batchProcessingTask = task({
+  id: "batch-processing",
+  run: async (payload: { records: any[] }) => {
+    for (let i = 0; i < payload.records.length; i++) {
+      const record = payload.records[i];
+
+      // Update progress
+      metadata.set("progress", {
+        step: i + 1,
+        total: payload.records.length,
+        percentage: Math.round(((i + 1) / payload.records.length) * 100),
+        currentRecord: record.id,
+      });
+
+      await processRecord(record);
+    }
+  },
+});
+```
+
+### Status updates with logs
+
+Append log entries while maintaining status:
+
+```ts
+import { task, metadata } from "@trigger.dev/sdk/v3";
+
+export const deploymentTask = task({
+  id: "deployment",
+  run: async (payload: { version: string }) => {
+    metadata.set("status", "initializing");
+    metadata.append("logs", "Starting deployment...");
+
+    // Step 1
+    metadata.set("status", "building");
+    metadata.append("logs", "Building application...");
+    await buildApplication();
+
+    // Step 2
+    metadata.set("status", "deploying");
+    metadata.append("logs", "Deploying to production...");
+    await deployToProduction();
+
+    // Step 3
+    metadata.set("status", "verifying");
+    metadata.append("logs", "Running health checks...");
+    await runHealthChecks();
+
+    metadata.set("status", "completed");
+    metadata.append("logs", "Deployment successful!");
+  },
+});
+```
+
+### User context and notifications
+
+Store user information and notification preferences:
+
+```ts
+import { task, metadata } from "@trigger.dev/sdk/v3";
+
+export const userTask = task({
+  id: "user-task",
+  run: async (payload: { userId: string; action: string }) => {
+    // Set user context in metadata
+    metadata.set("user", {
+      id: payload.userId,
+      action: payload.action,
+      startedAt: new Date().toISOString(),
+    });
+
+    // Update status for user notifications
+    metadata.set("notification", {
+      type: "info",
+      message: `Starting ${payload.action} for user ${payload.userId}`,
+    });
+
+    await performUserAction(payload);
+
+    metadata.set("notification", {
+      type: "success",
+      message: `${payload.action} completed successfully`,
+    });
+  },
+});
+```
+
 ## Metadata propagation
 
 Metadata is NOT propagated to child tasks. If you want to pass metadata to a child task, you must do so explicitly: