Creating Bricks

Bricks live in one global library and are reused across fields.

Go to Mason → Bricks and click New Brick in the top right.

A brick has:

• Name — what authors see in the inserter, e.g. Callout.
• Short name — the machine name used in templates, auto-derived from the name, e.g. callout. Same idea as an EE field's short name.
• Icon — pick from the full, searchable Lucide icon set.
• Group (optional) — which brick group this brick belongs to.
• Tabs (optional) — group a brick's fields into tabs such as Content / Settings. A field with no tab falls under the first tab.
• Fields — the inputs authors fill in for each instance. Each field is a card with a label, short name, kind, kind-specific settings, width, optional tab, and optional conditions. See Field Kinds.

Click Save Brick.

To remove bricks, select them on the Bricks list and choose Delete.

Duplicating a Brick#

Each row on the Bricks list has a clone action next to the edit pencil.

It copies the whole definition — every field, tab, and the binder flag — under a fresh unique short name:

<short_name>_copy

The copy then opens in the editor.

This is useful for building bricks that differ only slightly, such as one changed setting or variant, without rebuilding the field set.

Update its short name and fields, then click Save.

Editing a brick's fields affects every field and entry that uses it. Stored values are keyed by each field's short name, so renaming one orphans the values already saved under the old name. The same applies to a brick's own short name.

Brick Groups#

Groups keep a large library tidy — the same idea as EE's field groups.

The Bricks sidebar lists All Bricks plus a Brick Groups section.

• Click New next to Brick Groups to create a group.
• Each group folder can be renamed or deleted on hover.
• Deleting a group only ungroups its bricks — it never deletes bricks.
• Click a group to filter the list to just that group's bricks.
• Ungrouped shows the remaining bricks.
• Assign a brick to a group with the Group dropdown in the brick editor.

Groups also organize the brick inserter menu inside the editor.

Binders#

A binder is a reusable set of fields you define once and bind into many bricks.

For example, a common Settings panel containing theme, spacing, and background fields can live in one place instead of being recreated on every brick.

Editing the binder updates every brick that binds it.

Create a Binder#

Build a brick as usual, then turn on Binding only (binder) in the brick editor.

A binding-only brick is hidden from the insert menu. It can't be placed on a page directly; it only exists to be bound.

Bind It#

When editing another brick, click Bind a binder and choose one.

It appears as a locked, tinted block among that brick's fields.

You can:

• Drag it to reorder it.
• Drop it into a tab.
• Bind more than one binder to a brick.

Its fields keep the binder's own organization and can't be edited from the host brick. Edit the binder itself to change them.

Authoring#

On the entry form, a bound binder shows as a tidy, badged container holding its fields, ready to fill in.

Templating#

A binder's fields merge into the host brick's own namespace.

Output them with the same {brick:short_name} tokens as any other field. See Templating.

Because the namespace is flat, keep binder field short names from clashing with the host brick's fields. The editor warns you if they do.

Because it's a live reference, editing a binder's fields changes every brick bound to it. Its fields resolve by short name, so renaming or removing one orphans values already saved under the old name — the same rule as a normal brick field.