The Next.js App Router introduces a fundamentally different way to build applications.

One that emphasizes layouts, colocation, and composability.

With Sitecore JSS, adopting the App Router was difficult due to deep assumptions about routing and rendering. The Sitecore Content SDK removes those constraints entirely.

App Router Without Compromise

Using the Content SDK, your project structure looks like a standard Next.js app:

• app
  • layout.tsx
    • page.tsx

There’s no page factory, no route hijacking, and no generated files controlling rendering.

Native Next.js and Sitecore Side by side

Because Content SDK follow the same structure as native Next.js, you can mix and match static pages, Sitecore pages, and even pages from another system entirely in the same way.

• [app]
  • [site]
    • [locale]
      • [...path]
  • layout.tsx (layout for sitcore)
  • (externl path)
    • layout.tsx (custom layout)
      • about-us
        • page.tsx (custom page, no sitecore)

This allows for cleaner code organization, faster development, and greater flexibility.

Looking for more information or help migrating you're existing Sitecore JSS site to Content SDK? Reach out to experts like my colleagues and I at XCentium.