Hot answers tagged

5

This depends entirely on your requirements. Separate applications would enable you to develop, deploy, and scale sites independently. Components and other code could be shared via npm packages. A shared, multi-site application could save cost via easier deployment and less infrastructure. Next.js can now support multi-site applications in the same "...


1

The sc_site parameter getting constructed using "siteName" parameter which we can set in RestLayoutService and RestDictionaryService. These two are getting initialize in SitecorePagePropsFactory ( if you are using basic_company next.js example) For standalone app which created using cli these two services getting set in layout-service-factory.ts ...


1

With Next.js, running a build will trigger a production build, which requires a service to communicate with first. The build target by default then needs a running Sitecore instance configured in the scjssconfig.json. What you want instead likely is npm run start, which will start the disconnected/mock Sitecore service and run Next.js in development mode ...


1

Welcome to Sitecore Stack Exchange. I wouldn't recommend trying to install unsupported JSS version, even if you succeed on making it work if you find any issues related to the module you won't be able to get official help for example from sitecore support. Depending on your current website installation (mostly if you need to migrate xDb data) I would rather ...


Only top voted, non community-wiki answers of a minimum length are eligible