Weave Code
Statamic Nextjs Laravel Package
morethingsdigital/statamic-nextjs
A Statamic addon that connects your CMS to Next.js, exposing content through a headless API so your frontend can fetch and render Statamic entries, with support for previews and revalidation workflows.
At a glance
Frequently asked questions about Statamic Nextjs
- What does the morethingsdigital/statamic-nextjs addon do?
- It is a Statamic addon that connects your Statamic CMS backend to a Next.js frontend. It exposes content through a headless API so the Next.js app can fetch and render Statamic entries, and it supports preview and revalidation workflows. Structurally it is a conventional Laravel service provider that registers a config file and a view namespace inside your existing Laravel application, so it adds no separate runtime or deployment unit.
- How do I install statamic-nextjs with Composer?
- Require it in your Laravel and Statamic application with composer require morethingsdigital/statamic-nextjs. Statamic addons are Laravel service providers that are auto-discovered, so registration happens through the package provider rather than manual wiring in config/app.php. After installation, publish and edit the package config file to point the addon at your Next.js frontend and any preview or revalidation endpoints. Pin an exact version in composer.json, because the package is pre-1.0 and patch releases may change behaviour without a migration guide.
- Which Statamic, Laravel and PHP versions does statamic-nextjs support?
- The published assessment does not confirm the exact constraints, so read the require block in the package's composer.json before adopting it. Alpha addons typically declare a minimum Statamic and Laravel version rather than testing a broad compatibility matrix. Confirm the declared constraints match the Statamic, Laravel and PHP versions you actually run, and check whether CI tests against them. If there is no tested matrix, add your own smoke tests around the API responses.
- Is statamic-nextjs production ready?
- It is currently at v0.0.2-alpha, which is pre-1.0 and carries no semver stability guarantee. The design is sound, since it is a thin, Laravel-native addon sitting between Statamic and Next.js rather than a parallel runtime, but the dominant risk is maturity rather than architecture. Treat it as suitable for pilots and internal projects until the content delivery and preview contracts settle. Expect that any patch release could alter public behaviour.
- How do previews work between Statamic and Next.js with this addon?
- The addon is designed to support preview workflows so editors working in the Statamic Control Panel can see draft or unpublished content rendered by the Next.js frontend. The exact preview contract, including token handling and the draft-content route, is still unsettled at this alpha stage. Read the addon's routes, controllers and config file to confirm the request flow before you rely on it in an editorial workflow. Test the preview path end to end against a staging Next.js deployment.
- How does revalidation work with Next.js and Statamic?
- The addon supports revalidation workflows, typically by notifying your Next.js app when Statamic content changes so cached pages can be regenerated on demand. In practice you configure an endpoint, usually in the addon's config file, that points at the revalidation route your Next.js app exposes. Because the package is alpha, verify the payload shape and any signing or secret handling directly in the source. Do not assume the contract is frozen across releases.
- Can I override the addon's Blade views without forking it?
- Yes. The addon registers its views under a namespace, so package-provided Blade templates can be overridden from your host application without vendor patching. That also removes the risk of view-name collisions with your app or other addons. Whether you want to override them depends on what they contain, such as Control Panel screens, frontend templates, or preview and error views, so inspect them first. Overriding is generally preferable to forking a young package.
- Is statamic-nextjs actively maintained and tested?
- The package is published under an agency namespace at a 0.0.2-alpha version with a single-bullet release note, so maintainer bandwidth and long-term stewardship are unproven. Automated compatibility testing against your Statamic and Laravel versions is not confirmed, and alpha packages often ship without a tested version matrix. Check the repository for a test suite, a CI workflow file, and recent commit activity. Clarify the support model up front, whether that is GitHub issues only, best-effort help, or paid support through the agency.
- How do I configure the statamic-nextjs addon?
- Configuration lives in the config file the package's service provider registers, which is where you point the addon at your Next.js frontend and set up preview and revalidation options. The assessment describes the integration surface as limited to provider registration, a config file, and a view namespace, so there is no separate runtime to configure. Publish the config into your application and keep environment-specific values such as frontend URLs and secrets in your .env file. Version-control the published config so changes are reviewable.
- What are the alternatives to statamic-nextjs?
- The main alternatives are Statamic's built-in REST API, the Statamic GraphQL addon, or a small custom controller in your own Laravel app that shapes entries for Next.js. Those options leave the HTTP contract entirely under your control, at the cost of writing the preview and revalidation glue yourself. This addon's value is packaging that glue into a Laravel-native addon, but it does so at an alpha maturity level. If you need a frozen, versioned API contract today, the built-in or custom route approach is easier to reason about.
Weaver
How can I help you explore Laravel packages today?