Structure canvas

Where in the UI. Structure tab. Palette / context menu adds nodes. Drag between handles to connect. Inspector on the right.

Structure is the map of the recipe. Each node is a kind of object; edges are allowed relationships, not decoration.

Tasks

1. Add elements under the template until each kind of item you need exists.
2. Build the category tree on the template (definitions + properties), then categoryRef them onto elements.
3. Add layouts per element (one is enough to start).
4. Attach scripts to lifecycle handles, or place them in the library and wire later.

Addable node kinds

The full list with legal edges is in Structure nodes. You will use template, element, layout, component (usually created from Layout tab), category definition, category property, category ref, script, expression, and asset most often. Filters, field bindings, predefined canvas items, classes, and UI packs appear when the template grows up.

Classes canvas

The Structure tab has a Classes mode (next to Template, Categories, and Expressions). On that canvas you add a class package, then category refs, scripts, actions, an edit filter, and variables. Parent→child class edges mean “extends.” Back on Template, add a class ref on the element and, when needed, a class API call on a lifecycle or button wire. Details: Categories and classes.

Mechanics

Rename in the inspector (ids propagate). Copy/paste remaps ids. Sticky notes are not exported. Illegal connections are rejected (e.g. you cannot parent a layout to a category property).