Hi @Nick666 , It is an unrealistic requirement. It is not possible to convert PDFs into web pages. Until and unless you develop a special tool, based on computer vision technology to detect different component in pdf and convert it into HTML.

Hi @sachindey1231 , You can check the below documentation for react SPA for reference and give a try for vue. https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/spa-editor/react/integrate-spa.html?lang=en 

Hi @stefanjank , It seems the issue is with your CSS. Try to give max-height and check, Because in the 2nd screenshot rotate is working but the image is getting cropped. If possible then please share your CSS snippet?. So that I can try to reproduce it.

Hi @aniketp1012 , Could you please elaborate on your issue more clearly? and also attach output screenshots for better understanding.

Hi @AjayAkula , Check the below example. It will surely help you.https://github.com/hashimkhan786/aem-groovy-scripts/blob/master/modifyProperties.groovy

Hi @rangavinod , It seems in the fragment configuration is not enabled for the folder in which you are trying to create the content fragment. That's why the model from the child configuration is now showing. Go to your asset select your folderopen that folder's propertiesselect the cloud configurati...

Hi @arunpatidar , This is a live copy. You can check the source. It is pointing to the master copy. 

Hi @bhagchand , Have you checked this official documentation ?https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-cloud-manager/managing-code/working-with-multiple-source-git-repositories.html?lang=en 

Hi @nikita24tailor , I had a similar requirement, Fetching page properties data in the sling model for further processing and the below solution worked for me.https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/fetch-page-properties-in-sling-model/td-p/321017 

Hi @nave_27 , If it is working in on-premise versions and not on the cloud then it is a bug. You can raise an adobe support ticket or simply extend the component. Hide the existing field for alt text and add a new field explicitly for the same.