I am trying to proxy/implement the Teaser component into a new component which adds an additional dialog field. The RTE in the Text section of the dialog is not reflecting any changes made to the <paraformat> node. Below is the entire descriptionGroup node. I only have 2 paragraph formats, but it is...

When creating a new Experience Fragment template, then creating a new XF using that new template, I am seeing the following error in the logs:Caused by: org.mozilla.javascript.EcmaError: TypeError: Cannot call method "getChildren" of null (/libs/cq/experience-fragments/components/xfpage/body.js#27)a...

When using the Core Component "Container" is there a way to restrict the width of the content area, which in turn, will affect the width of the AEM Layout Grid?See attached screens for current vs. desired results:vs.This can currently be achieved by placing one container in another container, but th...

When attempting to create a building block by selecting multiple items within an experience fragment, I receive the following error (Full Exception Below):Internal Server ErrorCannot serve request to /libs/cq/experience-fragments/content/buildingblock.build in com.adobe.cq.xf.impl.buildingblocks.ser...

I'm exploring how best to integrate FontAwesome characters into the Touch UI RTE, and found that this solution works, but the display is not elegant. Has anyone had experience integrating FontAwesome into the authoring experience?

When extending the [Container] core component, I want to modify the placeholder text once the component is placed on the page, displaying the jcr:title of the component.This seems to work well when adding just one, however, when I try to add another [Container] inside of that one, the display issues...

Is it possible within the Template Editor to have multiple layout containers, allowing for different component policies within those different containers?Screenshot attached for clarity.Specific example:In the top container, I want to create a policy for the Title to only allow H1, H2.In the bottom ...

I'm seeing the following error when trying to place some of the new Core Components on a page.Uncaught (in promise) TypeError: editable.getParentPath is not a function                                        core.77bdb990ebfb947d76da6f37f3dbc06c.js:30105    at Array.ns.editables.self.getParent (core....

Is there an easy/efficient way to perform the following scenario within AEM Assets?1. I have an asset named "asset1.jpg" that is referenced on X amount of pages.2. I would like to add another image to the DAM named "asset1.svg".3. I would like to replace all references of "asset1.jpg" with "asset1.s...

This is difficult for me to articulate, so I'll do the best I can.I want to extend the layout component to add some additional properties (BG color, ability to provide an anchor, etc). The tricky part I am running in to is I want the component to extend 100% of the viewport, but the inner content to...