Studio › Elements is the project's element library: reusable rendered fragments (a hero, a product grid, a contact form, a pricing table) that documents place through an element field and templates render.
A new project starts with an empty library. Ready-made elements come from Modules: a module that ships elements adds them to the library when it is installed. Explore elements in Modules in the page header opens the Modules catalog with its Elements filter on (the button shows when you can open Modules — the develop capability). Elements imported from the former platform element kits, before that import was retired on 2026-10-18, stay in the library as your own.
Library#
The list of elements with their categories and the order they appear in pickers; each element has fields (the data a placement carries), a Handlebars body and scoped CSS. Edit them here or let the Studio agent write them. A row's ⋮ menu holds Duplicate (copies an element into a new one of your own) and Change category; on a module element you have edited, its module chip turns amber and the menu also offers Revert changes, which puts the module's version back (project managers only). The search box at the top of the list filters it by name, id, category or module (Escape clears it; reordering is paused while a search is on). Drag the list's edge to make it wider or narrower — the width is remembered in your browser.
A placement's data has to match the element's fields. When a stored value contradicts a field's declared kind (for example a live collection reference under a field declared as a list), the document editor shows a warning row on that placement and the value read-only, so nothing is overwritten by accident; Repair declaration changes the element's field to the kind that stores the value — for every placement of that element (needs the web capability; a module's element asks first, it then counts as customized). The Studio agent and MCP clients cannot write such a mismatch in the first place.
Elements that belong to an installed module carry a module chip. You can edit a module's element — it then counts as customized and module updates skip it (reset it from the module page) — but not delete it: it leaves with the module. Elements you duplicate from a module or build on one stay yours. While the module is disabled or not installed, such elements render nothing on the published site, and the picker does not offer elements of a disabled module. A module element is always placed live — it cannot be copied into a page template.
Gallery#
Every element of the library rendered on the project's design with its sample data, grouped by category in the library's order. Open in Elements on an element jumps to it in the editor.
Needs the web capability.