You can retrieve page properties values in HTL using the following syntax. ${pageProperties.testfield}

It is possible OOTB using AEM Forms. https://ms-29.com/aem/forms/form-submission-from-publish-to-author-instance  https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/install-aem-forms/configure-aem-forms/configuring-the-processing-server-url 

You can use JcrPackageManager API to create package programmatically. https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/bundle/src/main/java/com/adobe/acs/commons/packaging/impl/InstantPackageImpl.java https://www.albinsblog.com/2018/01/sling-scheduler-to-auto-create-packages-...

You need to overlay the experiencefragment _cq_dialog in your project and include the rootPath="/content/experience-fragments/brands" property within the fragmentVariationPath node. <fragmentVariationPath jcr:primaryType="nt:unstructured" sling:resourceType="cq/experience-fragments/editor/componen...

Sometimes IDE needs to restart for new dependency taking any effect. Could you please restart your IDE and try again?

You need to add core.wcm.components.core dependency to your root and core pom.xml <dependency> <groupId>com.adobe.cq</groupId> <artifactId>core.wcm.components.core</artifactId> <version>${core.wcm.components.version}</version> </dependency>  

Equivalent XPath Query/jcr:root/content/aem-demo//element(*, cq:Page) [ (jcr:like(fn:name(), '%check%')) ]You can refer to this link for more details.https://experienceleague.adobe.com/docs/experience-manager-65/assets/JCR_query_cheatsheet-v1.1.pdf?lang=en  

You can utilize the nodename predicate to search for pages by their name.type = cq:Page path = /content/aem-demo nodename = *check* p.limit = -1https://experienceleague.adobe.com/docs/experience-manager-65/content/implementing/developing/platform/query-builder/querybuilder-predicate-reference.html?l...

You can use AssetReferenceSearch get the resources referenced by the page. It's constructor takes the node (content node of the page ) to search under, path where the assets are stored (can be /content/dam ) and Resource Resolver.String Pagepath = "/content/we-retail/en"; //This would be your page p...

To expose dialog properties to the React component, need to implement a Sling Model. Refer to the Adobe documentation for guidance on creating a custom SPA componenthttps://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-with-aem-headless/spa-editor/react/custom-component.ht...