feat: add vercel specific microfrontends guide

Author: logaretm

docs/platforms/javascript/guides/nextjs/best-practices/micro-frontends.mdx

@@ -0,0 +1,39 @@
+---
+title: Micro Frontends
+description: "Learn how to add Sentry instrumentation to your Vercel's micro frontend projects."
+---
+
+<PlatformContent includePath="getting-started-prerequisites" />
+
+You also need a [micro frontends project](https://vercel.com/docs/microfrontends) deployed to Vercel.
+
+## Overview
+
+There are many ways to use micro frontends. You can split your application into smaller projects, each managed by a different team. Each micro frontend project can be either a separate application with its own tech stack and UI, or it can contribute a piece of functionality or content to a host application.
+
+- **Multi-zone applications**: Multiple independent projects, where each is its own application with its own UI and tech stack.
+- **Module Federation**: A host application that pulls in other applications as dependencies or shares components and functionality with other applications.
+
+## Multi-zone Applications
+
+Multi-zone applications allow you to slice a large application into smaller, more manageable projects. Each project is its own application with its own UI and tech stack. For example, you could use Next.js for one project, SvelteKit for another, and React for a third.
+
+To set up Sentry for a multi-zone application, set up Sentry for each project individually by following the installation instructions for each framework:
+
+- **[Next.js](/platforms/javascript/guides/nextjs/)**
+- **[React Router](/platforms/javascript/guides/react/)**
+- **[SvelteKit](/platforms/javascript/guides/sveltekit/)**
+
+<Alert title="Tip">
+  We recommend using a different DSN for each project. This makes it easier to
+  identify which project errors are coming from, helping you track issues and
+  fix them faster in complex frontend architectures.
+</Alert>
+
+## Module Federation
+
+For micro frontends using module federation (where a host application pulls in other applications as dependencies), see the [JavaScript Micro Frontends documentation](/platforms/javascript/best-practices/micro-frontends/), which covers:
+
+- Automatically routing errors to different projects using `ModuleMetadata` and `makeMultiplexedTransport`
+- Manually routing errors to different projects
+- SDK version alignment across micro frontends

docs/platforms/javascript/guides/nextjs/index.mdx

@@ -180,6 +180,7 @@ Our next recommended steps for you are:
 - Learn how to [manually capture errors](/platforms/javascript/guides/nextjs/usage/)
 - Continue to [customize your configuration](/platforms/javascript/guides/nextjs/configuration/)
 - Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts
+- Learn how to [set up Sentry for Vercel's microfrontends](/platforms/javascript/guides/nextjs/best-practices/micro-frontends/)
 - Learn more about our [Vercel integration](/organization/integrations/deployment/vercel/)
 
 <Expandable permalink={false} title="Are you having problems setting up the SDK?">