OK, I just ended up making a custom Transformer since I was only really worried about img tags for this use case.

No, we're just publishing experience fragments in a very stripped down template to produce an html fragment.  The number/types of component's being used might change from page to page and we don't want the downstream application to need to process any json at all.  We just want each to produce a sin...

No, the html fragments are being consumed by an angular app and injected into it so there's no iframe.  The needs for the content are fairly simple so we are hoping to just work with the out of the box components.  I'd rather not create custom components if I can avoid it

We're using experience fragments to produce HTML fragments that are consumed and displayed by an external application.  Since the html in that case is no longer being served by the AEM instance we need any assets to be referenced by an absolute path rather then a relative one.  I've seen some older ...

Just an update, we've found that SDI works if the template component is unlocked, but not when it's locked.

We've created components, we've added them to our authored templates and they are working fine.  But when we try to designate the components in the template should be rendered through SDI its not working.  When we create a page using those templates the components we drop on the page that are design...

We followed that, and we have it working for authored content in a page, but not any components authored in the template.

Yes, I meant editable templates

We're trying to set up SDI on pages that use authored templates on 6.3 but aren't having any luck.  We have a user widget in the header that uses dynamic data but we aren't seeing anything happen in page rendering when we flag the header component as being an SDI resource type.  We are seeing includ...