Hi @RahulSi13  every time a new deployment happens the unique hash with the clientlibs gets changedetc.clientlibs/myproject/clientlibs/clientlib-site.lc-<unique_hash>-lc.min.js So whenever new HTML is being rendered, it will have the new hash of the clientlibs and the browser won't be calling the ol...

try using MS Word for the same scenario as I think in the notepad/vscode(can be due to some encoding) it already comes up as hard space and copying and pasting just promotes to AEM author as well as when I couldn't replicate the issue with the same steps mentioned by you.

Hi @Kalyan_ChakravarthyCh  Please use AssetManager API instead of directly targeting the original/jcr:content of the AssetYou can use createOrUpdateAsset method to update the JSON file in the rendition folder.

Hi @nj2  1. Is there any way to retain JSP as-is and still migrate from static template to editable template?no, editable templates will require HTL and new code and JSPs are not recommended at all now and best would be to migrate to HTL2. Is it necessary to migrate JSP to HTLAEM officially supports...

Hi @RahulSi13  Ideally, it shouldn't happen because when your HTML is refreshed with a new clientlib hash, it will request for the new clientlibs only and not the previous one.The browser will not load the old clientlibs if the hash value changes. can you check and compare the complete clientlibs pa...

Hi @TheHafiz  Can you share how are you authoring it? are you copying from somewhere and pasting it or directly pressing the spacebar?as it seems to be retaining the copied content text and from there it generates hard space.

it should work for jsp based templates. check belowhttps://opensource.adobe.com/aem-modernize-tools/pages/plan-operate/evaluation.htmlhttps://opensource.adobe.com/aem-modernize-tools/pages/structure/usage.html

Hi @nitish-jain , You need to handle the code in such way to create a object once in a flow and pass it via methods only. this will ensure that multiple resolvers are not invoked for functionality and will remove the resource leakage. best way would be to create a resolver at the origin(service orig...

Hi @Sai_Krishna_1404 You can overlay the class and use Lombok delegate feature to do that to ensure any update in future doesn't impact the functionality.refer to this: http://experience-aem.blogspot.com/2023/04/aem-cloud-service-delegate-annotation-extend-core-component-sling-models.html

can you please try the following type=cq:Pagepath=/content/demofulltext=*herbs* Also can you please create a custom index(use https://oakutils.appspot.com/generate/index) for it and try it?