Skip to main content
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

7 replies

Ravi_Pampana
Ravi_Pampana
New Participant
November 10, 2018

Hi,

You can add clientlibs folder under each component and add category name to clientlibs folder like below

categories="[componentspecificname]"

Add the clientlibs inside component jsp/html

JSP:

<cq:includeClientLib categories="categoryname" /> -- This includes both js/css files

<cq:includeClientLib js="categoryname"/> -- To include only js

<cq:includeClientLib css="categoryname"/> -- To include only css

Sightly:

HTL and ClientLibs

This will include multiple js/css files on the page as each component will include a js/css files. Also, if clientlibs are added in /apps user everyone should have read access of /apps for files to load in publisher or clientlibs needs to create under /etc/designs

    ariellea4070516
    ariellea4070516Author
    New Participant
    November 10, 2018

    I thought ‘cq’ was deprecated since AEM 5.3. Shouldn’t we be using ui now?

      ariellea4070516
      ariellea4070516Author
      New Participant
      November 13, 2018

      Also, this solution injects clientlibs in the body of the page, which defeats the purpose of a component-based architecture (increasing the performance of an app) by forcing the client to re-render the page. And adding <link .. /> to the body is invalid, 'link' tags should only be added in the head of a document.

        smacdonald2008
        smacdonald2008
        New Participant
        November 9, 2018

        You can call a clientlib from a specific component.

          ariellea4070516
          ariellea4070516Author
          New Participant
          November 9, 2018

          So using ui:includeClientLib then? Ok, I'll need to find a way to rewrite the src's and href's because that approach exposes the internal structure of the application.

            Terms & ConditionsAccessibility statement

            Loading footer...