Skip to content

Conversation

@pranaygp
Copy link
Collaborator

@pranaygp pranaygp commented Feb 6, 2026

Summary

  • Ports the customer logo wall (Mux, Whop, Neon) from vercel.com/workflow to the useworkflow.dev homepage
  • Ports the builder testimonial tweet wall (5 tweets) from vercel.com/workflow to the useworkflow.dev homepage
  • Logos use currentColor SVGs for automatic light/dark mode support
  • Tweet wall uses the docs site's existing shadcn Avatar and Card styling

Test plan

  • Verify logos render correctly in both light and dark mode
  • Verify tweet wall renders in responsive masonry layout (1/2/3 columns)
  • Verify tweet cards link to the correct X/Twitter URLs
  • Check avatar images load from blob storage

🤖 Generated with Claude Code

Port the customer logo wall (Mux, Whop, Neon) and builder testimonial
tweet wall from vercel.com/workflow to the docs site homepage.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings February 6, 2026 23:40
@changeset-bot
Copy link

changeset-bot bot commented Feb 6, 2026

⚠️ No Changeset found

Latest commit: 84f73e1

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link
Contributor

vercel bot commented Feb 6, 2026

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

📊 Benchmark Results

📈 Comparing against baseline from main branch. Green 🟢 = faster, Red 🔺 = slower.

workflow with no steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.038s (-0.5%) 1.017s (~) 0.978s 10 1.00x
💻 Local Express 0.043s (-1.4%) 1.008s (~) 0.966s 10 1.11x
💻 Local Nitro 0.043s (-1.1%) 1.007s (~) 0.964s 10 1.13x
🐘 Postgres Nitro 0.170s (-21.6% 🟢) 1.017s (~) 0.847s 10 4.44x
🐘 Postgres Express 0.268s (+44.9% 🔺) 1.019s (~) 0.751s 10 7.02x
🐘 Postgres Next.js (Turbopack) 0.388s (-8.6% 🟢) 1.022s (~) 0.635s 10 10.14x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 0.560s (-24.8% 🟢) 1.573s (-2.4%) 1.013s 10 1.00x
▲ Vercel Nitro 0.590s (-10.1% 🟢) 1.600s (~) 1.010s 10 1.05x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - -

🔍 Observability: Express | Nitro

workflow with 1 step

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.095s (~) 2.013s (~) 0.919s 10 1.00x
💻 Local Nitro 1.115s (~) 2.007s (~) 0.893s 10 1.02x
💻 Local Express 1.120s (~) 2.008s (~) 0.888s 10 1.02x
🐘 Postgres Next.js (Turbopack) 2.209s (-2.2%) 3.022s (~) 0.812s 10 2.02x
🐘 Postgres Express 2.229s (-7.2% 🟢) 3.016s (~) 0.787s 10 2.04x
🐘 Postgres Nitro 2.441s (+10.1% 🔺) 3.013s (~) 0.572s 10 2.23x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.373s (-6.8% 🟢) 3.176s (-14.8% 🟢) 0.803s 10 1.00x
▲ Vercel Express 2.428s (-3.5%) 3.313s (-11.4% 🟢) 0.884s 10 1.02x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - -

🔍 Observability: Nitro | Express

workflow with 10 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 10.744s (~) 11.026s (~) 0.282s 3 1.00x
💻 Local Express 10.833s (~) 11.017s (~) 0.184s 3 1.01x
💻 Local Nitro 10.834s (~) 11.014s (~) 0.180s 3 1.01x
🐘 Postgres Next.js (Turbopack) 15.359s (-23.7% 🟢) 16.035s (-23.8% 🟢) 0.676s 2 1.43x
🐘 Postgres Nitro 20.399s (+31.7% 🔺) 21.030s (+31.2% 🔺) 0.631s 2 1.90x
🐘 Postgres Express 20.466s (~) 21.032s (~) 0.566s 2 1.90x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 19.541s (-2.9%) 20.220s (-3.1%) 0.679s 2 1.00x
▲ Vercel Express 19.805s (-1.0%) 20.594s (-1.3%) 0.789s 2 1.01x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - -

