I'm running into an issue where an editable template's "structure"
components are not showing up in the publish environment. (I'm assuming
this means that the template is not rendering at all, since the "Initial
Content" sections would be part of the page itself at that point.)The
structure components do show up as expected in the authoring
environment, including in the "View as Published" view.The templates in
question appear to be present and referenced correctly in the publish
Thanks for the response. The only way I could find of doing #1
(including clientlibs on a per-component basis) involved putting the
include in the component HTL, rather than in the document head or at the
end of the body. This is why I started to look into how to add
async/defer in the first place, since I didn’t want a script in the
middle of the page to block the rendering.Ideally, I wanted to keep the
number of requests down by creating bundles for groups of components
that are loaded as need...
I'm trying to include clientlibs with async or defer attributes in the
script tag. However, I also want to ensure that each clientlib is not
loaded more than once. So if I include the clientlib within a
component's code and the component is used multiple times on a page, the
script tag should only appear in the first instance of the component.The
default way of including clientlibs (using
/libs/granite/sightly/templates/clientlib.html) does seem to prevent the
same script from being loaded more ...