Manual setup
Numbered checklist to wire Nexus CMS into a Next.js App Router project.
Manual setup
No architecture essay — run these in order.
1. npm i nexus-cms
# or: npm i @nexus-cms/nextjs @nexus-cms/cli
2. npx nexus init
3. Wrap next.config with withNexus from nexus-cms/config
# or: @nexus-cms/nextjs/config
4. npx nexus generate
5. Import Providers from app/providers (created by init) in layout.tsx
6. Wrap layout {children} with <Providers>
7. Local dogfood: init uses createMemoryAdapter — open /?edit=1
8. Production: switch backend.adapter + createHttpAdapter (or Laravel)
9. npx nexus doctor && npx nexus check --ciChoices
| Choice | When |
|---|---|
Dedicated providers.tsx | Always (client boundary for overlay) |
| Memory adapter | Local / alpha UI pass |
| HTTP / Laravel adapter | Real content + publish |
Exclude header/footer in nexus.config | Dual-state sticky chrome until @cms-nav / auto header is enough |
@cms-ignore on particles / SVG ornaments | Always |
| Lift copy out of ignored trees | Only if ignore traps marketing strings (nexus doctor warns) |
Pro license key (NEXT_PUBLIC_NEXUS_LICENSE_KEY) | Versions, locales, collection add/remove |
Verify
npx nexus generatewrites.nexus/cms-schema.json- Dev server starts without transform errors
/?edit=1shows hit targets on marketing copy- Sticky header still looks like the live viewport (not twin logos)
- Excluded footer does not paint dead hits