Experience fragment on a page without including its css and js files | Community
Skip to main content
anelem1760873
anelem1760873
Level 4
Mar 19, 2021 7:47 AM UTC
Solved

Experience fragment on a page without including its css and js files

Hi there,

is the a way in AEM we can include an experience fragment on a page without including its css and js files, using HTL
Something like this, is there any argument to pass to ignore/exlude css and js file on this.

<sly data-sly-resource="${ @ path="experiencefragmentPathHere", resourceType='wcm/foundation/components/parsys', wcmmode='disabled', decoration='false' }"></sly>

 Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Umesh_Thakur
Umesh_ThakurAccepted solution
New Participant
Mar 19, 2021 9:38 AM UTC

We had similar kind of requirement, so we had created two xf structure component and so two template one with and another without clientlibs.

We were using without clientlib XF, to create a experince fragment to be embeded on the page where we allready have all the client libs to generate the look and feel for the experience fragment.

And with clintlibs to create experience fragment, where we were using experience fragment stand alone.

 

So you can take that approach to handle to scenario.

 

If you don't have that option available you can take help from template policy to include or exclude a client libs based on there category.

 

Hope this will help.

Umesh Thakur

 

View reply

2 replies

arunpatidar
arunpatidar
New Participant
Mar 19, 2021 11:12 AM UTC

Hi, can you try with content selector?

Translate
Arun Patidar
    Umesh_Thakur
    Umesh_ThakurAccepted solution
    New Participant
    Mar 19, 2021 9:38 AM UTC

    We had similar kind of requirement, so we had created two xf structure component and so two template one with and another without clientlibs.

    We were using without clientlib XF, to create a experince fragment to be embeded on the page where we allready have all the client libs to generate the look and feel for the experience fragment.

    And with clintlibs to create experience fragment, where we were using experience fragment stand alone.

     

    So you can take that approach to handle to scenario.

     

    If you don't have that option available you can take help from template policy to include or exclude a client libs based on there category.

     

    Hope this will help.

    Umesh Thakur

     

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...