🔍 Observability: Nitro | Express

workflow with 25 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 27.214s (~) 28.042s (~) 0.828s 3 1.00x
💻 Local Nitro 27.478s (~) 28.024s (~) 0.546s 3 1.01x
💻 Local Express 27.506s (~) 28.023s (~) 0.517s 3 1.01x
🐘 Postgres Next.js (Turbopack) 37.755s (-25.0% 🟢) 38.059s (-25.5% 🟢) 0.304s 2 1.39x
🐘 Postgres Nitro 50.278s (+30.6% 🔺) 51.073s (+30.8% 🔺) 0.795s 2 1.85x
🐘 Postgres Express 50.343s (~) 51.079s (~) 0.737s 2 1.85x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 49.170s (-2.4%) 49.979s (-2.2%) 0.809s 2 1.00x
▲ Vercel Nitro 50.120s (+0.5%) 36.021s (-29.1% 🟢) -14.100s 3 1.02x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - -

🔍 Observability: Express | Nitro

workflow with 50 sequential steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 56.620s (~) 57.051s (~) 0.431s 2 1.00x
💻 Local Nitro 57.184s (~) 58.038s (~) 0.854s 2 1.01x
💻 Local Express 57.276s (~) 58.048s (~) 0.772s 2 1.01x
🐘 Postgres Next.js (Turbopack) 74.927s (-25.5% 🟢) 75.132s (-25.7% 🟢) 0.205s 2 1.32x
🐘 Postgres Nitro 97.559s (+27.8% 🔺) 98.095s (+27.2% 🔺) 0.536s 1 1.72x
🐘 Postgres Express 100.131s (~) 101.116s (~) 0.985s 1 1.77x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 105.634s (-0.5%) 106.752s (-5.1% 🟢) 1.118s 1 1.00x
▲ Vercel Nitro 108.207s (+1.1%) 109.504s (+1.3%) 1.297s 1 1.02x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - -

🔍 Observability: Express | Nitro

Promise.all with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 1.407s (~) 2.008s (~) 0.601s 15 1.00x
💻 Local Nitro 1.418s (+1.2%) 2.006s (~) 0.588s 15 1.01x
💻 Local Next.js (Turbopack) 1.418s (+2.3%) 2.013s (~) 0.594s 15 1.01x
🐘 Postgres Nitro 1.913s (-15.2% 🟢) 2.318s (-15.7% 🟢) 0.405s 13 1.36x
🐘 Postgres Next.js (Turbopack) 2.062s (-3.7%) 2.322s (-18.1% 🟢) 0.260s 13 1.47x
🐘 Postgres Express 2.278s (~) 3.014s (~) 0.736s 10 1.62x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 8.748s (+235.0% 🔺) 10.014s (+173.1% 🔺) 1.266s 3 1.00x
▲ Vercel Express 16.570s (+477.9% 🔺) 17.798s (+368.4% 🔺) 1.229s 2 1.89x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - -

🔍 Observability: Nitro | Express

Promise.all with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 2.587s (+4.8%) 3.103s (+2.7%) 0.516s 10 1.00x
💻 Local Express 2.628s (+1.2%) 3.010s (~) 0.382s 10 1.02x
💻 Local Nitro 2.632s (+1.5%) 3.017s (~) 0.384s 10 1.02x
🐘 Postgres Nitro 8.362s (-24.4% 🟢) 8.798s (-24.7% 🟢) 0.436s 4 3.23x
🐘 Postgres Express 8.549s (-6.0% 🟢) 9.077s (-5.2% 🟢) 0.528s 4 3.30x
🐘 Postgres Next.js (Turbopack) 12.153s (-4.2%) 12.442s (-7.2% 🟢) 0.289s 3 4.70x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.869s (-25.6% 🟢) 3.983s (-14.4% 🟢) 1.113s 8 1.00x
▲ Vercel Nitro 2.881s (-9.1% 🟢) 3.721s (-6.4% 🟢) 0.840s 9 1.00x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - -

🔍 Observability: Express | Nitro

