Hello @monish7 ,Two things I will suggest-   1. Make sure you set the allowproxy in clientlib, (allowProxy="{Boolean}true")  <?xml version="1.0" encoding="UTF-8"?><jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" jcr:primaryType="cq:ClientLibraryFold...

Hello @ssharma48 , QueryBuilder is the tool for searching and filtering content in AEM, you may need to combine it with custom Java code that involves date calculations. This is because QueryBuilder is primarily designed for selecting nodes based on their properties and structure, not for performing...

Hello @ayush_agarwal , You can check this process: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-blogs/seamless-integration-of-vue-js-in-aem-project-a-step-by-step/ba-p/615179 Github Project: https://github.com/SadyRifat/aem-vue/tree/webpack-build-with-typescript  In this...

Then if possible, please share the error, it will be more helpful to solve it.

Hello @aem101 , The categories property allows you to group client libraries into categories. Categories can be used to include multiple client libraries at once by specifying the category name. This is useful when you want to load related libraries together. In summary, this will merge the same cat...

Hello @aem101 , To manage clientlib you can follow these tips: Define your component clientlib with category, exactly the definition of the component categoryFor a higher environment, build it in a minified format.Load clientlib in gzip encoded format, which will reduce your file sizeAvoid creating ...

Hello @test566, You can check this article, where it will meet your requirements: https://exadel.com/news/aem-experience-fragments-consuming-outside-aem/  From the external source, you can add it via, <div>External Content</div> <script src="http://localhost:4502/content/experience-fragments...

Hello @Aaron_Dempwolff ,You can not directly extend the ContainerImpl in your Java class. You can follow the Sling Delegation Pattern where you need to extend the Interface first then Implement your interface.In the implementation, you just need to @Self annotation that will let your core implementa...

Hello @keshava219 ,You can try this script,In your clientlib JS, (function($) { $(document).on("foundation-contentloaded", function(e) { console.log("Hello"); $(".coral-Form-field.coral3-Multifield").each(function() { let $multifield = $(this); let $fields...

Now it is totally understandable, But I think you can simplify the Author's Dialog and make it easier,Just put the "Custom CSS Class" field into the first tab multifield. No Need for additional validationLess error proneNo extra complex code