Hello AEM Experts,
have a requirement related to MSM. Requirement is to have (en + few languages) for which we have translations happen using Smartling. The content (Text) will be same across all the languages however the assets might be different for different languages. Considering the requirement, I have 2 options
Option 1 – Similar to wknd / weretail
/language-masters
steps:
Issues:
Option 2 - Additional locale added
/language-masters
steps:
Issue:
Rollout - Standard Rollout configuration
Note: I understand we can use Custom Rollout configurations here but thinking if there is any OOTB approach
Just want to know your inputs on what’s the recommended approach to handle this requirement in the best way
Solved! Go to Solution.
Views
Replies
Total Likes
I understand the problem here, at this moment, I have a few solutions for you.
1. As Adobe always recommends of using modularity while authoring a page, if the image components are used instead of any custom component where the image is part of the custom component html, this wouldn't have been a problem as we can break the inheritance of only images not text. So try keeping your page as modular as possible and re use core components.
(I Know, it is hard to resist in creating a custom component)
2. Add new fields/tab to your component, where ever you expect to have locale based images – author them once at your en page and handle the value retrieving in your sling model by leveraging the OOTB context aware configurations (I would recommend this approach, as you might put lot of effort in creating your application specific components).
the solution here is to add only a few extra dialog fields, adding a util class which serves context aware configs, changes to your sling models, but trust me this is going to be a one time change. Also, authors can feel the ease in authoring just at the en level and need not to worry about the inheritance breaking.
I hope this idea helps,
I will come back and edit this answer, If I get another solution.
3. Custom Rollout configurations.
Thank you.
-Sravan
I understand the problem here, at this moment, I have a few solutions for you.
1. As Adobe always recommends of using modularity while authoring a page, if the image components are used instead of any custom component where the image is part of the custom component html, this wouldn't have been a problem as we can break the inheritance of only images not text. So try keeping your page as modular as possible and re use core components.
(I Know, it is hard to resist in creating a custom component)
2. Add new fields/tab to your component, where ever you expect to have locale based images – author them once at your en page and handle the value retrieving in your sling model by leveraging the OOTB context aware configurations (I would recommend this approach, as you might put lot of effort in creating your application specific components).
the solution here is to add only a few extra dialog fields, adding a util class which serves context aware configs, changes to your sling models, but trust me this is going to be a one time change. Also, authors can feel the ease in authoring just at the en level and need not to worry about the inheritance breaking.
I hope this idea helps,
I will come back and edit this answer, If I get another solution.
3. Custom Rollout configurations.
Thank you.
-Sravan
Views
Likes
Replies