Pulse Wall: I Let Sanity Run My Repost Marketplace's Content

Khalid Siyanbola — Sat, 19 Sep 2026 01:42:38 +0000

This is a submission for the Sanity Challenge, Path Two: Vibe-Code Something Strange

What I Built

Pulse Wall, a Sanity-powered showcase of repost campaigns and promoter spotlights. It's a spin-off of Pulse, a community-powered social promotion marketplace I'm building separately (businesses run repost campaigns, promoters earn money sharing them). Instead of reimplementing Pulse's full backend (Go, MongoDB, Paystack), I reused Pulse's Next.js UI and turned the campaign marketplace into pure content. Every campaign and promoter spotlight lives in Sanity and is editable in Studio, no redeploy needed for new content to go live.

Demo

https://pulse-sanity.onrender.com

Code

https://github.com/siyanbolagiggs1/pulse-sanity

My Build Process

I used Claude Code as my AI-native IDE for this build. I started by pointing it at my existing Pulse repo and asking it to reuse the Next.js UI (Tailwind theme, shadcn/ui components, marketing shell) rather than starting from scratch, then strip out everything backend-coupled (auth, wallet, Paystack, the Go API) and replace the campaign marketplace with a Sanity content layer.

What worked well: defining two schemas (campaign with a playful vibeScore field, spotlight) and embedding Sanity Studio directly into the Next.js app at /studio using next-sanity, so there's one deployable app instead of two.

Where it got stuck: CORS. Sanity blocks Studio API calls from origins it doesn't recognize, so both localhost and the deployed Render URL had to be explicitly added as CORS origins with credentials allowed before Studio would even load, not obvious until we hit a CorsOriginError in the browser console.

The bigger one: after publishing new campaigns in Studio, they weren't showing up on the live site. Turned out Next.js route segment config (revalidate/dynamic) only takes effect in page.tsx/layout.tsx files, not in an arbitrary component I'd put it in. It was silently ignored, so the homepage got fully statically prerendered at build time and never picked up new Sanity content, directly undercutting the "live from Sanity, no rebuild" pitch. Moving export const dynamic = "force-dynamic" into page.tsx fixed it.

I deployed to Render instead of Vercel, using a render.yaml blueprint for one-click deploy, and added a GitHub Actions workflow to ping the free-tier instance every 5 minutes so it doesn't spin down between judge visits.

I didn't reach into the App SDK or Workflows for this one, kept scope to the Content Lake, Studio, and GROQ queries.

Sanity Project Details

Project ID: b2izifpg, dataset: production

Agent Session

Pulse Wall: Claude Code build transcript (curated) Sanity Challenge, Path Two submission Tool: Claude Code (Sonnet 5)