@snowwhite92 AFAIK, nothing needs to be updated. If you can share the network logs of when you are clicking Skip > Don't show again, i would be able to check.

Hi @snowwhite92 ,Can you take a backup of /etc/clientlibs/fd/af , by creating a package. In case your own clientlibraries exist under this, then you can move them outside this path /etc/clientlibs/fd/af. And then deleting this /etc/clientlibs/fd/af folder all together.This folder shouldn't have exis...

Hello, Is this happening for all your themes? Did you try creating a new one, is that working?We haven't heard of such an issue, as themeauthouring js is always getting loaded from /libs and not etc.As per your screenshot also, I see that it is getting loaded from libs and then there is an extra ent...

As per "Because I heard some forms we don't have XDPs , planning go with XSD only."In this case, you should go for JSON schema based form and auto generate DoR. And not create XSD or XDP for same.

You may have look at document [1], it describes how you can create a custom formatter.[1] https://experienceleague.adobe.com/docs/experience-manager-65/content/forms/adaptive-forms-advanced-authoring/adaptive-form-expressions.html?lang=en#creating-custom-patterns-for-a-field 

I am not able to comprehend the usecase where you want to make it a page level client library. In any case the issue is with  var outputs = {            "id": idNode,            "name": nameNode,            "description": descriptionNode        };As the thirdparty code will not understand this.Recom...

This is available on cloud, you may take latest version of archetype (release 47 [1]), to build the project. For 6.5, archetype changes are merged, and will be soon released. In case you need it early, you may build the archetype [2] and then build the project. [1] https://github.com/adobe/aem-proje...