Hello Team,
I am looking for details around the benefits of using AEMasCS Preview instance against the Author Preview mode. what are the advantages that we get which is not there in author preview/disabled mode.
Solved! Go to Solution.
Views
Replies
Total Likes
@pradeepmoolemane We have lot of advantages using AEMaacs preview.
let’s say for example if u want to preview the content with out publishing and with out onboarding people to AEM
we can use the preview url and share it with the users. Follow the purpose of author preview in AEMaacs from below link
@pradeepmoolemane We have lot of advantages using AEMaacs preview.
let’s say for example if u want to preview the content with out publishing and with out onboarding people to AEM
we can use the preview url and share it with the users. Follow the purpose of author preview in AEMaacs from below link
As we already know that Author preview mode is just to check whether styles and authored content is working as expected before publishing.
However we have some funtionalities that requires publish instances such as end user login or securing pages etc.,
If you want to verify those type of specific functionlaities which requires publish environment those can be done using the preview environment.
This is one of the uses of using preview, we can also use this for content validation by the content approvers, design validations by UX team and finalize everything in preview instead of publishing them directly.
Hope this is helpful.