Features/Components

Reusable components

Turn any group of elements into a named component you can reuse across every page of the site.

A component is a named, reusable tree of elements stored once per site. You build it once in the Components panel and place it anywhere; every placement renders the same definition. The Components tab sits in the left sidebar next to Pages, Layers and Colors. It lists the site's components with a search field and a create button. Each component has a context menu with Name, Edit, Duplicate, Variables, Get component and Remove. Use it for navbars, footers, cards, CTAs and any block that repeats across pages, so a change in one place shows up everywhere.

How it works

  • Context menu options: Name (rename inline), Edit (open the component on the canvas), Duplicate, Variables (define widget fields, see Widgets), Get component (copies the component so it can be set on an element), Remove (with confirmation), Active/Unset Area.
  • Create: a component is created with a first root tag in one transaction; the server answers 'Component "<name>" has been successfully created.'
  • Every change goes through the builder's undo/redo history.
  • Copying a site (project duplicate, Studio template copy) copies components and component tags.

When to use it

  • One navbar and footer shared by every page
  • A product card reused in several sections
  • A CTA block that marketing updates in one place

Limitations

  • The Components panel only lists site-wide components.
  • A component cannot render itself recursively.

Availability

  • Works in Designer, MCP and AI Studio.
  • Included in every plan.

How to use it.

  1. Open the Components tab in the left sidebar.
  2. Click the plus button (Create Component) and give it a name.
  3. Edit the component on the canvas.
  4. Use Get component, then Set on an element to place an instance.

Questions.

If I edit a component, do all placements update?

Can I duplicate a component?

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.