Thank you @Ganthimathi_R for the suggestion. We also thought about doing the rollout first but we were not sure if it will be the recommended way or we should handle it in different way.Your comment had added more weight on this approach. Thank you. This forum has always been very helpful in providi...

Looking for best adobe practices and recommendations.   1. We have pages in en-us with the live copies maintained in locales eg es-es.   2. We add a component in en-us and do the rollout which makes the component available in the live copy locale es-es with cq:LiveRelationship property.3. We submit ...

Thank you @edubey  It resolved my issue. I was not using the format and was forming the path as ${'item'$itemList.counter}

We also found the issues in the code where multiple loops where doing rollout several times.

Hi rush_pawan - We are not overriding any blueprints. All those blueprints are independent and separate and created for block of content/pages.We dont have custom implementation for creating the blueprint, but it seems we have so many blueprints as that is our need, rollout performance is getting af...

Moving the blueprints from /etc/blueprints to /apps/msm had no impact in the performance. I had deleted the /etc/blueprints folder after moving the blueprints.

We have implemented a custom rollout by using the OOTB RolloutManager's rollout functionality and passing the required attributes.We have basically used what we have for we.retail and implemented language masters and live copy implementation for about 10 different languages. In local env rollout wor...

Thank you. I had the same issue.

Thank you for the response. I will take reference component or content fragment into the consideration.

We are following we.retail example and we have the language copy containing the master (blueprint) for live copies (language branch).language-masters/en is the blueprint for live copy - en,language-masters/fr is the blueprint for live copy - fr, Our requirement is that if we have any image (static c...