Editors

Primitives vs components

Know when you are editing a simple field on the page and when you are configuring a multi-field component block from your team or the Store.

Primitives

A primitive is a single content field wired directly into the HTML — for example a headline, a paragraph, or an image. You usually edit it by clicking the element on the page or opening its field in the sidebar.

NameTypeDescription
TextprimitiveHeadlines, labels, short copy — edit inline or in the sidebar.
ImageprimitivePick or replace from the asset library; alt text may be editable too.
Rich textprimitiveFormatted paragraphs with a rich editor in the sidebar.
GroupprimitiveA container of nested fields treated as one unit in the tree.

Components

A component is a packaged block with its own fields (and sometimes slots). Examples: a slider, a pricing table, or a free-form section. After your team installs it from the Store (or builds a local custom component), you place and configure it like any other editable region — but the sidebar shows the component’s own field groups instead of one primitive.

Content vs styled
Store components ship as either a content block (inherits your site styles) or a styled widget (ships its own look, with design options you can tweak). That choice is made by the publisher, not when you edit.

Slots inside components

Some components expose repeatable or projected regions:

  • Items slots — add, remove, and reorder entries (for example slides). Macro owns the list; you fill each item’s fields.
  • Project slots — regions your developer filled with HTML for that placement. You can still edit primitives inside them; you typically cannot add or remove the projected structure yourself.

Developers: see Slots and Store components.

Do

  • Edit primitives in place when the highlight appears on the page.
  • Open the sidebar for component settings, design tokens, and slot items.
  • Ask an Admin to assign Store licenses in Dashboard → Components when a block is missing.

Don’t

  • Don’t expect every visual element to be editable — only keys your developers marked.
  • Don’t confuse Dashboard “Components” (licenses) with editing fields in the overlay.

Also see