Custom ISML tags with ismodule
Key Takeaway
Declare a custom ISML tag with <ismodule> by giving it three things: the template path, the tag name without the is prefix, and the attribute names it accepts. Then call the tag as is plus the name, with attribute values, such as <israting stars="4">.
The <ismodule> tag declares a custom ISML tag that is backed by its own template file. After you declare the tag, it inserts that template wherever a page uses it. The tag can also pass user-defined attributes to the template. You can then reuse a piece of template logic like a built-in tag, instead of copying it into every page.
What a custom ISML tag is
<ismodule> builds reusable units of template functionality that you insert with custom ISML tags. A custom tag is an included template that can take user-defined attributes, so every custom tag definition is stored in its own separate template file.
<isinclude> pulls in content in two ways. A local include pulls in content from another template file. A remote include pulls in content by running a second pipeline. Unlike <isinclude>, <ismodule> puts an included template behind a named tag, so the caller can pass attribute values each time it uses the tag.
In SFRA implementations, <ismodule> is mainly used for content assets.