aside element
Content related to, but separate from, the main content — a tip, a related-links box.
Renders
<aside>Required
Nothing beyond
type.Native apps
Compiled native apps and server-driven apps
Syntax
aside element
{ "type": "aside" }An element lives in a screen's sections, another element's elements, a layout slot or a component root.
Properties
| Property | Type | Description |
|---|---|---|
elements | array of element | |
layout | object |
|
content | string | literal text, or an expression starting with = ("=product.name") |
Plus the properties every element accepts: id, className, style, responsive, states, animation, visible, ariaLabel, attributes and more.
Example
aside example
{
"type": "aside",
"className": "tip",
"elements": [
{ "type": "text", "variant": "label", "content": "Tip" },
{ "type": "text", "content": "Orders placed before 2pm ship the same day." }
]
}Expected output
The HTML IWC rendered for the example above (inside the page's content wrapper). Class names such as i807b63fc are generated per element for its scoped CSS.
Rendered HTML
<div class="iwc-page ipage" id="iwc-content">
<aside class="iwc-aside i427f81e3 tip">
<span class="iwc-text i0efd68b2 iwc-text-label">Tip</span>
<p class="iwc-text ic0be0fe1">
Orders placed before 2pm ship the same day.
</p>
</aside>
</div>Data, conditions & styling
- Conditional rendering:
"visible": {"auth": "signed-in"},{"roles": ["admin"]}or an expression such as"=product.stock > 0". Decided on the server: hidden elements are never sent. - Data binding:
bindtakes text from data (name,user.name,props.title,params.slug,state.cart.count);bindsbinds attributes. Containers become data-driven withdata+item. See data binding. - Styling:
classNamefor your stylesheets,stylefor CSS in JSON,statesfor hover/focus/active,animationfor entrance motion. See the style property reference. - Responsive behaviour:
responsiveapplies CSS at or below a breakpoint ({"mobile": {"padding": "12px"}}); grids also takeresponsiveColumns.