
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.
Articles
Front‑end development is where product intent becomes the interface people actually use. My writing approaches it as engineering rather than surface decoration, with attention to browser behaviour and code that remains accessible, fast, and safe for a team to change.

A Pages Router to App Router migration checklist for Next.js teams, covering routing, data fetching, caching, metadata, server components, and rollout.

How to isolate Core Web Vitals regressions after a redesign, covering LCP, INP, CLS, templates, scripts, images, fonts, data, and release evidence.

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 replatforming, recovery, SEO, performance, CMS, Vercel, and production debugging work.

Use Angular signals for performance optimisation with derived state, computed values, OnPush, effects, RxJS interop, and measuring whether work improved.

How to debug NextAuth when it works locally but fails in production, covering callback URLs, cookies, secrets, middleware, providers, and Vercel.

Manage Angular state with RxJS Subjects and derived streams, including combineLatest timing, AsyncPipe cleanup, local UI state and when signals fit better.

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 explained through production concerns: rendering, routing, caching, SEO, deployment, CMS data, and debugging.

A Next.js production triage checklist for broken deploys, covering rollback decisions, logs, environment drift, routes, auth, CMS data, and cache.

Memoisation helps JavaScript functions run faster by caching previous results. Here's a clear guide on how and when to use memoisation effectively.

A production runbook for stale CMS content in Next.js, covering webhooks, route dependencies, ISR, cache boundaries, preview, and editor trust.

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.

A headless CMS SEO checklist covering metadata, canonicals, schema, redirects, sitemaps, preview, internal links, image fields, and publishing controls.

Technical SEO launch criteria for Next.js migrations, covering URLs, redirects, canonicals, metadata, rendered HTML, schema, sitemaps, and recovery.

The JavaScript module pattern explained through closures and private state, plus the architectural lessons it still teaches modern developers today.

Compare rendered HTML before and after a migration, checking headings, metadata, links, schema, body copy, media, crawl signals, and launch risk.

Compare client‑side React caching, Next.js SSG, ISR and SSR caching, and Redis‑backed caches for reliable serverless data fetching and persistence.