Promise.all with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 7.426s (+2.0%) 8.423s (+1.7%) 0.997s 4 1.00x
💻 Local Nitro 7.486s (+4.1%) 8.485s (+4.1%) 0.999s 4 1.01x
💻 Local Next.js (Turbopack) 7.602s (+6.6% 🔺) 8.606s (+10.6% 🔺) 1.004s 4 1.02x
🐘 Postgres Nitro 48.631s (-6.8% 🟢) 49.172s (-7.4% 🟢) 0.541s 1 6.55x
🐘 Postgres Express 49.596s (+1.5%) 50.350s (+2.2%) 0.754s 1 6.68x
🐘 Postgres Next.js (Turbopack) 52.981s (-5.7% 🟢) 53.217s (-6.9% 🟢) 0.236s 1 7.13x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 3.689s (-67.4% 🟢) 4.611s (-62.7% 🟢) 0.922s 7 1.00x
▲ Vercel Nitro 4.196s (-71.5% 🟢) 5.211s (-67.0% 🟢) 1.015s 7 1.14x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - -

🔍 Observability: Express | Nitro

Promise.race with 10 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 1.440s (+3.3%) 2.010s (~) 0.570s 15 1.00x
💻 Local Express 1.452s (+1.3%) 2.007s (~) 0.555s 15 1.01x
💻 Local Nitro 1.456s (+2.7%) 2.006s (~) 0.551s 15 1.01x
🐘 Postgres Nitro 1.861s (-16.7% 🟢) 2.230s (-14.0% 🟢) 0.370s 14 1.29x
🐘 Postgres Express 2.247s (+9.5% 🔺) 2.602s (+12.1% 🔺) 0.355s 12 1.56x
🐘 Postgres Next.js (Turbopack) 2.281s (-1.8%) 2.691s (-1.7%) 0.410s 12 1.58x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 3.356s (+32.4% 🔺) 4.585s (+28.9% 🔺) 1.230s 7 1.00x
▲ Vercel Express 11.967s (+282.1% 🔺) 12.878s (+204.6% 🔺) 0.911s 5 3.57x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - -

🔍 Observability: Nitro | Express

Promise.race with 25 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Nitro 2.694s (~) 3.020s (~) 0.325s 10 1.00x
💻 Local Next.js (Turbopack) 2.701s (+2.6%) 3.025s (-4.9%) 0.324s 10 1.00x
💻 Local Express 2.732s (+1.0%) 3.024s (~) 0.291s 10 1.01x
🐘 Postgres Nitro 10.258s (-13.1% 🟢) 10.408s (-13.4% 🟢) 0.150s 3 3.81x
🐘 Postgres Express 10.730s (-2.6%) 11.020s (-3.0%) 0.289s 3 3.98x
🐘 Postgres Next.js (Turbopack) 13.234s (-3.3%) 13.696s (-4.7%) 0.462s 3 4.91x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 2.760s (-17.9% 🟢) 3.781s (-13.3% 🟢) 1.021s 8 1.00x
▲ Vercel Express 3.125s (+12.5% 🔺) 4.096s (+10.1% 🔺) 0.972s 8 1.13x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - -

🔍 Observability: Nitro | Express

Promise.race with 50 concurrent steps

💻 Local Development

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Express 7.933s (-2.9%) 8.615s (-5.2% 🟢) 0.681s 4 1.00x
💻 Local Nitro 8.170s (+3.2%) 9.142s (+2.5%) 0.972s 4 1.03x
💻 Local Next.js (Turbopack) 8.217s (+9.0% 🔺) 8.905s (+3.9%) 0.688s 4 1.04x
🐘 Postgres Nitro 52.608s (+1.0%) 53.136s (~) 0.528s 1 6.63x
🐘 Postgres Express 53.397s (+5.2% 🔺) 54.187s (+6.0% 🔺) 0.790s 1 6.73x
🐘 Postgres Next.js (Turbopack) 54.549s (-5.1% 🟢) 55.254s (-5.0% 🟢) 0.705s 1 6.88x

▲ Production (Vercel)

