Fix cross-site build errors by filtering allowed sites for static params #198
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
This PR fixes a critical build error that occurred during Vercel deployments when multiple XM Cloud sites share the same instance.
Root Cause
During static site generation (SSG), the generateStaticParams function was attempting to prerender pages for ALL sites in the XM Cloud instance, not just the site being deployed. For example, when deploying the SYNC site, it would incorrectly attempt to prerender pages from the Alaris site, causing build failures.
Solution
Modified the generateStaticParams function across all example starters to filter sites based on the defaultSite configuration in sitecore.config. The implementation now:
This ensures each starter only generates static params for pages that belong to its designated site, preventing cross-site build errors when multiple starters share the same XM Cloud instance.
Testing Details
Testing Performed:
Verified successful Vercel deployments for individual starters in a shared XM Cloud environment
Confirmed static params generation only includes pages from the configured defaultSite