Expand my Community achievements bar.

SOLVED

AEMasCS Preview Instance Vs Author preview

Avatar

Level 4

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. 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@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

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/sites/authoring/fun...

 

View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor

@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

 

https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/sites/authoring/fun...

 

Avatar

Level 5

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.