Same dev env for both sites as you probably won't change each site it should be quite similar.
You can use two different pipelines for your deployment to each region. It will be one after the other if you are using the same solution and dev env but after that you should be good to go.
For the changes you have to make you got two different options.
You can either fetch the URL for client site changes if it just needs to be some words, layout, designs etc. or you could setup an environment variable.
Fetch that one inside your header via a FetchXML server side and just render what you want to render for the specific region.
In case you need to call different APIs etc. for UAT,Prod or/and each region, you could also use the envvar and fetch specific webfiles/content snippets to get access to these.
Just be really sure that you are deploying all components and dependencies. Otherwise you will face some issues in the long term if you are going to create anything manual in any other env than your dev.
Hope that helps.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
8
Share
Report
All responses (
Answers (
