Features/Components

Nested components

Put instances of components inside other components, or let a widget field choose which component to render.

Components can contain instances of other components, for example a card component with a button component inside. A change to the inner component reaches every outer component that uses it. Widgets also have a Component field type: the editor picks a component from a list and it is rendered in that spot, with its own variable values. This keeps design systems small: build atoms once and compose them into larger blocks.

How it works

  • An instance can live inside a component's tree; rendering goes through render.symbol recursively.
  • Self-reference guard: a component already in the render chain is skipped; more than 500 nested levels returns 'Failed to render component.'

When to use it

  • A pricing card that uses a shared Button component
  • A hero widget where the editor chooses which CTA component to show

Limitations

  • A component cannot include itself (directly or through a chain).

Availability

  • Works in Designer and MCP.
  • Included in every plan.

How to use it.

  1. Edit a component.
  2. Set an inner element to an instance of another component (Get component, then Set).
  3. Or add a Component field in Variables and pick the component per instance.

Questions.

What happens if the chosen component is deleted?

Related features.

No card needed

Build it today.Pay when it goes live.

Every feature is unmetered while you build. Checkout opens the first time you publish.