Experience fragment best practice
In order to use Experience fragments on AEM pages, we have created an experience fragment under(/content/experience-fragments/abc/language-master/en) and used on pages(/content/abc/language-master/en).
Once rollout the page(/content/abc/language-master/en), the same language-master-XF is being rolled out to live-copy pages as well. So that all the links used in XF are language-master links even in live-copy domains.(This is creating an issue)
To avoid this issue, we have created a custom rollout configuration. Once we use this configuration on rollout, all the reference links gets updated to respective live-copy links in live-copy XF.
If we use language-master-XF on language-master page and rollout that page to a live-copy page, same language-master-XF is present on live-copy page as well.(This is creating another issue)
To Avoid this issue, we are breaking the inheritance of that particular component on live-copy page and updating language-master-XF link(/content/experience-fragments/abc/language-master/en) to live-copy-XF link(/content/experience-fragments/abc/india/en), then this issue gets resolved here.
However, we do not want to break the inheritance and change the link from language-master-XF link to live-copy-XF link in all the live-copy pages(18 live-copies available for my site). Is there any other way? (or) is this the best practice?
Thanks in Advance.!
