TanStack

TanStack is a strong fit for Paragraph CMS when your team wants a React-first app with explicit route data loading, structured route boundaries, and direct control over how published and draft content is delivered.

Recommended architecture

• fetch published content through shared server-side loaders or helpers rather than inside leaf components;
• map CMS slugs and locales into one route contract so route params and content lookups stay aligned;
• prerender stable CMS-backed routes where possible and leave preview or highly dynamic paths on the server; and
• keep draft reads behind server-only code so preview credentials never ship to the client.

Implementation checklist

• create one CMS client for published delivery and a separate preview path for drafts;
• derive route params from CMS slugs before they reach page components;
• prefetch shared settings, navigation, and SEO models close to the route tree; and
• trigger cache refresh or rebuild work when editors publish.

When TanStack is a good fit

Choose this path when you want React ergonomics with stronger routing and data-loading structure than a plain React application, without moving to Next.js.