feat: Complete Next.js Vercel cron integration and simplify docs

- Add Next.js Vercel automatic integration page
- Create comprehensive Next.js crons main page with proper navigation
- Simplify Vercel integration content to be concise and actionable
- Update platform checklist to reflect Next.js completion
- Revert Nuxt changes (missing sub-pages, moved back to pending)
- Remove Nuxt from supported platforms in common JS crons

Next.js now has complete cron monitoring documentation including:
- Main crons page with all setup methods
- Dedicated Vercel automatic integration page
- Proper cross-references and navigation structure

Author: smeubank

.cursor/project/features/005-unified-cron-monitoring-experience/PLATFORM-CRON-DOCS-CHECKLIST.md

@@ -9,24 +9,22 @@ This checklist guides the application of our proven cron documentation improveme
 
 ## 🎯 Platforms to Update
 
-### ✅ Completed Platforms
-- [x] **JavaScript Frameworks** - ✅ **Phase 1 Complete**
-  - [x] Next.js ⭐ *Special: Needs Vercel automatic integration page*
+### ✅ Completed Platforms (Phase 1)
+- [x] **JavaScript** - ✅ **Phase 1 Complete**
+  - [x] Node.js (base)
+  - [x] Next.js ✅ **Vercel Auto Integration Page Created**
   - [x] SvelteKit  
   - [x] Remix
   - [x] NestJS
-  - [x] Node.js (base patterns established)
 
-### 🔄 Pending JavaScript Platforms
-- [ ] **Node.js Additional Frameworks**
-  - [ ] Koa
-  - [ ] Hapi
-  - [ ] Express (basic patterns may exist, needs review)
-- [ ] **JavaScript Runtimes**
-  - [ ] Deno
-  - [ ] Bun
+### 🔄 Pending Platforms
 
-### 🔄 Pending SDK Platforms
+#### JavaScript Frameworks (Remaining)
+- [ ] **Nuxt**
+- [ ] **Koa**
+- [ ] **Hapi**
+- [ ] **Deno**
+- [ ] **Bun**
 
 #### High-Priority SDK Platforms
 - [ ] **Python** 
@@ -174,6 +172,20 @@ Brief intro to cron monitoring for {platform}.
 
 ## 🔧 Platform-Specific Considerations
 
+### ✅ Next.js Special Requirements - COMPLETED
+**Status:** ✅ All Next.js requirements completed
+
+**Completed Actions:**
+- ✅ **Created Vercel Automatic Integration Page** - `docs/platforms/javascript/guides/nextjs/crons/vercel-automatic.mdx`
+- ✅ **Created Main Next.js Crons Page** - `docs/platforms/javascript/guides/nextjs/crons/index.mdx`  
+- ✅ **Content includes:**
+  - Automatic Check-Ins (Vercel Only) configuration
+  - `automaticVercelMonitors: true` setup in `next.config.js`
+  - Pages Router vs App Router support clarification
+  - `vercel.json` crons field integration
+  - Next.js-specific API route examples
+  - Proper navigation and cross-references
+
 ### High Auto-Instrumentation Platforms
 **Platforms:** Node.js, Python
 - [ ] Emphasize automatic integration as preferred method
@@ -192,55 +204,6 @@ Brief intro to cron monitoring for {platform}.
 - [ ] Focus on the available functionality
 - [ ] Clear setup instructions specific to CLI/HTTP approach
 
