Strapi Next.js Starter version 3.4.0: Built for Humans, AI, and Production Scale

It's easy to spin up your own starter template, but the real challenge starts on day two. When you go live, you hit the hard realities of enterprise operations: managing many pages and their content, updating the frontend cache with page changes, and redeploying code just because marketing needed a simple path redirect. That is why we built the Strapi + Next.js Monorepo Starter - to handle these operational challenges out of the box.

At NOTUM, we build and maintain high-traffic digital platforms for brands like Scenic and Axi. In our version 3.4.0 release of the Strapi + Next.js Monorepo Starter, we have backported the core components of our enterprise architecture to solve these exact friction points.

Here is what we shipped to move the starter from a development boilerplate to a hardened production foundation.

Accessible Development: Docs and Onboarding for Developers and AI Agents

For a headless CMS starter to be truly production-ready, it must be easy to understand, navigate, and modify. We have bridged this gap by making the repository fully accessible to both human developers and the AI coding agents that assist them. With the release of version 3.4.0, we have optimized our workflow templates to make onboarding seamless, whether you are coding by hand or co-authoring with an LLM.

A Documentation Site That Removes the Guesswork

We've launched a comprehensive documentation site, designed to remove the guesswork from page building & rendering, proxies, deployments, and internationalization (https://strapinextjs.docs.notum.tech). The site provides a complete roadmap of the monorepo architecture:

• Interactive Search: Quickly locate commands, components, and configuration files.
• Mermaid Workflow Diagrams: Clear visual representations of page builder lifecycles and cache paths.
• Component Registry Guides: Step-by-step documentation on how Strapi dynamic zones map to Next.js components.
• Development Cycle: Best practices including Git hooks, conventions, and Strapi types.
• Authentication: Guidelines and flows for secure user access.
• Design System: Integration details for UI components and styling.

Built-in Agent Skills for AI-first Development

Modern development is increasingly collaborative, involving autonomous AI agents working in parallel. Version 3.4.0 introduces native configurations to leverage these tools effectively:

• Pre-Configured Agent Skills: Built-in repository instructions (supporting .claude and .agents configurations) that teach AI agents exactly how the project is structured. This prevents hallucinations when writing schemas or page builder components.
• Git Worktree Scripts Toolkit: A custom script collection designed to spin up isolated, parallel workspace folders. Developers and AI subagents can work on separate feature branches simultaneously without duplicating node_modules or causing database conflicts.

Hardened Security: Enterprise-Grade Guardrails

Security and verification are core requirements for enterprise environments. In version 3.4.0, we have introduced several features to isolate environments and protect administrative services:

• Runtime Security Headers: Full support for Content Security Policy (CSP), HSTS, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy headers.
• Secure Preview Framing: A new preview framing system using secure cookies. This allows Strapi to safely iframe the frontend for inline editing (matching the STRAPI_URL frame-ancestors rule) while keeping the admin server's URL hidden from the public.
• Sitemap Gating: To prevent search engine crawlers from indexing development or staging sites, /sitemap.xml is now hidden behind ?allow-sitemap=yes in non-production environments.
• Dockerized Playwright Tests: E2E visual regression tests are now fully containerized in Docker for both local runs and CI. This guarantees a consistent rendering baseline, eliminating host-system layout discrepancies.

Production Performance: Deep Monorepo Upgrades

Beyond documentation and security, version 3.4.0 brings significant architectural upgrades designed to improve performance, caching, and observability under heavy production traffic.

• Automated Cache Revalidation: We built a custom document middleware in Strapi that triggers tag-based revalidation in Next.js when content changes. Editors can also trigger manual CDN purges (integrated with Azure FrontDoor) via a custom widget in the Strapi Admin panel.
• Structured Logging with OpenTelemetry: We replaced standard console.* outputs with @repo/logging - a unified logging package using Pino and OpenTelemetry. It correlates traces between the Strapi backend and Next.js frontend, automatically redacting sensitive tokens and database secrets. It also supports telemetry backends like Azure Application Insights.
• Zero-Deploy Redirects: Marketing redirects can now be defined directly inside the Strapi Redirects collection. Next.js applies them instantly at the proxy layer with no code changes or redeploys, leveraging a 2-minute in-memory cache and stale-while-refresh logic.
• Page Hierarchy Management: The new Hierarchy single type recalculates the fullPath of your pages on-demand when URL structures change, automatically generating the necessary redirects.

Upgrade Path and Repository Links

If you are already running our starter, you can pull the latest features via git cherry-pick. If you encounter conflicts, you can leverage AI - the starter is fully optimized to support it!

If you find this project valuable, please consider starring our repository on GitHub:

• ⭐ Strapi Next Monorepo Starter (GitHub)

Explore more resources:

• 📖 Full Documentation: Use the built-in search to locate code examples or configuration steps in seconds (optimized for both human developers and AI context loaders).
• 🚀 Live Demo: Explore the application in action.
• 💬 Enterprise Architecture Team: Book a session to discuss your project structure.

‍