As far as I have seen, it does work fine now as well. Check out the syntax here:
https://experienceleague.adobe.com/docs/experience-manager-htl/using/htl/block-statements.html?lang=...
resource
data-sly-resource includes the result of rendering the indicated resource through the sling resolution and rendering process.
A simple resource include:
<article data-sly-resource="path/to/resource"></article>
Path Not Always Required
Note that use of a path with data-sly-resource is not required if you already have the resource. If you already have the resource, you can use it directly.
For example the following is correct.
<sly data-sly-resource="${resource.path @ decorationTagName='div'}"></sly>However the following is also perfectly acceptable.
<sly data-sly-resource="${resource @ decorationTagName='div'}"></sly>It is recommended to use the resource directly when possible due to the following reasons.
- If you already have the resource, re-resolving using the path is additional, unnecessary work.
- Using the path when you already have the resource can introduce unexpected results since Sling resources can be wrapped or can be synthetic and not provided at the given path.
Options
Options allow a number of additional variants:
Manipulating the path of the resource:
<article data-sly-resource="${ @ path='path/to/resource'}"></article>
<article data-sly-resource="${'resource' @ prependPath='my/path'}"></article>
<article data-sly-resource="${'my/path' @ appendPath='resource'}"></article>Add (or replace) a selector:
<article data-sly-resource="${'path/to/resource' @ selectors='selector'}"></article>Add, replace or remove multiple selectors:
<article data-sly-resource="${'path/to/resource' @ selectors=['s1', 's2']}"></article>Add a selector to the existing ones:
<article data-sly-resource="${'path/to/resource' @ addSelectors='selector'}"></article>Remove some selectors from the existing ones:
<article data-sly-resource="${'path/to/resource' @ removeSelectors='selector1'}"></article>Remove all selectors:
<article data-sly-resource="${'path/to/resource' @ removeSelectors}"></article>Overrides the resource type of the resource:
<article data-sly-resource="${'path/to/resource' @ resourceType='my/resource/type'}"></article>Changes the WCM mode:
<article data-sly-resource="${'path/to/resource' @ wcmmode='disabled'}"></article>By default, the AEM decoration tags are disabled, the decorationTagName option allows to bring them back, and the cssClassName to add classes to that element.
<article data-sly-resource="${'path/to/resource' @ decorationTagName='span',
cssClassName='className'}"></article>NOTE
AEM offers clear and simple logic controlling the decoration tags that wrap included elements. For details see Decoration Tag in the developing components documentation.
