-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Next.js] Introduce nextjs-xmcloud
Initializer Template
#1653
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…emplate (driven by prompt / --xmcloud CLI option)
…(GraphQLSiteInfoService)
...ges/create-sitecore-jss/src/templates/nextjs-xmcloud/scripts/config/plugins/edge-platform.ts
Outdated
Show resolved
Hide resolved
illiakovalenko
approved these changes
Nov 7, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! 👍 See only one comment below that we discussed
7 tasks
art-alexeyenko
pushed a commit
that referenced
this pull request
Nov 8, 2023
* rename nextjs-personalize -> nextjs-xmcloud. move feaas and BYOC here. * Move Sitecore Edge Platform / conext related items to nextjs-xmcloud * Repurpose nextjs-personalize -> nextjs-xmcloud initializer "system" template (driven by prompt / --xmcloud CLI option) * Moved skipping of site information fetch on XM Cloud to base package (GraphQLSiteInfoService) * CHANGELOG update * fix scaffold samples * removed <BYOC/> from sxa Layout.tsx * fix for PR comment (cherry picked from commit 19f5c22)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description / Motivation
Introduced a
nextjs-xmcloud
initializer “system” template which will contain all XM Cloud base features, including Personalize, FEaaS, BYOC, Edge Proxy and Context support. Moved everything related to these features fromnextjs
base template tonextjs-xmcloud
. This keeps the basenextjs
template free of XM Cloud-only artifacts for SXP.Note: this replaces the previous
nextjs-personalize
template.The following changes are made to the JSS initializer (
create-sitecore-jss
) flow:nextjs
is the selected framework, a new prompt shows:nextjs-xmcloud
is added to template listnextjs-styleguide
(SXP and XMC)nextjs-styleguide-tracking
(SXP)nextjs-sxa
(SXP and XMC)nextjs-multisite
(SXP and XMC)-xmcloud
to control prompt via CLIThis PR also includes a follow-up to #1649, moving the skipping of site information fetch on XM Cloud to the
GraphQLSiteInfoService
.Testing Details
Types of changes