You might want to check this Swagger documentation.https://developer.adobe.com/experience-manager/reference-materials/6-5/assets-api-content-fragments/index.html 

This is a known issue in AEM v6.5.18, and Adobe has provided a work around to resolve the issue.https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/release-notes.html?lang=en#known-issuesTo work around this issue, do one of the following:Remove the following “path” property./...

AEM does not provide built-in Social Sharing capabilities; You need to develop a custom component to incorporate this feature. For a detailed step-by-step guide, you can refer to this existing community discussionhttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/share-aem-url...

To extend component A to component B and inherit the style policies of component A, you can proceed as follows:1. In component B, ensure that you've configured the sling:resourceSuperType property to reference the resource type of component A.2. By extending component B from component A using the sl...

Hi @Vani1012,Navigate to the lower-left section and locate the "JSON QueryBuilder Link". Click on this link to access a list of page paths along with their associated tags.

If I have understood your requirement correctly, you can use the query builder to obtain paths and their associated tags as shown below. path = /content/masters/en type = cq:Page tagid = atlas-copco:industrial-tools/expert-hub/industries/industrial_assembly tagid.property = jcr:content/cq:tags p.hit...

We used acast.com for hosting podcasts and broadcasting them to platforms like Apple Podcasts, Google Podcasts, and Spotify. Acast provides an embedding feature that allows us to seamlessly integrate podcasts into an AEM component using an iframe.

Hi @sean12341, You can add default content to nested components using cq:template. For a detailed step-by-step guide, you can refer to this resource: http://prashantonkar.blogspot.com/2019/01/composite-components-in-aem-using.html 

Hi @n_radhakrishna, It seems like the request is being blocked by filters. To identify which filter rules are causing this, I suggest reviewing the dispatcher.log where you should be able to pinpoint the specific filter rules responsible for blocking the request.

I would also recommend the same as @arunpatidar @EstebanBustamante @aanchal-sikka suggested, use the page name with English characters such as nar-tik-tok-blir-din-nye-utviklingsavdeling. However, there's another option in the Page Properties, found in the Advanced Tab, called "Alias". You can updat...