Check the following Make sure to include preload tag in head sectionMake sure to include all paths (check n/w tag with font filter) of fonts added as preload. Sometime, css files generate some random urls.

Honeypot is an old way to avoid spams by adding a tricky field in your form, but now hackers are quite smart, so it's observed that honeypots are not much effective. Rather, it's advised to use Captcha with client-side and server-side validation.

Earlier AEM had Reference Paragraph [1] component, which was removed from the Touch UI interface, and AEM Introduced a more flexible way to manage and use shared content, called Experience Fragments [2]. You should create xFragments for the content that is reusable, and use the Experience Fragment...

2.21.0 is not compactable with 6.5.10, see this document [1], you have to use 2.19.0 instead. [1] https://experienceleague.adobe.com/docs/experience-manager-core-components/using/versions.html?lang=en

I have noticed that the pathbrowser make following request [1] which has hideContentFragments as true. If we make it false, path browser start returning CFs also. So you have to find out a way to make this flag as false. [1] http://localhost:4502/mnt/overlay/cq/gui/content/linkpathfield/picker/vie...

If the values are the same of the field selected for Order By, then their node hierarchy will be used to define precedence.

Which version of core components you are using? Have you checked if it's compactable with 6.5.10?

Just checking if you have configured CQ Mail service correctly [1] ? [1] https://experienceleague.adobe.com/docs/experience-manager-65/administering/operations/notification.html?lang=en

I suggest the following approach Create a Generic List [1] named "country" for countries <Australia:au, India:in ...>Create state generic lists, one for each country, named (au-state / in-state), and add states in it.Create Cities generic lists, one for each state-country combination (in-hp-cities, ...

Logically, CFs are used to collect structured data, which does not have any presentation linked to it. Saying this, CFs are re-useable content, to be consumed by other components, so that components can consume the CF data and render it in a presentable layout. So ideally, you should create a p...