Dispatcher auto-allow filters is correct way to handle it, if its not working, means there are some problem with your configuration. Alternatively, you can ask editors to setup vanity in AEM with context path as prefix, so instead of setting a vanity "/abc", you should configure "/content/path/to/ho...

Try to use standard solutionshttps://experienceleague.adobe.com/docs/experience-manager-learn/ams/dispatcher/disp-vanity-url.html?lang=enYou actually need to apply Dispatcher auto-allow filters for vanity.https://experienceleague.adobe.com/docs/experience-manager-learn/ams/dispatcher/disp-vanity-url...

You need to grant read permission at least.

I am aligned with this. To solve this, I used launch script to pass cookie value to Target, in Velocity i was able to read the value:${mbox.<cookie name>}

This is a good use case for content Personalization and should be handled by specialized tools like Adobe Target. You can create different xFragments for different audiences, and export the xFragments [1] to Adobe Target. Now in Target, you can define rules to identify the audience and render the xF...

For your requirement, you can leverage the AssetReferenceSearch API which can give the details of Assets used in a page (node of type cq:Page). See this discussion also.

@ambikaTewari_ATCI I have checked this but its does not have any information about cookie. Also $cookies.all or $cookies is throwing parsing error

Hello, I am using velocity code in designs and have the following querieshow can i read a user cookie in velocity code?how can i read a variable defined in javascript in velocity code?

Have you tried the AEM List core component [1], which provides this capability?   [1] https://www.aemcomponents.dev/content/core-components-examples/library/core-content/list.html

I suggest using the selector approach here. In your template, implement a selector which will render styled HTML only.   Your 3rd parties can use a page path with selector like www.example.com/path/of/page.content.html