Blocks Field (PRO)

Embeds a block grid inside a field, so a table row can own its own blocks the way a resource does — built, ordered and published in place.

There is nothing to configure: the grid takes its object from the record the field belongs to. Only the label, the name and the tab are yours to set — a placeholder, a default value and "required" are not offered, because the field reads none of them. It is a nested grid, not an input: it submits nothing with the form and writes through its own controller. The width is locked to the full row, as with a table.

Not the same as reusable blocks

Reusable blocks show one and the same block in several places at once, edited in one. This field gives the record a block list of its own, belonging to it and to nothing else.

It contributes nothing to the moderation preview

The moderation queue summarises a pending row from its text fields. A blocks field holds a tree, not a line of text, so it is skipped — a row whose only content is blocks appears in the queue with an empty preview. Give such a table a title field if moderators need to tell rows apart.