World Framework Workflow Time Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Nitro 6.923s (+11.8% 🔺) 7.691s (+12.8% 🔺) 0.768s 5 1.00x
▲ Vercel Express 7.560s (-3.4%) 8.329s (-2.5%) 0.769s 4 1.09x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - -

🔍 Observability: Nitro | Express

Stream Benchmarks (includes TTFB metrics)
workflow with stream

💻 Local Development

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
💻 Local 🥇 Next.js (Turbopack) 0.145s (+2.2%) 1.003s (~) 0.015s (+4.8%) 1.027s (~) 0.881s 10 1.00x
💻 Local Express 0.182s (+0.8%) 0.992s (~) 0.015s (+3.5%) 1.021s (~) 0.839s 10 1.25x
💻 Local Nitro 0.183s (+1.6%) 0.992s (~) 0.014s (+6.0% 🔺) 1.020s (~) 0.838s 10 1.25x
🐘 Postgres Next.js (Turbopack) 1.004s (-48.6% 🟢) 1.569s (-37.2% 🟢) 0.000s (-100.0% 🟢) 1.717s (-36.8% 🟢) 0.713s 10 6.90x
🐘 Postgres Nitro 1.356s (+7.4% 🔺) 1.736s (-2.4%) 0.000s (+Infinity% 🔺) 2.014s (~) 0.658s 10 9.32x
🐘 Postgres Express 2.366s (+0.9%) 2.678s (-0.6%) 0.000s (-100.0% 🟢) 3.016s (~) 0.650s 10 16.26x

▲ Production (Vercel)

World Framework Workflow Time TTFB Slurp Wall Time Overhead Samples vs Fastest
▲ Vercel 🥇 Express 2.590s (-58.5% 🟢) 3.057s (-48.3% 🟢) 0.146s (-7.6% 🟢) 3.740s (-49.1% 🟢) 1.149s 10 1.00x
▲ Vercel Nitro 2.808s (-51.3% 🟢) 2.935s (-52.0% 🟢) 0.184s (-23.2% 🟢) 3.845s (-46.2% 🟢) 1.037s 10 1.08x
▲ Vercel Next.js (Turbopack) ⚠️ missing - - - - -

🔍 Observability: Express | Nitro

Summary

Fastest Framework by World

Winner determined by most benchmark wins

World 🥇 Fastest Framework Wins
💻 Local Next.js (Turbopack) 8/12
🐘 Postgres Nitro 7/12
▲ Vercel Express 6/12
Fastest World by Framework

Winner determined by most benchmark wins

Framework 🥇 Fastest World Wins
Express 💻 Local 10/12
Next.js (Turbopack) 💻 Local 12/12
Nitro 💻 Local 10/12
Column Definitions
  • Workflow Time: Runtime reported by workflow (completedAt - createdAt) - primary metric
  • TTFB: Time to First Byte - time from workflow start until first stream byte received (stream benchmarks only)
  • Slurp: Time from first byte to complete stream consumption (stream benchmarks only)
  • Wall Time: Total testbench time (trigger workflow + poll for result)
  • Overhead: Testbench overhead (Wall Time - Workflow Time)
  • Samples: Number of benchmark iterations run
  • vs Fastest: How much slower compared to the fastest configuration for this benchmark

Worlds:

  • 💻 Local: In-memory filesystem world (local development)
  • 🐘 Postgres: PostgreSQL database world (local development)
  • ▲ Vercel: Vercel production/preview deployment
  • 🌐 Starter: Community world (local development)
  • 🌐 Turso: Community world (local development)
  • 🌐 MongoDB: Community world (local development)
  • 🌐 Redis: Community world (local development)
  • 🌐 Jazz: Community world (local development)

📋 View full workflow run


Some benchmark jobs failed:

  • Local: success
  • Postgres: success
  • Vercel: failure

Check the workflow run for details.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

🧪 E2E Test Results

Some tests failed

Summary

