fix(angular): point JP sample targets to the EN source#375
Merged
Conversation
The JP docs loaded live samples from a separate JP demos deploy (jp.*.infragistics.com/angular-demos) that just duplicated the EN one. Point the JP demo/sample base URLs (demos, dv, lob) at the EN host (staging/www.infragistics.com) so JP consumes the English samples and the duplicate JP deploy can be retired.
Zneeky
force-pushed
the
aahmedov/angular-jp-samples-en-source
branch
from
3d5fe5c to
a7d8477
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Angular JP docs environment configuration so that JP pages load live demo/sample content from the English (EN) demo hosts instead of the duplicate jp.* Angular demos deployments, reducing maintenance and infrastructure duplication.
Changes:
- Repoint JP
stagingdemo/sample base URLs fromjp.staging.infragistics.com/angular-demos*tostaging.infragistics.com/angular-demos*. - Repoint JP
productiondemo/sample base URLs fromjp.infragistics.com/angular-demos*towww.infragistics.com/angular-demos*. - Leave
development(localhost) and non-sample JP-specific URLs (e.g.,infragisticsBaseUrl,sassApiUrl, GTM IDs) unchanged.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
ChronosSF
approved these changes
Jun 30, 2026
This file contains hidden or 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
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.
Closes #364
Summary
Switch the Angular JP sample targets to load from the English source instead of a separate JP demos deploy.
The JP docs were loading live samples from
jp.*.infragistics.com/angular-demos, a second sample source that just duplicates the EN one. That adds unneeded maintenance/infra complexity. This points the JP demo base URLs at the EN host so JP consumes the English samples directly, allowing the duplicate JP demos deploy to be retired.Changes
docs/angular/src/content/jp/environment.json— repoint the demo/sample base URLs (demosBaseUrl,dvDemosBaseUrl,lobDemosBaseUrl) for thestagingandproductionblocks from thejp.host to the EN host:jp.staging.infragistics.com/angular-demos*→staging.infragistics.com/angular-demos*jp.infragistics.com/angular-demos*→www.infragistics.com/angular-demos*crmDemoBaseUrlanddvApiBaseUrlalready pointed at the EN host (no change needed); the JP demo URLs now match EN exactly.developmentblock (localhost) and non-sample JP keys (infragisticsBaseUrl,sassApiUrl,GTMContainerId) are intentionally left untouched.Verification
jp.*/angular-demosreferences in the JP content.https://staging.infragistics.com/angular-demos/grid/grid-rowStyles-sample(previouslyjp.staging.infragistics.com/...). Sample paths are unchanged, so existing sample references still resolve.