Should You Move from Contentful to Sanity?
How to decide whether moving from Contentful to Sanity makes sense for a Next.js website, including workflow, modelling, preview, and migration risk.
Articles
Next.js
Next.js is an open‑source React framework created by Vercel. It is used to build fast, scalable websites and web applications, combining React with routing, data fetching, API routes, automatic code splitting, TypeScript support, server‑side rendering (SSR), and static site generation (SSG).
Below you will find a subset of articles from my blog specifically about Next.js as well as Next.js platform consulting. This is an area I have worked with for many years, and it has been a regular subject in my writing. There are fifty‑one articles collected together for you below.
Should You Move from Contentful to Sanity? 
Fixing Contentful Preview in Next.js Draft Mode. Fixing Contentful Preview in Next.js Draft Mode
Fix Contentful preview in Next.js by checking Draft Mode, preview URLs, iframe cookies, draft data boundaries, auth, performance, and editor trust.
Next.js Build Failing on Vercel: How to Find the First Real Failure. Next.js Build Failing on Vercel: How to Find the First Real Failure
A practical way to debug failing Next.js builds on Vercel, from first useful error lines and environment drift to route generation and memory pressure.
Traffic Dropped After a Replatform: The Technical Checks I Run First. Traffic Dropped After a Replatform: The Technical Checks I Run First
Diagnose traffic drops after a redesign, migration, or replatform by checking route parity, rendered HTML, redirects, canonicals, sitemaps, and schema.
E‑Commerce SEO Migration: Product and Category Pages in Next.js. E‑Commerce SEO Migration: Product and Category Pages in Next.js
How to migrate e‑commerce product and category pages to Next.js without losing SEO value, including URLs, filters, schema, canonicals, and redirects.
Should You Move a Shopify Storefront to Next.js? Should You Move a Shopify Storefront to Next.js?
Decide whether Shopify to Next.js is worth it by weighing storefront control, SEO, performance, checkout, apps, content workflow, cost, and risk.
Next.js Multi‑Tenant Architecture. Next.js Multi‑Tenant Architecture
How to design multi‑tenant Next.js architecture across routing, domains, configuration, content, caching, previews, analytics, and team ownership.
Content Security Policy in Next.js: Static Pages, Nonces, and Real‑World Trade‑Offs. Content Security Policy in Next.js: Static Pages, Nonces, and Real‑World Trade‑Offs
Plan Content Security Policy in Next.js with static pages, nonces, third‑party scripts, headers, frames, previews, and incremental deployment safely.
Pages Router to App Router Migration Risk Checklist. Pages Router to App Router Migration Risk Checklist
A Pages Router to App Router migration checklist for Next.js teams, covering routing, data fetching, caching, metadata, server components, and rollout.
When Production Data Breaks a Next.js Site. When Production Data Breaks a Next.js Site
Why production data breaks Next.js sites, including CMS fields, slugs, images, relations, dates, rich text, generated routes, and validation gaps.
How to Vet a Senior Next.js Developer for a Replatform or Recovery Project. How to Vet a Senior Next.js Developer for a Replatform or Recovery Project
How to vet a senior Next.js developer for replatforming, recovery, SEO, performance, CMS, Vercel, and production debugging work.
NextAuth Works Locally but Fails in Production. NextAuth Works Locally but Fails in Production
How to debug NextAuth when it works locally but fails in production, covering callback URLs, cookies, secrets, middleware, providers, and Vercel.
Why Next.js Builds Time Out on Vercel. Why Next.js Builds Time Out on Vercel
Debug Next.js build timeouts on Vercel by checking route generation, CMS data fan‑out, memory pressure, image work, caching, logs, and platform limits.
React Developer vs. Next.js Developer: What Actually Changes in Production. React Developer vs. Next.js Developer: What Actually Changes in Production
React developer vs. Next.js developer explained through production concerns: rendering, routing, caching, SEO, deployment, CMS data, and debugging.
Next.js Site Broke After Deploy: A Production Triage Checklist. Next.js Site Broke After Deploy: A Production Triage Checklist
A Next.js production triage checklist for broken deploys, covering rollback decisions, logs, environment drift, routes, auth, CMS data, and cache.
Next.js Proxy Replaces Middleware: What Changes in Practice. Next.js Proxy Replaces Middleware: What Changes in Practice
Next.js Proxy replaces Middleware in v16. See what changed, how to migrate to proxy.ts, and when request‑time interception still belongs in production.
CMS Content Not Updating in Next.js. CMS Content Not Updating in Next.js
A production runbook for stale CMS content in Next.js, covering webhooks, route dependencies, ISR, cache boundaries, preview and editor trust.
Handling API Routes in Next.js: When to Use Server Actions vs. API Routes. Handling API Routes in Next.js: When to Use Server Actions vs. API Routes
Next.js gives us two ways to handle back‑end logic: API Routes and Server Actions. Here, I clearly explain when to choose each approach for the best results.