Passed Failed Skipped Total
❌ ▲ Vercel Production 474 5 38 517
✅ 💻 Local Development 438 0 32 470
✅ 📦 Local Production 438 0 32 470
✅ 🐘 Local Postgres 438 0 32 470
✅ 🪟 Windows 47 0 0 47
❌ 🌍 Community Worlds 31 169 0 200
✅ 📋 Other 129 0 12 141
Total 1995 174 146 2315

❌ Failed Tests

▲ Vercel Production (5 failed)

astro (1 failed):

  • Calculator.calculate - static workflow method using static step methods from another class

fastify (1 failed):

  • health check (CLI) - workflow health command reports healthy endpoints

nitro (1 failed):

  • health check (queue-based) - workflow and step endpoints respond to health check messages

nuxt (1 failed):

  • AllInOneService.processNumber - static workflow method using sibling static step methods

sveltekit (1 failed):

  • AllInOneService.processNumber - static workflow method using sibling static step methods
🌍 Community Worlds (169 failed)

mongodb (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

redis (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

starter (43 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • health check (CLI) - workflow health command reports healthy endpoints
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

turso (42 failed):

  • addTenWorkflow
  • addTenWorkflow
  • should work with react rendering in step
  • promiseAllWorkflow
  • promiseRaceWorkflow
  • promiseAnyWorkflow
  • readableStreamWorkflow
  • hookWorkflow
  • webhookWorkflow
  • sleepingWorkflow
  • nullByteWorkflow
  • workflowAndStepMetadataWorkflow
  • outputStreamWorkflow
  • outputStreamInsideStepWorkflow - getWritable() called inside step functions
  • fetchWorkflow
  • promiseRaceStressTestWorkflow
  • error handling error propagation workflow errors nested function calls preserve message and stack trace
  • error handling error propagation workflow errors cross-file imports preserve message and stack trace
  • error handling error propagation step errors basic step error preserves message and stack trace
  • error handling error propagation step errors cross-file step error preserves message and function names in stack
  • error handling retry behavior regular Error retries until success
  • error handling retry behavior FatalError fails immediately without retries
  • error handling retry behavior RetryableError respects custom retryAfter delay
  • error handling retry behavior maxRetries=0 disables retries
  • error handling catchability FatalError can be caught and detected with FatalError.is()
  • hookCleanupTestWorkflow - hook token reuse after workflow completion
  • concurrent hook token conflict - two workflows cannot use the same hook token simultaneously
  • stepFunctionPassingWorkflow - step function references can be passed as arguments (without closure vars)
  • stepFunctionWithClosureWorkflow - step function with closure variables passed as argument
  • closureVariableWorkflow - nested step functions with closure variables
  • spawnWorkflowFromStepWorkflow - spawning a child workflow using start() inside a step
  • pathsAliasWorkflow - TypeScript path aliases resolve correctly
  • Calculator.calculate - static workflow method using static step methods from another class
  • AllInOneService.processNumber - static workflow method using sibling static step methods
  • ChainableService.processWithThis - static step methods using this to reference the class
  • thisSerializationWorkflow - step function invoked with .call() and .apply()
  • customSerializationWorkflow - custom class serialization with WORKFLOW_SERIALIZE/WORKFLOW_DESERIALIZE
  • instanceMethodStepWorkflow - instance methods with "use step" directive
  • crossContextSerdeWorkflow - classes defined in step code are deserializable in workflow context
  • pages router addTenWorkflow via pages router
  • pages router promiseAllWorkflow via pages router
  • pages router sleepingWorkflow via pages router

Details by Category

❌ ▲ Vercel Production
App Passed Failed Skipped
❌ astro 42 1 4
✅ example 43 0 4
✅ express 43 0 4
❌ fastify 42 1 4
✅ hono 43 0 4
✅ nextjs-turbopack 46 0 1
✅ nextjs-webpack 46 0 1
❌ nitro 42 1 4
❌ nuxt 42 1 4
❌ sveltekit 42 1 4
✅ vite 43 0 4
✅ 💻 Local Development
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 📦 Local Production
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 🐘 Local Postgres
App Passed Failed Skipped
✅ astro-stable 43 0 4
✅ express-stable 43 0 4
✅ fastify-stable 43 0 4
✅ hono-stable 43 0 4
✅ nextjs-turbopack-stable 47 0 0
✅ nextjs-webpack-stable 47 0 0
✅ nitro-stable 43 0 4
✅ nuxt-stable 43 0 4
✅ sveltekit-stable 43 0 4
✅ vite-stable 43 0 4
✅ 🪟 Windows
App Passed Failed Skipped
✅ nextjs-turbopack 47 0 0
❌ 🌍 Community Worlds
App Passed Failed Skipped
✅ mongodb-dev 3 0 0
❌ mongodb 5 42 0
✅ redis-dev 3 0 0
❌ redis 5 42 0
✅ starter-dev 3 0 0
❌ starter 4 43 0
✅ turso-dev 3 0 0
❌ turso 5 42 0
✅ 📋 Other
App Passed Failed Skipped
✅ e2e-local-dev-nest-stable 43 0 4
✅ e2e-local-postgres-nest-stable 43 0 4
✅ e2e-local-prod-nest-stable 43 0 4

📋 View full workflow run


Some E2E test jobs failed:

  • Vercel Prod: failure
  • Local Dev: success
  • Local Prod: success
  • Local Postgres: success
  • Windows: success

Check the workflow run for details.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds new marketing/social proof sections to the docs homepage (useworkflow.dev) by porting a customer logo wall and a builder testimonial “tweet wall” into the existing home page layout.

Changes:

  • Inserted a new LogoWall section beneath the hero on the docs homepage.
  • Added a new TweetWall section (5 tweet-style testimonial cards) into the main homepage grid.
  • Introduced new components implementing the logo SVGs (using currentColor) and tweet cards using the existing shadcn Avatar styling.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File Description
docs/app/[lang]/(home)/page.tsx Wires the new LogoWall and TweetWall components into the homepage layout.
docs/app/[lang]/(home)/components/tweet-wall.tsx Adds the testimonial tweet wall component with a responsive multi-column layout and external links.
docs/app/[lang]/(home)/components/logo-wall.tsx Adds the customer logo wall component with inline SVG logos using currentColor.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +10 to +12
<div className="columns-1 gap-4 space-y-4 md:columns-2 lg:columns-3">
{TWEETS.map((tweet) => (
<div key={tweet.username} className="break-inside-avoid">
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The masonry container combines CSS columns with space-y-4. Because space-y-* adds margin-top based on DOM order (not per column), the first card in column 2/3 will also get a top margin, producing uneven top alignment. Prefer giving each item a bottom margin/padding (e.g., on the .break-inside-avoid wrapper) and remove space-y-4, keeping columns-* + gap-* for column spacing.

Suggested change
<div className="columns-1 gap-4 space-y-4 md:columns-2 lg:columns-3">
{TWEETS.map((tweet) => (
<div key={tweet.username} className="break-inside-avoid">
<div className="columns-1 gap-4 md:columns-2 lg:columns-3">
{TWEETS.map((tweet) => (
<div key={tweet.username} className="break-inside-avoid mb-4 last:mb-0">

Copilot uses AI. Check for mistakes.
Comment on lines +7 to +9
<p className="font-semibold text-2xl md:text-3xl lg:text-4xl tracking-tight text-center text-balance mb-6 md:mb-10">
What builders say about Workflow DevKit
</p>
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section title is rendered as a <p> even though other homepage sections use heading tags (h2, h3). Using a heading element here will improve document outline/SEO and keep heading semantics consistent across the homepage.

Suggested change
<p className="font-semibold text-2xl md:text-3xl lg:text-4xl tracking-tight text-center text-balance mb-6 md:mb-10">
What builders say about Workflow DevKit
</p>
<h2 className="font-semibold text-2xl md:text-3xl lg:text-4xl tracking-tight text-center text-balance mb-6 md:mb-10">
What builders say about Workflow DevKit
</h2>

Copilot uses AI. Check for mistakes.
Comment on lines +84 to +90
function InlineLink({
className,
...props
}: React.ComponentProps<'span'>): JSX.Element {
return (
<span className={cn('text-[rgb(29,155,240)]', className)} {...props} />
);
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

InlineLink renders a <span> (not an anchor) but is named like a link, which is misleading for future maintenance. Consider renaming it to something like InlineMention/InlineHandle, or change it to render an actual <a> when appropriate.

Copilot uses AI. Check for mistakes.
fill="none"
xmlns="http://www.w3.org/2000/svg"
{...props}
>
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The SVG logo is missing accessible text (e.g., a <title> element and/or aria-label). Other SVG icons in this docs codebase include <title> for screen readers. Add a title/label here (or explicitly mark the SVG aria-hidden if it’s purely decorative).

Suggested change
>
>
<title>Mux logo</title>

Copilot uses AI. Check for mistakes.
Comment on lines +40 to +42
xmlns="http://www.w3.org/2000/svg"
{...props}
>
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This SVG logo is missing accessible text (e.g., a <title> element and/or aria-label). Add a title/label here (or explicitly mark the SVG aria-hidden if it’s purely decorative) to avoid unlabeled images for screen readers.

Suggested change
xmlns="http://www.w3.org/2000/svg"
{...props}
>
xmlns="http://www.w3.org/2000/svg"
role="img"
aria-labelledby="whop-logo-title"
{...props}
>
<title id="whop-logo-title">Whop logo</title>

Copilot uses AI. Check for mistakes.
height="80"
viewBox="0 0 280 80"
fill="none"
xmlns="http://www.w3.org/2000/svg"
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This SVG logo is missing accessible text (e.g., a <title> element and/or aria-label). Add a title/label here (or explicitly mark the SVG aria-hidden if it’s purely decorative) to avoid unlabeled images for screen readers.

Suggested change
xmlns="http://www.w3.org/2000/svg"
xmlns="http://www.w3.org/2000/svg"
role="img"
aria-label="Neon logo"

Copilot uses AI. Check for mistakes.
@pranaygp pranaygp marked this pull request as draft February 6, 2026 23:48
- Replace simple bar chart with full O11yVisual animation ported from
  vercel.com/workflow (status bar, animated counter, grid lines, sequential
  animated bars with progress line)
- Move observability to its own full-width section
- Move tweet wall above "Get started quickly" templates section

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy link
Collaborator Author

@pranaygp pranaygp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good overall — the logo wall, tweet wall, and new o11y animation are solid additions. A few things to consider:

Layout change (page.tsx): Observability and Frameworks were previously in a side-by-side lg:grid-cols-2 layout and are now stacked vertically. Assuming this was intentional to give the new o11y animation more room, but wanted to flag it.

Animation replay (o11y-visual.tsx): useInView is used without { once: true }, so the animation will re-trigger every time the user scrolls the section back into view. The old observability section used viewport={{ once: true }}. If a user scrolls past and back, the bars will be at their current position and try to animate again. Consider either passing { once: true } to useInView, or resetting the motion values in the cleanup function so replay is clean.

No changeset needed since this is a docs-only change — confirmed.

return (
<motion.div
style={{
width: useTransform(width, (v) => `${v}%`),
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

useTransform is a React hook being called inside the JSX return rather than at the top of the component body. While it works (it's always called, not conditional), it's unconventional and also creates a new callback on every render. Consider extracting it:

const widthPercent = useTransform(width, (v) => `${v}%`);

return (
  <motion.div
    style={{ width: widthPercent, overflow }}
    ...

<div className="flex flex-col items-start">
<span className="text-sm font-medium flex items-center gap-1">
{name}
<svg
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The verification badge is hardcoded on every tweet. Are all five of these accounts actually verified on X? If not, this could be misleading — consider making it a per-tweet boolean in the TWEETS data.

export function O11yVisual(): JSX.Element {
const [isFinished, setIsFinished] = useState(false);
const ref = useRef<HTMLDivElement>(null);
const isInView = useInView(ref);
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: useInView(ref) without { once: true } means the animation restarts on every scroll-in. The old observability section used viewport={{ once: true }}. If the user scrolls past and returns, the bars will be mid-state and re-animate from there. Passing { once: true } would match the previous behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant