docs: add Recipes section with 5 real-world workflow guides#1116
docs: add Recipes section with 5 real-world workflow guides#1116johnlindquist wants to merge 4 commits intomainfrom
Conversation
Adds a new Recipes documentation section with production-ready patterns for common workflow use cases, driven by usage data analysis: - Data Synchronization (100 teams, 369K runs) - Webhook Integrations (40 teams, 516K runs) - Data Ingestion & File Processing (23 teams, 1.1M runs) - Notifications & Email (58 teams, 288K runs) - Error Monitoring & Alerting (19 teams, 4.7M runs)
|
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests▲ Vercel Production (3 failed)astro (1 failed):
nextjs-turbopack (1 failed):
nitro (1 failed):
🌍 Community Worlds (45 failed)turso (45 failed):
Details by Category❌ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
❌ 🌍 Community Worlds
✅ 📋 Other
❌ Some E2E test jobs failed:
Check the workflow run for details. |
📊 Benchmark Results
workflow with no steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) workflow with 1 step💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express workflow with 10 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) workflow with 25 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) workflow with 50 sequential steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) Promise.all with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express Promise.all with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express Promise.all with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express Promise.race with 10 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express Promise.race with 25 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express Promise.race with 50 concurrent steps💻 Local Development
▲ Production (Vercel)
🔍 Observability: Express | Next.js (Turbopack) Stream Benchmarks (includes TTFB metrics)workflow with stream💻 Local Development
▲ Production (Vercel)
🔍 Observability: Next.js (Turbopack) | Express SummaryFastest Framework by WorldWinner determined by most benchmark wins
Fastest World by FrameworkWinner determined by most benchmark wins
Column Definitions
Worlds:
❌ Some benchmark jobs failed:
Check the workflow run for details. |
Replace verbose polling/scheduling examples in error-monitoring and webhook-integrations recipes with shorter inline snippets that link to the canonical Scheduling & Cron foundations guide for depth.
- data-ingestion: use for-await over single webhook instead of creating webhook inside loop; remove unused getWritable import - webhook-integrations: move process.env into step function; use FatalError for invalid signatures; sanitize repo name slashes in tokens - error-monitoring: add retry loop for hook delivery race condition after start(); add callout explaining the race - notifications-email: rename FormData interface to ContactSubmission to avoid collision with Web API FormData - data-sync: fix Contact.updatedAt type from Date to string (JSON responses don't auto-parse dates)
Summary
Adds a new Recipes documentation section with production-ready patterns for common workflow use cases. Each recipe was motivated by usage data analysis across 10 workflow categories.
New docs
Structure
docs/content/docs/recipes/index.mdx— section overview with Cardsdocs/content/docs/recipes/meta.json— navigation configmeta.jsonto include Recipes after AI AgentsTest plan