Next.js

Next.js gives you the widest range of rendering choices, which means the main advanced task is drawing clean boundaries between static output, revalidated output, preview, and request-time rendering.

Rendering strategy

• separate fully static routes from routes that need revalidation or request-time rendering;
• keep shared CMS reads in a small content layer rather than duplicating fetch logic across route segments;
• scope cache invalidation to affected entities and paths instead of rebuilding everything; and
• keep static path generation independent from page rendering so large route sets stay manageable.

Preview and publishing

• isolate draft access behind preview or draft mode with signed URLs;
• keep preview credentials separate from delivery credentials;
• log webhook and revalidation failures with route-level detail; and
• make preview URLs environment-aware so staging and production stay predictable.

Operational guardrails

• fail builds clearly when locales, referenced entries, or SEO fields are missing;
• batch slug generation for large content sets;
• generate sitemap and feed data from the same query layer as routes; and
• treat content model changes as deployment-affecting changes when they alter route or block contracts.