Presets
A brick library says what the pieces are. It never said how they go together — so every page needing "section heading, then a split image, then stats" was built by hand again, and a layout you worked out once could not be used twice.
A preset is a saved arrangement of bricks, with the values you gave them.
Saving one
Build the arrangement on a page first, then keep it:
- Select two or more bricks in the editor — click the first brick's title bar, then shift-click the last. The range highlights, and the toolbar button tells you how many you have.
- Choose Save as preset in the toolbar.
- Give it a name.
It appears in the insert menu straight away, under Presets at the top of the list, showing how many bricks it will add.
Inserting one
Open the insert menu and pick it from Presets, exactly like a brick. The bricks it contains are added in order, with their saved values, ready to edit.
Undo removes the whole preset, not one brick at a time.
A preset is a copy, not a link
Once inserted, the bricks are ordinary bricks. Edit them, reorder them, delete one — nothing objects, and nothing is "still part of" the preset.
The other side of that: editing a preset later does not change pages already built from it. That is deliberate. A preset gives you a starting point, and a page somebody has since worked on should not be rewritten underneath them.
This is the opposite of a binder, and the difference is worth holding onto. A binder is a live reference — rename a field on the binder and every brick using it follows. A preset is a stamp. Binders share a definition; presets share a starting point.
Bricks that have hit their limit
If a brick in a preset has a usage limit and the page has already reached it, that brick is skipped and the rest are still inserted — and Mason tells you which one it left out. The insert menu warns you before you click, too.
Asking for a five-brick section and getting four with an explanation beats getting nothing and guessing why.
Managing them
Mason → Presets lists what you have. From there you can rename a preset, move it to another stack, delete it, or export it.
There is no "new preset" button, and that is on purpose: building an arrangement away from a real page is exactly the thing this feature exists to avoid.
Moving them between sites
Presets travel in an export bundle like bricks do, and they bring what they need with them — the bricks they name, and any binders those bricks bind.
If something cannot be resolved on the far side — a member brick that does not exist there and is not in the bundle — it is dropped and reported, never silently swapped for something else. The preset still imports and still works; it just contains less, and you are told.