Headless CMS: the agent answers

I’d use **Sanity** for this.

It fits a Next.js marketing site especially well:

- Marketers edit structured content in Sanity Studio.
- Its Presentation tool provides live preview and click-to-edit overlays on the actual Next.js page.
- The official `next-sanity` integration supports App Router, Draft Mode, live updates, caching, and on-demand revalidation. Publishing copy can update the site without rebuilding or deploying the application. [Sanity’s Next.js documentation](https://www.sanity.io/docs/nextjs/introduction)
- Drafts remain private until published.
- Document history supports reviewing and reverting revisions, although retention depends on the plan: currently 3 days on Free, 90 days on Growth, and 365 days on Enterprise. [History details](https://www.sanity.io/docs/user-guides/history-experience)
- Larger campaigns can be grouped, previewed, scheduled, and published together through Content Releases, though that is an Enterprise feature. Single-document scheduled drafts are available on Growth. [Content Releases](https://www.sanity.io/docs/user-guides/content-releases)

I would model the homepage as sections—hero, proof points, testimonials, CTA—not as one unrestricted rich-text field. Marketing can change wording and reorder approved sections, while developers retain control of components, accessibility, and layout.

What I’d evaluate first:

| Platform | Why consider it | Why I’d choose it instead |
|---|---|---|
| **Storyblok** | Probably the strongest marketer-first visual page-building experience; solid Next.js preview and detailed version restoration. [Visual preview](https://www.storyblok.com/docs/guides/nextjs/visual-preview), [history](https://www.storyblok.com/docs/manuals/history) | Pick it over Sanity if marketers must frequently assemble and rearrange landing pages themselves. |
| **Contentful** | Mature enterprise product, governance, localization, roles, version snapshots, and Vercel preview integration. [Versioning](https://www.contentful.com/help/faq/versioning/), [Vercel preview](https://www.contentful.com/help/apps/vercel-app/) | Pick it when enterprise procurement, localization, or cross-channel governance outweigh customization and developer ergonomics. |
| **DatoCMS** | Polished hosted product with Draft Mode, real-time preview, and click-to-edit support for Next.js. [Visual editing](https://www.datocms.com/docs/next-js/visual-editing) | A good lower-complexity alternative if its pricing and limits fit. |
| **Payload** | TypeScript-native, highly customizable, and self-hostable | Pick it when data ownership or keeping the CMS inside your own infrastructure is a firm requirement; expect more operational responsibility. |

My practical shortlist would be **Sanity versus Storyblok**. For “marketing edits copy safely,” I’d select Sanity. For “marketing visually constructs pages from approved blocks,” I’d lean Storyblok.

One important distinction: CMS publishing should not trigger a full application deployment. Use Next.js Draft Mode for previews and either Sanity’s live-content integration or a signed webhook calling `revalidateTag`/`revalidatePath` for published content. Code and schema changes still deploy normally; copy changes do not.

I’d use **Sanity** for this—assuming you want a managed headless CMS and your developers are comfortable defining the content schema in code.

Sanity fits particularly well because its official Next.js tooling supports App Router, Server Components, Draft Mode, automatic cache revalidation, and click-to-edit visual preview. Editors can work inside its Presentation tool and see homepage changes in context before publishing. [Sanity’s Next.js documentation](https://www.sanity.io/docs/nextjs/introduction)

The setup I’d ship:

- Model the homepage as structured sections—hero, proof points, CTAs, testimonials—not an unrestricted HTML field.
- Render published content through `next-sanity`.
- Enable Sanity Presentation plus Next.js Draft Mode for authenticated, live-as-you-type previews.
- Use the Live Content API or a publish webhook with on-demand revalidation, so publishing updates the site without a deployment.
- Give marketing edit/publish permissions while reserving schemas and component choices for engineering.

Sanity has document history and restoration, but retention depends on the plan: currently 3 days on Free, 90 days on Growth, and 365 days on Enterprise. That deserves checking against your rollback requirements. [Sanity history documentation](https://www.sanity.io/docs/user-guides/history-experience) Grouped, scheduled Content Releases are also plan-dependent; ordinary drafts and publishing are enough for many homepage workflows. [Content Releases documentation](https://www.sanity.io/docs/apis-and-sdks/content-releases-api)

What I’d evaluate first:

| Platform | Why it made the shortlist | Why I wouldn’t choose it first here |
|---|---|---|
| **Storyblok** | Probably the strongest alternative if marketing wants a visual page-builder. It has in-context editing, draft/published states, scheduling, and restorable version history. [Preview](https://www.storyblok.com/docs/guides/nextjs/visual-preview), [history](https://www.storyblok.com/docs/manuals/history) | Its block-oriented authoring can encourage marketers to assemble pages rather than edit governed content. I’d choose it over Sanity if that autonomy is intentional. |
| **Contentful** | Mature governance, roles, localization, releases, and a solid React/Next.js live-preview SDK. [Live Preview](https://www.contentful.com/developers/docs/tutorials/preview/live-preview/) | Generally heavier operationally and commercially for a straightforward marketing site. Its documented entry versioning records published snapshots and is limited to the master environment. [Versioning](https://www.contentful.com/help/faq/versioning/) |
| **Payload** | Excellent TypeScript/Next.js fit, self-hosting, drafts, autosave, diffs, restoration, scheduling, and server-side live preview. [Versions](https://payloadcms.com/docs/versions/overview), [preview](https://payloadcms.com/docs/live-preview/server) | You own the database, hosting, upgrades, backups, and CMS operations. I’d choose it if data ownership or self-hosting outweighed minimizing maintenance. |

My decision rule is simple: **Sanity for structured content and developer-controlled flexibility; Storyblok when visual page composition is the dominant requirement; Payload when self-hosting is required.** For the scenario described, Sanity is the best default.

I’d use **Sanity Growth** for this.

It fits a Next.js marketing site especially well:

- Official `next-sanity` support for App Router, Server Components, Draft Mode, caching, and secure preview.
- Marketers can preview drafts inside the rendered site, with live updates and click-to-edit overlays.
- Publishing can update the production site without a deployment, using Sanity Live or webhook-driven Next.js revalidation.
- Draft/published separation, scheduled drafts, collaboration, and document history are built in.
- Growth currently costs **$15/editor/month** and retains revision history for **90 days**. Sanity Free has only three days of history and less suitable roles, so I wouldn’t use it for a production marketing team. [Next.js integration](https://www.sanity.io/docs/nextjs/introduction), [visual editing](https://www.sanity.io/docs/visual-editing), [history retention](https://www.sanity.io/docs/user-guides/history-experience), [pricing](https://www.sanity.io/pricing)

One important architectural point: moving copy into a CMS does not automatically eliminate deploys. Production pages should fetch cached published content and use either Sanity Live or an authenticated publish webhook that calls `revalidateTag`/`revalidatePath`. Preview should use Next.js Draft Mode and fetch uncached draft content. Code and schema changes still deploy; copy changes do not.

What I’d shortlist first:

| Platform | Why consider it | Why it wouldn’t be my default |
|---|---|---|
| **Storyblok** | Probably the most approachable visual, component-based editor for marketers; strong Next.js preview | Growth is $99/month, but history retention is only 30 days; coordinated Releases require a custom-priced tier. [Pricing](https://www.storyblok.com/pricing), [Next.js preview](https://www.storyblok.com/docs/guides/nextjs/visual-preview) |
| **Contentful** | Mature hosted platform, solid live preview, governance, and enterprise ecosystem | Usually more administration and cost than this use case needs; version snapshots are created around publication and versioning is limited to the master environment. [Live preview](https://www.contentful.com/developers/docs/tutorials/preview/live-preview/), [versions](https://www.contentful.com/help/content-and-entries/versions/) |
| **Payload** | Excellent if you want open-source, TypeScript-native ownership; drafts, diffs, restoration, scheduling, and live preview are strong | You own the database, hosting, upgrades, backups, and operational reliability—extra work if the objective is simply marketer autonomy. [Versions](https://payloadcms.com/docs/versions/overview), [live preview](https://payloadcms.com/docs/live-preview) |
| **DatoCMS** | Clean hosted product with draft mode, real-time preview, and visual editing on every current plan | A credible second choice, but Sanity’s Next.js tooling and customizable editorial workflows give it the edge here. [Next.js visual editing](https://www.datocms.com/docs/next-js/visual-editing) |

The main caveat with Sanity is long-term or campaign-level versioning: Growth history expires after 90 days, and coordinated multi-document Content Releases are an Enterprise feature. If “proper versioning” means indefinite audit retention or staging an entire campaign as one atomic release, I’d evaluate Enterprise pricing—or choose self-hosted Payload with controlled backups—before committing.

I’d use **Sanity** for this Next.js site.

It has the cleanest fit for your workflow:

- Marketers edit structured homepage content in Sanity Studio.
- Sanity’s Presentation tool provides live preview and click-to-edit overlays inside the rendered site.
- Next.js Draft Mode keeps unpublished content private.
- Published changes can update through Sanity’s Live Content API or on-demand revalidation—so changing copy does **not** require a new application deployment.
- Draft history is built in, with retention depending on plan. Scheduled drafts start on Growth; coordinated multi-page Content Releases and full release rollback are Enterprise features. [Next.js integration](https://www.sanity.io/docs/nextjs/introduction), [plans and history limits](https://www.sanity.io/pricing?lang=en)

A sensible architecture would be:

```text
Sanity Studio → draft preview → approval/publish
                                   ↓
Sanity Content Lake → Next.js server components → cached homepage
                                   ↑
                    live update or cache revalidation
```

Keep layout, typography, and components in Next.js; expose only controlled content fields such as headline, subheading, CTA label/link, announcements, testimonials, and SEO metadata. I would avoid giving marketers an unrestricted page builder unless assembling pages is genuinely part of their job.

What I’d evaluate first:

- **Storyblok** — my runner-up, and possibly the better choice if marketers strongly prefer a visual, block-based page builder. Its Next.js visual editor supports clicking components and seeing draft changes in real time. It also creates versions on saves and supports restoring earlier versions; comparison and visual-history capabilities are paid features. [Next.js visual preview](https://www.storyblok.com/docs/guides/nextjs/visual-preview), [history and restoration](https://www.storyblok.com/docs/manuals/history)

- **Contentful** — mature, polished, and well suited to larger organizations. It offers side-by-side live preview and a React/Next.js-oriented SDK. However, its model and administration can feel heavier for a homepage-copy problem, and its documented entry snapshots are created on publish and available only in the master environment. [live preview](https://www.contentful.com/developers/docs/tutorials/preview/live-preview/), [versioning](https://www.contentful.com/help/faq/versioning/)

- **Payload** — the choice if owning the CMS code and database matters. It integrates closely with Next.js and has excellent drafts, autosave, diffs, restoration, scheduling, and server-side live preview. The tradeoff is that your team owns hosting, upgrades, database operations, and more of the editorial experience. [versions](https://payloadcms.com/docs/versions/overview), [Next.js live preview](https://payloadcms.com/docs/live-preview/server)

- **Strapi** — worth considering for self-hosting and conventional REST/GraphQL content management, but I wouldn’t choose it ahead of Payload for a Next.js-centric project or ahead of Sanity/Storyblok for editorial preview.

The important caveat is “proper versioning.” If you mean ordinary draft history and recovering recent changes, Sanity is a strong default. If you mean long-lived audit history, comparing arbitrary versions, and atomically rolling back an entire campaign across several pages, confirm the required Sanity plan before committing—the advanced release workflow is an Enterprise capability. [Sanity Content Releases](https://www.sanity.io/docs/user-guides/content-releases)

So my decision would be: **Sanity by default; Storyblok if visual page composition is the dominant requirement; Payload if data ownership and self-hosting outweigh operational simplicity.**

I’d use **Sanity** for this Next.js site.

It gives you the best balance of developer control and marketer autonomy:

- Marketers edit structured homepage content in Sanity Studio.
- Sanity’s Presentation tool embeds the real site, shows drafts live, and supports click-to-edit overlays.
- The official `next-sanity` integration supports App Router, Server Components, Draft Mode, caching, and automatic revalidation. Published copy can appear without rebuilding or redeploying the app. [Sanity’s Next.js integration](https://www.sanity.io/docs/nextjs/introduction)
- Drafts remain separate from published content, while Content Releases can group and schedule coordinated changes. [Content releases and versions](https://www.sanity.io/docs/apis-and-sdks/js-client-releases)
- Editors get document history and restoration. Note that history retention depends on the plan—currently 3 days on Free, 90 on Growth, and 365 on Enterprise. [History retention](https://www.sanity.io/docs/user-guides/history-experience)

I’d implement the homepage as constrained sections—hero, proof points, customer logos, CTA, SEO metadata—not a completely free-form page builder. Marketing can change copy, reorder approved sections, preview responsive layouts, and publish safely without accidentally redesigning the site.

The other platforms I’d shortlist first:

| Platform | Why I considered it | Why Sanity wins here |
|---|---|---|
| **Storyblok** | Probably the strongest alternative when marketers want a highly visual block-based page builder. It has live Next.js preview plus restorable page history. [Preview](https://www.storyblok.com/docs/guides/nextjs/visual-preview), [history](https://www.storyblok.com/docs/manuals/history) | I’d choose Storyblok instead if drag-and-drop page composition is the dominant requirement. Sanity offers a more flexible schema and developer workflow. Some Storyblok comparison, visual-history, scheduling, and release features are paid-tier dependent. |
| **Contentful** | Mature, enterprise-friendly, with Next.js-compatible live preview and snapshots of published entries. [Live preview](https://www.contentful.com/developers/docs/tutorials/preview/live-preview/), [versioning](https://www.contentful.com/help/faq/versioning/) | Strong governance, but typically heavier and less pleasant to customize. Its documented entry snapshots are created on publish, which is less granular than Sanity’s editing history. |
| **Payload** | Excellent if you want an open-source, self-hosted, TypeScript-first CMS living close to Next.js. It has live preview, drafts, diffs, restoration, and scheduled publishing. [Live preview](https://payloadcms.com/docs/live-preview/server), [versions](https://payloadcms.com/docs/versions/overview) | You own more infrastructure, database operations, upgrades, backups, and availability. I’d pick it when data ownership or self-hosting outweighs operational simplicity. |
| **DatoCMS** | Polished hosted option with Draft Mode, real-time updates, click-to-edit overlays, and side-by-side Next.js previews. [Next.js visual editing](https://www.datocms.com/docs/next-js/visual-editing) | A credible runner-up, but Sanity’s customizable Studio, querying model, and release/version workflow are a stronger overall fit for an evolving marketing site. |

The resulting publishing path should be:

`Edit draft → preview the actual Next.js page → approve/publish → invalidate cached content → visitors see the update`

No application deploy is involved unless the team changes code, layout, or the content schema.

I’d use **Sanity** for this.

It fits a Next.js marketing site especially well:

- Editors get a visual, click-to-edit preview and see draft changes update live.
- Next.js App Router and Draft Mode have first-party integration through `next-sanity`.
- Structured schemas keep editors within safe design constraints.
- Drafts remain separate from published content.
- Document history supports inspecting and restoring revisions.
- Content Releases can group and schedule coordinated changes, although some advanced release/rollback features depend on the plan.
- Publishing can trigger on-demand revalidation, so a copy change updates the site without rebuilding and deploying the application.

Sanity’s current Next.js guide covers the complete preview flow: Draft Mode, authenticated draft fetching, live updates, and click-to-edit overlays in its Presentation Tool. [Sanity Next.js visual editing guide](https://www.sanity.io/docs/nextjs/visual-editing-with-next-js-app-router) Its history retention varies by plan, so I would verify that the chosen tier meets your rollback requirements. [Sanity history documentation](https://www.sanity.io/docs/user-guides/history-experience)

What I’d evaluate first:

| Platform | Why consider it | Why I wouldn’t lead with it here |
|---|---|---|
| **Storyblok** | Probably the strongest alternative when visual page-building is the top priority; excellent visual editor, reusable blocks, comparison and restore tools. | Its component/block model can encourage marketers to assemble layouts rather than simply manage governed content. Some history comparison features are paid. [Visual preview](https://www.storyblok.com/docs/guides/nextjs/visual-preview), [history](https://www.storyblok.com/docs/manuals/history) |
| **Contentful** | Mature SaaS, strong governance, localization, roles, workflows, and live preview; a safe enterprise shortlist choice. | Often more expensive and administratively heavier than necessary for a marketing homepage. Its modeling and editor experience can feel less flexible than Sanity’s customized Studio. [Contentful preview documentation](https://www.contentful.com/developers/docs/tutorials/preview/content-preview/) |
| **Payload** | Best option if self-hosting, database ownership, TypeScript configuration, or keeping CMS and Next.js together is strategically important. It has drafts, diffs, restoration, access control, and live preview. | Your team owns the database, upgrades, hosting, backups, and CMS operations. That is extra responsibility when the real problem is editorial independence. [Payload versions](https://payloadcms.com/docs/versions/overview), [live preview](https://payloadcms.com/docs/live-preview/server) |

I’d implement the homepage as structured sections—hero, proof points, testimonials, CTAs—not as one unrestricted rich-text field. Production reads only published content; an authenticated preview route enables Next.js Draft Mode; publishing calls a revalidation webhook for the affected route.

That removes application deploys from the copy-editing loop while preserving preview, rollback, permissions, and design control. If the marketing team explicitly wants drag-and-drop page composition, I’d choose **Storyblok instead**; otherwise, **Sanity is my default**.

I’d use **Sanity** for this.

It has a strong first-party Next.js integration, supports App Router Draft Mode and visual editing, and gives marketers a hosted Studio where they can edit structured homepage content without touching the repository. Published changes can trigger Next.js on-demand revalidation, so content updates appear without a code deploy. [Next.js integration](https://www.sanity.io/docs/nextjs)

A sensible setup would be:

- Model the homepage as structured sections—hero, proof points, CTAs, testimonials—not an unrestricted page builder.
- Embed or separately host Sanity Studio.
- Use Next.js Draft Mode for authenticated previews of unpublished content.
- Enable Sanity’s visual editing so selecting text on the preview opens the corresponding field.
- On publish, call a protected revalidation webhook for the affected paths.
- Keep the production site reading only the published perspective.

Sanity retains document revisions and lets editors inspect or restore history. Current retention is three days on Free, 90 days on Growth, and 365 days on Enterprise, so I would budget for Growth if “proper versioning” means more than emergency rollback. Growth is currently listed at $15 per seat/month. Coordinated multi-page releases are substantially more expensive because Content Releases are an Enterprise feature; ordinary drafts and scheduled drafts are enough for many marketing sites. [History retention](https://www.sanity.io/docs/user-guides/history-experience) · [Pricing](https://www.sanity.io/pricing) · [Content Releases](https://www.sanity.io/docs/user-guides/content-releases)

What I’d evaluate alongside it:

| Platform | Why it made the shortlist | Why I wouldn’t choose it first |
|---|---|---|
| **Storyblok** | Probably the strongest choice if marketers demand a visual, component-based page builder; good Next.js preview and restorable history. | More opinionated around “stories” and blocks, with important workflow/history capabilities and longer retention tied to higher tiers. Growth currently starts at $99/month. [Next.js preview](https://www.storyblok.com/docs/guides/nextjs/visual-preview) · [History](https://www.storyblok.com/docs/manuals/history) · [Pricing](https://www.storyblok.com/pricing) |
| **Contentful** | Mature governance, localization, roles, versioning, and React/Next.js live preview. | Often more platform and pricing complexity than one marketing site needs; I’d favor it for a larger organization already standardizing content across products and regions. [Live preview](https://www.contentful.com/developers/docs/tutorials/preview/live-preview/) |
| **Payload** | Excellent TypeScript/Next.js fit, open source, self-hostable, with drafts, versions, scheduled publishing, and live preview. | You own the database, hosting, upgrades, backups, and CMS availability. Great when control or data residency matters; less attractive when the goal is simply to remove engineering from routine copy changes. [Drafts and versions](https://payloadcms.com/docs/versions/drafts) · [Live preview](https://payloadcms.com/docs/live-preview/server) |

My decision rule: choose **Sanity by default**, **Storyblok if the marketing team prioritizes drag-and-drop visual composition**, and **Payload if self-hosting and ownership outweigh operational simplicity**. Before committing, I’d run a short editor test using the real homepage—one marketer changes the hero, previews it, publishes it, and restores an earlier version. That usually exposes the right answer faster than a feature matrix.

I’d use **Sanity** for this Next.js app.

It fits the workflow well:

- Marketing edits structured homepage content in Sanity Studio.
- Sanity’s Presentation tool provides live, click-to-edit previews through Next.js Draft Mode.
- Draft and published content remain separate.
- Editors can inspect and restore document history; retention is currently 3 days on Free, 90 days on Growth, and 365 days on Enterprise.
- Publishing can trigger signed, on-demand Next.js cache revalidation. That updates the homepage without rebuilding or deploying the application.
- The schema and Studio configuration live in your repository, so developers retain control over what editors can change.

Sanity has a first-party Next.js toolkit covering App Router, typed GROQ queries, Draft Mode, visual editing, and live content. Its official documentation also provides a webhook pattern for `revalidatePath` or `revalidateTag`. [Next.js integration](https://www.sanity.io/docs/nextjs), [cache revalidation](https://www.sanity.io/docs/nextjs/validating-sanity-webhooks-nextjs), [history behavior](https://www.sanity.io/docs/user-guides/history-experience)

I would model the homepage as constrained sections—hero, proof points, testimonials, CTA—not as one unrestricted rich-text field. Marketing could change copy, links, images, ordering, and approved section variants, while layout and design-system rules remain in React.

What I’d evaluate first:

| Platform | Why consider it | Why I wouldn’t lead with it here |
|---|---|---|
| **Storyblok** | Probably the strongest alternative when an extremely visual, component/page-builder experience is the top priority. It has in-context editing and restorable saved versions. [Visual Editor](https://www.storyblok.com/docs/concepts/visual-editor), [history](https://www.storyblok.com/docs/manuals/history) | More page-builder-shaped, and current paid tiers jump from $99 to $349/month. Version retention is plan-limited. [Pricing](https://www.storyblok.com/pricing) |
| **Contentful** | Mature governance, environments, roles, localization, and enterprise ecosystem. Its live-preview SDK is optimized for React/Next.js. [Live Preview](https://www.contentful.com/developers/docs/tutorials/preview/live-preview/) | Generally heavier and less pleasant to customize. Standard entry history snapshots are created on publication and versioning is limited to the master environment. [Versioning](https://www.contentful.com/help/faq/versioning/) |
| **DatoCMS** | Polished editor experience, visual mode, good Next.js support, and relatively quick implementation. [Visual editing](https://www.datocms.com/docs/next-js/visual-editing) | A strong smaller-team choice, but Sanity gives me more flexibility in modeling and customizing the editorial workflow. |
| **Payload** | Best candidate if self-hosting, database ownership, or keeping CMS code inside the Next.js/TypeScript stack is important. It supports drafts, diffs, restoration, autosave, scheduling, and live preview. [Versions](https://payloadcms.com/docs/versions/overview), [Live Preview](https://payloadcms.com/docs/live-preview) | Your team owns the hosting, upgrades, database, backups, and operational reliability. That is unnecessary overhead if the immediate problem is marketing autonomy. |

One caveat: if “proper versioning” means coordinated campaign releases spanning several pages, not merely restoring individual documents, verify the commercial tier before committing. Sanity’s single-document scheduled drafts are on Growth, while full multi-document Content Releases are currently an Enterprise feature. [Content Releases](https://www.sanity.io/docs/user-guides/content-releases), [pricing](https://www.sanity.io/pricing?lang=en)

My practical choice would therefore be **Sanity Growth + Next.js App Router + Draft Mode/Presentation + signed webhook revalidation**. I’d switch the recommendation to Storyblok only if the marketing team strongly prioritizes a page-builder-style visual editor over developer flexibility.

I’d use **Sanity** for this.

It fits a Next.js site particularly well:

- Marketing edits structured homepage content in Sanity Studio.
- Production fetches only the published perspective.
- Next.js Draft Mode powers a private preview.
- Sanity’s Presentation tool provides live preview and click-to-edit overlays directly on the rendered page. [Sanity Visual Editing](https://www.sanity.io/docs/visual-editing)
- Content Releases let the team group, preview, schedule, and revert coordinated changes. [Content Releases guide](https://www.sanity.io/docs/user-guides/content-releases)
- Document history records changes and authors, though retention depends on the plan: currently 3 days on Free, 90 on Growth, and 365 on Enterprise. [History documentation](https://www.sanity.io/docs/user-guides/history-experience)

Publishing would trigger a signed webhook that calls `revalidateTag("homepage")` or `revalidatePath("/")`. The updated copy then appears without rebuilding or deploying the application. Code, component, and content-schema changes would still require deployment—which is the boundary you want.

I’d model the homepage as controlled sections rather than giving marketers an unrestricted page builder: hero, logos, benefits, testimonials, CTA, SEO metadata, and perhaps an approved array of section types. That preserves design quality while giving marketing useful autonomy.

What I’d evaluate alongside it:

| Platform | Why consider it | Why it wouldn’t be my default |
|---|---|---|
| **Storyblok** | Probably the strongest alternative when marketers want a highly visual, component-block page-building experience. Its Next.js integration supports real-time visual editing, and its history can compare and restore saved versions. [Next.js preview](https://www.storyblok.com/docs/guides/nextjs/visual-preview) · [History](https://www.storyblok.com/docs/manuals/history) | More page-builder-oriented than necessary if the main requirement is governed copy editing. Some advanced history features are paid. |
| **Contentful** | Mature governance, roles, environments, APIs, and enterprise adoption. | Often heavier and costlier than this use case needs. Its documented entry snapshots are created on publish or republish, which is less appealing than richer draft-oriented history. [Contentful versioning](https://www.contentful.com/help/faq/versioning/) |
| **DatoCMS** | Excellent editorial experience and notably straightforward Next.js visual editing, including Draft Mode, real-time updates, and click-to-edit. [DatoCMS Next.js visual editing](https://www.datocms.com/docs/next-js/visual-editing) | A very close second; I’d select it if the team preferred its interface during a hands-on trial. Sanity offers more flexibility if the content model and workflows grow. |
| **Payload** | Open source, TypeScript-native, works closely with Next.js, and provides drafts, version diffs, restoration, scheduling, and live preview. [Versions](https://payloadcms.com/docs/versions/overview) · [Live Preview](https://payloadcms.com/docs/live-preview) | You own more infrastructure, upgrades, security, and operational work. I’d choose it when self-hosting or data ownership is a requirement, not merely to edit homepage copy. |

My practical decision would be: **Sanity by default; Storyblok if marketing explicitly wants drag-and-drop visual composition; Payload if self-hosting is mandatory.** Before committing, I’d give two marketers the same 30-minute homepage-editing exercise in Sanity and Storyblok—the editorial preference is the only factor likely to overturn the technical recommendation.

I’d use **Storyblok** for this case. It best matches a marketing-led workflow: editors can change the homepage in a visual editor, see draft changes rendered by the real Next.js components, then publish without involving Git or triggering a full deployment. It also records versions, shows diffs, and supports restoring earlier content. [Storyblok’s Visual Editor](https://www.storyblok.com/docs/manuals/visual-editor) and [version history](https://www.storyblok.com/docs/manuals/history) cover those workflows directly.

I’d implement it like this:

- Model the homepage as approved content blocks—hero, testimonials, CTA, feature grid—not unrestricted HTML.
- Render those blocks in Next.js through a controlled component registry.
- Use draft content and the Storyblok Bridge inside Next.js Draft Mode for live preview.
- Fetch published content using ISR, then have a publish webhook call `revalidateTag()` or `revalidatePath()`. Publishing copy becomes a cache refresh, not a deployment.
- Give marketing edit/publish permissions while developers retain control over schemas and components.

What I’d evaluate first:

| Platform | Why it made the shortlist | Why I wouldn’t choose it first here |
|---|---|---|
| **Sanity** | Excellent Next.js tooling, highly customizable Studio, real-time collaboration, visual editing | More implementation and editorial-UI design work; history retention depends on plan—currently 3 days on Free and 90 days on Growth. [Visual Editing](https://www.sanity.io/docs/visual-editing), [history limits](https://www.sanity.io/docs/user-guides/history-experience) |
| **Contentful** | Mature governance, roles, localization, enterprise ecosystem, solid Next.js live preview | Often heavier and more expensive than needed for a marketing homepage; its entry-oriented editor is less naturally page-builder-like. [Live Preview](https://www.contentful.com/developers/docs/tutorials/preview/live-preview/) |
| **DatoCMS** | Polished, relatively simple, strong Next.js visual editing and real-time draft preview | Very credible runner-up, but Storyblok’s component/page editing model is especially intuitive for marketer-managed landing pages. [Next.js visual editing](https://www.datocms.com/docs/next-js/visual-editing) |
| **Payload** | Open source, TypeScript-native, self-hostable, drafts and comprehensive versioning | You own hosting, upgrades, operations, and more of the editorial experience. I’d choose it when data ownership or self-hosting is a primary requirement. [Versions](https://payloadcms.com/docs/versions/overview), [Live Preview](https://payloadcms.com/docs/live-preview) |

The one decision that could change my recommendation: if the content will soon become deeply structured and reused across several products or channels, I’d lean toward **Sanity**. For a marketer-operated website and landing-page workflow, **Storyblok** is my default.

Dla Next.js z naciskiem na samoobsługę marketingu i preview + wersjonowanie postawiłbym na **Sanity**: natywny Draft Mode i Presentation Tool (podgląd na żywo w Twoim froncie, bez osobnego stagingu), pełna historia wersji dokumentów, hojny darmowy tier i to najczęściej spotykana konfiguracja z Next.js/Vercel, więc dokumentacja i przykłady są dobre. Główny kompromis: treść żyje poza repo (vendor lock-in, brak PR-owego review contentu jak w git), a strukturę trzeba świadomie zaprojektować, żeby marketing nie musiał grzebać w polach technicznych.

Przed tym sprawdziłem jeszcze:
- **Storyblok** - mocniejszy, bardziej "WYSIWYG" wizualny edytor (klikanie bezpośrednio po stronie), dobry wybór jeśli marketing ma być totalnie samodzielny wizualnie; trochę słabszy DX przy złożonych, mocno typowanych schematach niż Sanity.
- **Contentful** - solidny, ale cięższy i droższy przy skalowaniu, czułem że to przerost formy nad treścią dla jednej strony głównej.
- **Payload CMS** - self-hosted, TypeScript-native, brak vendor lock-inu, ale to Ty utrzymujesz hosting/bazę, więc znika główny plus (zero ops po stronie marketingu).
- Podejście git-based (MDX w repo) odrzuciłem, bo nadal wymaga PR-a i deploya na każdą zmianę kopii, czyli nie rozwiązuje właśnie problemu, o który pytasz.

Do Next.js z self-service edycją treści, podglądem i wersjonowaniem: postawiłbym na **Sanity** - ma oficjalny toolkit pod Next.js (App Router, draft mode, real-time preview) i wersjonowanie/historię zmian wbudowane od ręki, a darmowy tier starczy na start.

Co jeszcze brałem pod uwagę: **Storyblok** (mocniejszy wizualny edytor WYSIWYG, bardziej przyjazny dla nietechnicznego marketingu, ale słabszy model danych), **Contentful** (dojrzały, ale drogi i cięższy do wdrożenia) oraz **Payload CMS** (self-hosted, pełna kontrola i własna baza, kosztem utrzymania infrastruktury) - odpadły głównie przez koszt/ops względem Sanity.

Chcesz, żebym rozwinął porównanie (np. koszty przy Waszej skali ruchu) albo od razu naszkicował integrację z obecnym repo?

Rekomendowałbym **Sanity** - ma najlepsze wsparcie dla Next.js (App Router, ISR, real-time preview przez Presentation Tool), natywne drafty i historię wersji, a marketing dostaje edytor WYSIWYG bez dotykania kodu. Główny kompromis: to zewnętrzny SaaS (koszt przy większym ruchu treści, dane poza waszą infrastrukturą) i wymaga zdefiniowania schematów treści w kodzie, co jest jednorazową robotą dla dev teamu.

Co jeszcze brałem pod uwagę:
- **Contentful** - podobny model, ale droższy przy skali i słabszy natywny preview w Next.js (trzeba więcej ręcznie spinać).
- **Storyblok** - bardzo mocny wizualny edytor "klocków", świetny dla marketingu, ale ciągnie content w stronę komponentowego modelu, co bywa sztywne przy prostych zmianach copy.
- **Payload CMS** - open source, self-hosted, zero vendor lock-in i pełna kontrola, ale to wy utrzymujecie infrastrukturę i auth, więc więcej roboty na starcie.
- **WordPress headless** - znajome dla marketingu, ale niepotrzebny bagaż (pluginy, bezpieczeństwo) jak na sam homepage copy.

Jeśli chcesz, mogę rozpisać plan integracji z waszym repo Next.js, ale najpierw powiedz: zależy wam bardziej na zerowym vendor lock-in, czy na tym, żeby marketing miał jak najwygodniejszy edytor?

Dla tego przypadku (Next.js, edycja przez marketing, preview + wersjonowanie) postawiłbym na **Sanity** - ma najlepszą integrację z Next.js (`next-sanity`, Presentation tool do live preview przez Draft Mode) i wbudowaną historię dokumentów/wersjonowanie z pudełka. Główny koszt: trzeba poświęcić czas na zdefiniowanie schematu i customowego Studio, a to osobny hostowany serwis, więc dochodzi zależność i koszt przy skali.

Przed tym patrzyłbym jeszcze na:
- **Storyblok** - bardziej "what you see is what you get" (visual editor z click-to-edit na realnym layoucie), marketing to zwykle lubi bardziej niż strukturalny edytor Sanity, ale elastyczność schematu i możliwości customizacji są słabsze.
- **Contentful** - dojrzały, mocny w większych organizacjach (role, workflow, compliance), ale droższy i preview trzeba spinać ręcznie.
- **Builder.io** - drag & drop page builder, świetny gdy marketing ma układać całe sekcje/layout, nie tylko podmieniać teksty, ale to już inny model (marketing zaczyna kontrolować layout, nie tylko treść), co część zespołów devowych traktuje jako ryzyko.

Jeśli priorytetem jest, żeby marketing mógł też przestawiać sekcje na stronie a nie tylko edytować teksty, wolałbym Storyblok albo Builder.io zamiast Sanity. Chcesz, żebym rozpisał konkretny plan wdrożenia dla któregoś z nich?

Dla Next.js z naciskiem na samodzielną edycję marketingu, preview i wersjonowanie postawiłbym na **Sanity** (Visual Editing/Presentation daje live preview wprost w App Routerze, natywny draft/publish i historia dokumentów, do tego elastyczny schema i rozsądny darmowy tier).

Po drodze porównywałem jeszcze: **Storyblok** (najbardziej marketer-friendly wizualny edytor, ale mocniej narzuca komponentową strukturę stron), **Contentful** (dojrzały, enterprise'owy, ale drożej i preview trzeba więcej ręcznie spinać) oraz **Payload** (self-hosted, pełna kontrola i zero vendor lock-in, kosztem własnego hostingu i utrzymania). Główny kompromis: Sanity vs Storyblok to głównie "elastyczność dla deweloperów" vs "łatwość dla marketingu przy edycji layoutu".

Jeśli chcesz, mogę rozpisać architekturę integracji (Draft Mode w Next.js, webhooki do rewalidacji ISR, uprawnienia dla zespołu marketingu).