How a template is put together

Where in the UI. This is a concept page. The Structure canvas is where those boxes become nodes.

Think in layers. The template is the box. Elements are kinds of items. Layouts are costumes. Categories are extra columns. Bindings are the wires. Scripts are reactions. The app stores a live item — not the editor graph.

One template, many elements

A “Home inventory” template might have elements for Room, Box, and Object. Each element has its own layouts and may share categories (e.g. “Purchase info”). Classes bundle a set of categories + scripts so several elements can reuse the same package.

What users see

In Containd, people create items. Each item has an element type, a current layout index, built-in fields (title, size, colors…), zero or more categories with property values, optional item variables, images, and children. Your template only describes the rules; the item is the data.

What users never see

Structure nodes such as fieldBindings, editFilter, and graphWiringDefaults are authoring machinery. They compile into the template JSON the app loads. Sticky notes on the canvas are editor-only.