-### ⭐ Next.js Special Requirements - Vercel Integration
-
-**Platforms:** Next.js specifically
-- [ ] **Create dedicated Vercel integration page** - `automatic-vercel.mdx`
-- [ ] **Link only from Next.js crons main page** - Not shown for other JavaScript frameworks
-- [ ] **Content source combination:**
-  - [Automatic Check-Ins (Vercel Only)](https://docs.sentry.io/platforms/javascript/guides/nextjs/crons/#automatic-check-ins-vercel-only)
-  - [Instrument Vercel Cron Jobs](https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/#step-6-instrument-vercel-cron-jobs-optional)
-
-**Required Content Structure:**
-```markdown
-# Automatic Vercel Integration
-
-Automatic cron monitoring for Next.js applications deployed on Vercel.
-
-## Prerequisites
-- Next.js application hosted on Vercel
-- Vercel Cron Jobs configured in vercel.json
-- Pages Router (App Router not yet supported)
-
-## Configuration
-
-Add to your next.config.js:
-
-```javascript
-module.exports = withSentryConfig(nextConfig, {
-  automaticVercelMonitors: true,
-});
-```
-
-## How It Works
-- Instrumented cron jobs decided at runtime by examining crons field in vercel.json
-- Automatically creates Check-Ins in Sentry
-- Currently supports Pages Router only
-
-## Limitations
-- Vercel hosting required
-- Pages Router only (App Router route handlers not yet supported)
-- Requires vercel.json cron configuration
-```
-
-**Implementation Checklist:**
-- [ ] Create `docs/platforms/javascript/guides/nextjs/crons/automatic-vercel.mdx`
-- [ ] Add link from main Next.js crons page only
-- [ ] Include clear prerequisites and limitations
-- [ ] Working code example with next.config.js
-- [ ] Link to Vercel cron jobs documentation
-- [ ] Note about Pages Router vs App Router support
-
 ## 📊 Quality Assurance Checklist
 
 ### Content Quality
@@ -325,24 +288,21 @@ module.exports = withSentryConfig(nextConfig, {
 
 ## 🔄 Platform Rollout Schedule
 
-### JavaScript Platform Completion (Q1)
-1. **Next.js Vercel Integration** - Create automatic-vercel.mdx page
-2. **Node.js Frameworks** - Koa, Hapi, Express (review needed)
-3. **JavaScript Runtimes** - Deno, Bun
-
 ### Immediate Priority (Q1)
-4. **Python** - High usage, good auto-instrumentation support
-5. **PHP** - High usage, Laravel integration important
-6. **Java** - Enterprise focus, Spring Boot integration
+1. ✅ **Next.js Vercel Integration** - Completed 
+2. **JavaScript Frameworks** - Apply patterns to Nuxt, Koa, Hapi, Deno, Bun
+3. **Python** - High usage, good auto-instrumentation support
+4. **PHP** - High usage, Laravel integration important  
+5. **Java** - Enterprise focus, Spring Boot integration
 
 ### Secondary Priority (Q2)  
-7. **Go** - Growing adoption, manual methods focus
-8. **Ruby** - Established user base
-9. **Elixir** - Smaller but dedicated user base
+6. **Go** - Growing adoption, manual methods focus
+7. **Ruby** - Established user base
+8. **Elixir** - Smaller but dedicated user base
 
 ### Final Priority (Q3)
-10. **HTTP Documentation** - Language-agnostic approach
-11. **CLI Documentation** - Developer tooling focus
+7. **HTTP Documentation** - Language-agnostic approach
+8. **CLI Documentation** - Developer tooling focus
 
 ## 📝 PR Template for Each Platform
 

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

@@ -0,0 +1,107 @@
+---
+title: Set Up Crons
+sidebar_title: Crons
+description: "Monitor your scheduled jobs with Sentry in Next.js applications."
+sidebar_order: 5750
+supported:
+  - javascript.nextjs
+---
+
+Monitor the uptime and performance of your scheduled jobs in Next.js. Get alerts when jobs fail, timeout, or don't run as expected.
+
+## Setup Methods
+
+Choose the method that matches your current setup:
+
+* [UI Setup](/platforms/javascript/common/crons/ui-setup) - Create monitors in Sentry's web interface, then add instrumentation
+
+### Automatic Integration
+
+* [Vercel Automatic Integration](vercel-automatic) - Auto-instrument Vercel Cron Jobs (Pages Router only)
+* [node-cron](/platforms/javascript/common/crons/node-cron) - Auto-instrument node-cron library
+* [cron](/platforms/javascript/common/crons/cron-library) - Auto-instrument cron library  
+* [node-schedule](/platforms/javascript/common/crons/node-schedule) - Auto-instrument node-schedule library
+
+If you're using one of these popular cron libraries, use the automatic integration for seamless monitoring.
+
+#### Manual Methods
+
+* [Job Monitoring](/platforms/javascript/common/crons/job-monitoring) - Use withMonitor wrapper for automatic status tracking
+* [Check-Ins](/platforms/javascript/common/crons/check-ins) - Full control with manual status updates
+* [Heartbeat](/platforms/javascript/common/crons/heartbeat) - Simple success/failure notifications
+* [Upserting Monitors](/platforms/javascript/common/crons/upserting-monitors) - Programmatic monitor creation and management
+
+### Alternative Methods (Not Recommended)
+
+These methods work but don't provide the full benefits of SDK integration like tracing and error context:
+
+* [Sentry CLI](https://docs.sentry.io/cli/crons/) - Command-line tool for basic monitoring
+* [HTTP API](https://docs.sentry.io/product/crons/getting-started/http/) - Direct API calls for check-ins
+
+## Next.js-Specific Considerations
+
+### Server and Edge Runtimes
+
+Cron monitoring is only supported in **Server and Edge runtimes** for Next.js. Client-side monitoring is not available.
+
+### App Router vs Pages Router
+
+- **Vercel Automatic Integration**: Only works with Pages Router
+- **All other methods**: Work with both App Router and Pages Router
+
+### API Routes Example
+
+For App Router route handlers:
+
+```typescript {filename:app/api/cron/route.ts}
+import * as Sentry from '@sentry/nextjs';
+
+export async function GET() {
+  return Sentry.withMonitor('daily-report', async () => {
+    // Your cron job logic here
+    await generateDailyReport();
+    return new Response('Report generated', { status: 200 });
+  });
+}
+```
+
+For Pages Router API routes:
+
+```typescript {filename:pages/api/cron.ts}
+import * as Sentry from '@sentry/nextjs';
+import type { NextApiRequest, NextApiResponse } from 'next';
+
+export default async function handler(req: NextApiRequest, res: NextApiResponse) {
+  return Sentry.withMonitor('daily-report', async () => {
+    // Your cron job logic here
+    await generateDailyReport();
+    res.status(200).json({ message: 'Report generated' });
+  });
+}
+```
+
+## Alerts
+
+When your recurring job fails to check in (missed), runs beyond its configured maximum runtime (failed), or manually reports a failure, Sentry will create an error event with a tag to your monitor.
+
+To receive alerts about these events:
+
+1. Navigate to **Alerts** in the sidebar.
+2. Create a new alert and select "Issues" under "Errors" as the alert type.
+3. Configure your alert and define a filter match to use: `The event's tags match {key} {match} {value}`.
+
+Example: `The event's tags match monitor.slug equals my-monitor-slug-here`
+
+Learn more in [Issue Alert Configuration](/product/alerts/alert-types/#issue-alerts).
+
+## Rate Limits
+
+Crons imposes a rate limit on check-ins to prevent abuse and resource overuse. Specifically, you can only send a maximum of **6 check-ins per minute per existing monitor environment**. This limit is enforced on a per-project basis, meaning that the rate limit applies collectively to all monitor environments within a given project. You can check if any of your check-ins are being dropped in the [Usage Stats](/product/stats/) page.
+
+To avoid dropped check-ins, it is crucial to manage and distribute your check-ins efficiently within the rate limits. This will help maintain accurate monitoring and ensure that all critical check-ins are captured and processed.
+
+## Additional Resources
+
+* [Troubleshooting Cron Monitoring](/platforms/javascript/common/crons/troubleshooting)
+* [Cron Monitoring Best Practices](https://blog.sentry.io/cron-monitoring-best-practices)
+* [Debugging Failed Cron Jobs](https://blog.sentry.io/debugging-cron-jobs) 

docs/platforms/javascript/guides/nextjs/crons/vercel-automatic.mdx

@@ -0,0 +1,57 @@
+---
+title: "Vercel Automatic Integration"
+description: "Auto-instrument Vercel Cron Jobs in Next.js applications."
+sidebar_order: 5
+supported:
+  - javascript.nextjs
+---
+
+Monitor Vercel Cron Jobs automatically with minimal configuration.
+
+## Setup
+
+### 1. Enable Automatic Monitoring
+
+Update your `next.config.js`:
+
+```javascript {filename:next.config.js}
+module.exports = withSentryConfig(nextConfig, {
+  automaticVercelMonitors: true,
+});
+```
+
+### 2. Configure Vercel Cron Jobs
+
+Add cron jobs to your `vercel.json`:
+
+```json {filename:vercel.json}
+{
+  "crons": [
+    {
+      "path": "/api/cron/daily-report",
+      "schedule": "0 9 * * *"
+    }
+  ]
+}
+```
+
+That's it! Monitors are automatically created when your cron jobs run.
+
+## Limitations
+
+- **Pages Router only** - App Router support coming soon
+- **Vercel hosting required** - Use [manual methods](../index.mdx) for other hosts
+
+## Troubleshooting
+
+**Monitors not created?** 
+- Verify `automaticVercelMonitors: true` in config
+- Check `vercel.json` has valid `crons` field
+- Ensure using Pages Router
+
+**Check-ins missing?**
+- Confirm deployed to Vercel
+- Check deployment logs for errors
+- Verify cron path matches API route
+
+For other setup methods, see the [main guide](../index.mdx). 

platform-includes/crons/setup/javascript.nuxt.mdx

@@ -0,0 +1,17 @@
+Cron monitoring is only supported in Nuxt.js server-side
+
+## Automatic Crons Instrumentation
+
+<Include name="javascript-crons-automatic-crons-instrumentation.mdx" />
+
+## Job Monitoring
+
+<Include name="javascript-crons-job-monitoring.mdx" />
+
+## Check-Ins
+
+<Include name="javascript-crons-checkins.mdx" />
+
+## Upserting Cron Monitors
+
+<Include name="javascript-crons-upsert.mdx" />