Marketo landing pages are often seen by enterprises as one part of a larger web presence, and one that needs to have a unified user experience and interface regardless of where a web property is served.
In order to accommodate this, a common solution is to implement the use of Web Components for their brand. This provides a consistent look and feel across multiple tech platforms, including AEM and Marketo. However, while AEM can support web components, Marketo cannot support the custom element structure needed to work with web components. This results in a major pain point where Web Component-generated templates must be rendered back into flat HTML/CSS/JS—which is not always possible to do.
To use Adobe's own web components system as an example: if someone were to generate a landing page template using the <sp-button> tag, the markup would be stripped to just <sp>. This renders the custom web component elements unusable.
Would it be possible to update TinyMCE and the landing page template syntax validator to no longer strip web component custom elements? The standard uses hyphenation to determine custom elements to prevent rendering issues in older browsers.
... View more