Added additional resources links to nextjs and remix

Author: D-K-P

docs/guides/frameworks/nextjs.mdx

@@ -244,14 +244,24 @@ Here are the steps to trigger your task in the Next.js App and Pages router and
 
 </Tabs>
 
-<AddEnvironmentVariables/>
+<AddEnvironmentVariables />
 
-<DeployingYourTask/>
+<DeployingYourTask />
 
 ## Troubleshooting
 
     <NextjsTroubleshootingMissingApiKey/>
     <NextjsTroubleshootingButtonSyntax/>
     <WorkerFailedToStartWhenRunningDevCommand/>
 
+## Additional resources for Next.js
+
+<Card
+  title="Next.js - triggering tasks using webhooks"
+  icon="N"
+  href="/guides/frameworks/nextjs-webhooks"
+>
+  How to create a webhook handler in a Next.js app, and trigger a task from it.
+</Card>
+
 <UsefulNextSteps />

docs/guides/frameworks/remix.mdx

@@ -5,12 +5,12 @@ description: "This guide will show you how to setup Trigger.dev in your existing
 icon: "r"
 ---
 
-import Prerequisites from '/snippets/framework-prerequisites.mdx';
-import CliInitStep from '/snippets/step-cli-init.mdx';
-import CliDevStep from '/snippets/step-cli-dev.mdx';
-import CliRunTestStep from '/snippets/step-run-test.mdx';
-import CliViewRunStep from '/snippets/step-view-run.mdx';
-import UsefulNextSteps from '/snippets/useful-next-steps.mdx';
+import Prerequisites from "/snippets/framework-prerequisites.mdx";
+import CliInitStep from "/snippets/step-cli-init.mdx";
+import CliDevStep from "/snippets/step-cli-dev.mdx";
+import CliRunTestStep from "/snippets/step-run-test.mdx";
+import CliViewRunStep from "/snippets/step-view-run.mdx";
+import UsefulNextSteps from "/snippets/useful-next-steps.mdx";
 import TriggerTaskRemix from "/snippets/trigger-tasks-remix.mdx";
 import AddEnvironmentVariables from "/snippets/add-environment-variables.mdx";
 import DeployingYourTask from "/snippets/deplopying-your-task.mdx";
@@ -20,10 +20,10 @@ import DeployingYourTask from "/snippets/deplopying-your-task.mdx";
 ## Initial setup
 
 <Steps>
-    <CliInitStep />
-    <CliDevStep />
-    <CliRunTestStep />
-    <CliViewRunStep />
+  <CliInitStep />
+  <CliDevStep />
+  <CliRunTestStep />
+  <CliViewRunStep />
 </Steps>
 
 ## Set your secret key locally
@@ -40,27 +40,24 @@ For more information on authenticating with Trigger.dev, see the [API keys page]
 
   <Step title="Create an API route">
 
-  Create a new file called `api.hello-world.ts` (or `api.hello-world.js`) in the `app/routes` directory like this: `app/routes/api.hello-world.ts`.
+Create a new file called `api.hello-world.ts` (or `api.hello-world.js`) in the `app/routes` directory like this: `app/routes/api.hello-world.ts`.
 
   </Step>
 
   <Step title="Add your task">
 
-  Add this code to your `api.hello-world.ts` file which imports your task:
+Add this code to your `api.hello-world.ts` file which imports your task:
 
-  ```ts app/routes/api.hello-world.ts
-  import type { helloWorldTask } from "../../src/trigger/example";
-  import { tasks } from "@trigger.dev/sdk/v3";
+```ts app/routes/api.hello-world.ts
+import type { helloWorldTask } from "../../src/trigger/example";
+import { tasks } from "@trigger.dev/sdk/v3";
 
-  export async function loader() {
-    const handle = await tasks.trigger<typeof helloWorldTask>(
-      "hello-world",
-      "James"
-    );
+export async function loader() {
+  const handle = await tasks.trigger<typeof helloWorldTask>("hello-world", "James");
 
-    return new Response(JSON.stringify(handle), {
-      headers: { "Content-Type": "application/json" },
-    });
+  return new Response(JSON.stringify(handle), {
+    headers: { "Content-Type": "application/json" },
+  });
 }
 ```
 
@@ -74,13 +71,14 @@ For more information on authenticating with Trigger.dev, see the [API keys page]
 
 </Steps>
 
-<AddEnvironmentVariables/>
+<AddEnvironmentVariables />
 
-<DeployingYourTask/>
+<DeployingYourTask />
 
 ## Deploying to Vercel Edge Functions
 
 Before we start, it's important to note that:
+
 - We'll be using a type-only import for the task to ensure compatibility with the edge runtime.
 - The `@trigger.dev/sdk/v3` package supports the edge runtime out of the box.
 
@@ -104,10 +102,7 @@ export const config = {
 export async function action({ request }: { request: Request }) {
   // This is where you'd authenticate the request
   const payload = await request.json();
-  const handle = await tasks.trigger<typeof helloWorldTask>(
-    "hello-world",
-    payload
-  );
+  const handle = await tasks.trigger<typeof helloWorldTask>("hello-world", payload);
   return new Response(JSON.stringify(handle), {
     headers: { "Content-Type": "application/json" },
   });
@@ -155,7 +150,6 @@ Push your code to a Git repository and create a new project in the Vercel dashbo
 
 </Step>
 
-
 <Step title="Add your Vercel environment variables">
 
 In the Vercel project settings, add your Trigger.dev secret key:
@@ -174,7 +168,10 @@ You can find this key in the Trigger.dev dashboard under API Keys and select the
 
 Once you've added the environment variable, deploy your project to Vercel.
 
-<Note>Ensure you have also deployed your Trigger.dev task. See [deploy your task step](/guides/frameworks/remix#deploying-your-task-to-trigger-dev).</Note>
+<Note>
+  Ensure you have also deployed your Trigger.dev task. See [deploy your task
+  step](/guides/frameworks/remix#deploying-your-task-to-trigger-dev).
+</Note>
 
 </Step>
 
@@ -200,5 +197,14 @@ The `vercel-build` script in `package.json` is specific to Remix projects on Ver
 
 The `runtime: "edge"` configuration in the API route allows for better performance on Vercel's Edge Network.
 
+## Additional resources for Remix
+
+<Card
+  title="Remix - triggering tasks using webhooks"
+  icon="R"
+  href="/guides/frameworks/remix-webhooks"
+>
+  How to create a webhook handler in a Remix app, and trigger a task from it.
+</Card>
 
 <UsefulNextSteps />