Contents

Collection Margin

Space around the outside of the whole collection, between it and the parent.

Where to find it
Labelled Margin in the Collection Settings drawer (gear in the collection header).
Per device
Yes — you can set one value for every screen, or separate values for phone, tablet, and desktop.
Underlying CSS
margin

In plain English

Margin on the collection is the main way to inset the collection inside its parent widget or parent collection. It pushes the collection away from neighbouring content in its parent — it does not change the space inside the collection between rows.

You can set every side the same, or tune top, right, bottom, and left separately, including per device. The value "auto" on the left and right is the usual partner for Max Width when you want the collection centred in a wide parent.

When you would use it

  • A collection sits flush against neighbouring content in its parent and needs breathing room.
  • You are centring a capped-width collection: Max Width plus left and right Margin of "auto".

How to change it

  1. Open the collection, click the gear in the header to open Collection Settings, then "Margin".
  2. Set the sides you care about. Use "Same value for all resolutions" when phone, tablet, and desktop should match.
One value, or one per device? Every input in this setting sits under a “Same value for all resolutions” checkbox. Leave it checked for a single value everywhere, or uncheck it to give phones, tablets, and desktops their own. How per-device values work.

Watch out for

  • This setting is left out on the editing canvas so the drag-and-drop surface stays full size. Open Preview (or check the published page) to see the margin applied.
  • Padding is inside the collection; Margin is outside it. Row and column margins are separate settings on those scopes.

Related settings

For developers

The technical reference for what this setting produces: MDN: margin. You do not need any of it to use the setting — it is there for whoever is building the components or debugging the published page.

Where to go next