Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Expose AEM Page as a service

josephbuluran
Level 1
Level 1

Hello Community.

 

I want to get your thoughts, or you might know a similar solution to expose our current AEM pages or at least some elements/components to other applications. We know of content fragments, and experience fragments can do the trick. However, is there any implementation, solution, or plugin/s we might use to expose the page or an experience fragment as is (with HTML/CSS/JS elements and functions in it)? It is like making the page an iframe to another web application consumer smarter and more securely.

1 Accepted Solution
Shashi_Mulugu
Correct answer by
Community Advisor
Community Advisor

@josephbuluran if you want to expose AEM page with intact AEM rendered html, you can directly share the AEM Page URL (via Dispatcher) to other teams which will have complete AEM page with CSS, JS, header, body and footer HTML. If you want to share any specific component in AEM to outside, you will not get the CSS, JS which will be from template but the you can expose RAW component html.

 

https://wknd.site/us/en.html

https://wknd.site/us/en/jcr:content/root.html

https://wknd.site/us/en/jcr:content/root/container.html

https://wknd.site/us/en/jcr:content/root/container/teaser.html

 

View solution in original post

1 Reply
Shashi_Mulugu
Correct answer by
Community Advisor
Community Advisor

@josephbuluran if you want to expose AEM page with intact AEM rendered html, you can directly share the AEM Page URL (via Dispatcher) to other teams which will have complete AEM page with CSS, JS, header, body and footer HTML. If you want to share any specific component in AEM to outside, you will not get the CSS, JS which will be from template but the you can expose RAW component html.

 

https://wknd.site/us/en.html

https://wknd.site/us/en/jcr:content/root.html

https://wknd.site/us/en/jcr:content/root/container.html

https://wknd.site/us/en/jcr:content/root/container/teaser.html

 

View solution in original post