Start using Next.XP in existing project

thanks tsi. Yes we are trying to let the user choose to render preview in content studio with enonic or nextjs. We try to do this with a checkbox. That is also why I am wondering when you will release the builtin functionality to do this.

”you may not support live component updates both in Next.js and Site engine at the same time, within the same site.” How would we do live update only in Next.js, but still let the user choose if rendering is done in Site engine or Nextjs? Without the filter all rendering is done with Next.js, which is not what we want. At least not yet. For now we need to let the user choose. If we can not do live udpates in both Site engine and Nextjs at the same time, we could live with live updates only for nextjs.

Generally - by keeping the component mapping you should be able to have a working live update for a Next rendered page, but editing components in a regular page will then require a page refresh.

In terms of releases, our general plan, and rough estimat is

  • Content Studio 5.4 (with pluggable preview) - This fall
  • Add support for Next 15 - This fall?
  • Update Next integration to support pluggable preview - 2025

As the two latter projects have not yet been started, we do not know the exact scope or planned release, but both are of high priority.