Next.js CMS

A CMS built for Next.js sites

A CMS for Next.js gives your team a place to write and edit content, while the app fetches it on the server. BetterCMS does this with a first-party App Router adapter: your team edits on the real page, and a publish can refresh just the pages that changed.

How BetterCMS works with Next.js

Your team publishes in BetterCMS. Next.js refreshes only the pages that changed, without a full rebuild.

  1. Your team edits

    Marketers change copy and sections in BetterCMS, then publish.

  2. Publish sends a webhook

    A small route in your app receives it and clears the matching cache tag.

  3. Next.js re-fetches

    Server components read the fresh content through the adapter. No rebuild.

  4. Visitors see the update

    The refreshed page is cached again and served to everyone.

Choose how each page renders

  • Static

    Rendered at build time and served from the edge.

  • Revalidated

    Rendered once, then refreshed on a timer or when its cache tag is cleared.

  • Draft mode

    Reviewers see unpublished work on the real page, read from the server.

Marketing pages without a deploy

Marketing pages change every week, and the people who write them work outside the codebase. A deploy for every headline slows both teams down.

With BetterCMS, marketers edit on the rendered Next.js page and publish. Developers keep the components and the code review.

  • Edit in place. Copy and sections, on the real page.
  • Review and schedule. An approver and a named go-live time.
  • Typed fields. Each section maps to a React component with props.

Next.js CMS or a database?

Keep application data, like users, orders and settings, in your database.

Content that people write and review needs more than storage: an editor, drafts, roles, version history and an audit trail. That is the part a CMS adds, and the part that takes months to build.

When not to add a CMS

A Next.js app can hold its content in several places. A CMS is the right one less often than vendors suggest.

Use something else

4 points
  • Application data Users, orders and settings belong in the app database, not in a CMS.
  • Copy that ships with the code Button labels and error strings are best kept beside the components.
  • A five-page site MDX in the repository is less to run and less to pay for.
  • Anything personalised per user A delivery API is cached and public. Per-user content is not content.

Reach for a CMS

4 points
  • Marketing pages on an app domain Pages that change weekly and are written by people outside the codebase.
  • A large set of similar records Posts, case studies and product pages that share one shape.
  • Review and scheduling Someone must approve, and a page has to go live at a named time.
  • More than one front end A site, an app and a partner feed reading the same records.

The developer part is short

Read content in a server component, so the key stays on the server. Tag the read, and a publish can refresh just this page.

From the published @bettercms-ai/next adapter, for Next 14 or later. Install it with npm install @bettercms-ai/next.

app/blog/[slug]/page.tsx
import { cms } from '@/lib/cms';
import Article from '@/components/article';

export default async function Page({ params }: { params: { slug: string } }) {
  const entry = await cms.getEntry<{ title: string }>(params.slug, {
    tags: [`post:${params.slug}`],
  });

  return <Article entry={entry} />;
}

Next.js CMS questions

What comes up when wiring content into the App Router.

  • The best CMS for a Next.js app is a headless or hybrid one that returns structured fields rather than rendered HTML, issues a key the server can hold, has a draft mode for review, and exposes cache tags so a publish can clear one page instead of a whole route.

  • No. Next.js is a React framework and includes no content storage or editing interface. It supports MDX files in the repository, and everything beyond that comes from an external CMS or a database.

  • In an async server component, or in a route handler when the result is shared. Fetching in a client component would expose the API key in the browser bundle and would move the request onto the visitor’s connection.

  • Turn on Next.js draft mode from a route that the CMS links to, and read unpublished content inside that mode. The credentials for it stay server-side, so nothing about them reaches the browser.

  • Give each read a cache tag, then clear that tag when the content behind it is published. A timed revalidation is a fallback, not a plan: an editor who published two minutes ago should not have to wait for a timer.

  • If it is application data, yes. If it is content that people write and review, a database gives you storage and nothing else. The editor, the drafts, the roles, the version history and the audit trail are the parts that take months to build.

Your next website starts here

See BetterCMS running on your pages, not on a sample site.