Container

Whenever intrinsic attributes are to be applied to a multitude of tags all at once and said members are not already wrapped by another tag due to the nature of the template at hand, simply wrap them in an invisible container-tag such that they become logically grouped. This kind of grouping may come in handy as soon as conditionals, loops or bindings are to be employed to a greater scope.

Code-Blocks are only available within the browser

Nuanced Interpolation

Yet another great use for container-tags is to add more nuances to the basic interpolation-syntax of Code-Blocks are only available within the browser, by enclosing said invocation into a container with special properties.

Conditional Interpolation

Let's say that an interpolation is to be rendered conditionally - simply wrap it by a conditional container, as follows:

Code-Blocks are only available within the browser

Using containers with a single member as done above becomes tedious rather quickly, since one is often forced to append a closing-tag, as to preserve a clean hierarchy; for the sake of convenience, a self-closing container-tag supports a variable number of bound expressions, allowing for concise notation.

Code-Blocks are only available within the browser

Parameterized Interpolation

In order to parameterize an interpolation and thereby gain access to reusable components, simply define the corresponding let-bindings on the container, such that they will become available to the interpolated component when it gets interpreted.

Code-Blocks are only available within the browser