Problem or motivation
Right now CMS field values can only be bound to content properties (text, image source, link, etc.). I'd like the ability to bind CMS values to layout properties as well, specifically grid span fields (column span and row span).
In a collection list rendered as a grid, every item currently gets the same span, so all cells are uniform. I want individual items to take up different amounts of space based on a value stored in the CMS. For example, a "size" or "span" field per item that drives whether a card spans 1, 2, or 3 columns. This makes it possible to build bento-style and editorially weighted grids where featured items are larger, directly from the data, without hardcoding layout per item or splitting things into multiple lists.
Proposed solution
Let the column span and row span properties (and ideally other numeric layout values) accept a CMS field binding the same way content properties do. The field could map to a number, or to a set of named options that resolve to span values.
Alternatives considered
No response
Area
Visual Editor
Additional context
No response
Problem or motivation
Right now CMS field values can only be bound to content properties (text, image source, link, etc.). I'd like the ability to bind CMS values to layout properties as well, specifically grid span fields (column span and row span).
In a collection list rendered as a grid, every item currently gets the same span, so all cells are uniform. I want individual items to take up different amounts of space based on a value stored in the CMS. For example, a "size" or "span" field per item that drives whether a card spans 1, 2, or 3 columns. This makes it possible to build bento-style and editorially weighted grids where featured items are larger, directly from the data, without hardcoding layout per item or splitting things into multiple lists.
Proposed solution
Let the column span and row span properties (and ideally other numeric layout values) accept a CMS field binding the same way content properties do. The field could map to a number, or to a set of named options that resolve to span values.
Alternatives considered
No response
Area
Visual Editor
Additional context
No response