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

This piece is a submission for the Sanity Challenge, Path Two: Vibe-Code Something Strange. The project is called Pulse Wall, a showcase of repost campaigns and promoter spotlights built using Sanity. Instead of replicating Pulse's full backend, the focus was on adapting Pulse's Next.js UI to work as pure content in Sanity, with no need for redeployment for new content.

The build process involved using Claude Code as an AI-native IDE, starting with the existing Pulse repo and reusing the Next.js UI (Tailwind theme, shadcn/ui components, marketing shell), then stripping out everything backend-coupled and replacing it with a Sanity content layer. Defining schemas for campaigns and spotlights and embedding Sanity Studio directly into the Next.js app at /studio simplified deployment, but CORS issues prevented the Studio API calls from loading.

Adding the CORS origins explicitly resolved this issue. However, new campaigns not appearing on the live site was due to Next.js route segment config only taking effect in page.tsx/layout.tsx files, not in arbitrary components. Adding export const dynamic = force-dynamic; to the page.tsx solved this problem, ensuring live updates from Sanity without a rebuild.

The project was deployed to Render using a render.yaml blueprint for one-click deployment and a GitHub Actions workflow to keep the free-tier instance active between judge visits. The scope was kept narrow, focusing on the Content Lake, Studio, and GROQ queries.