Update 1.35: Field roles, units and collection templates

A field now says not only how a value is stored but what it means — and new collections start out already grouped.

The role states the meaning:

A number is a price, an odometer reading, a room count or a year of construction. The type cannot tell them apart, the new role can — twelve fixed roles, plus a unit on the value. “120” is meaningless, “120 m²” is not.

Nothing needs touching:

Role and unit are optional. A field without a role behaves exactly as before; no existing schema has to change.

A group that occurs exactly once:

Repeater fields may now carry an upper limit. At a limit of one the repeat mechanics fall away and what remains is the shape that was missing between single value and list: an address, opening hours, a price with its currency.

Four templates when creating:

Menu, events, team and services. No invented shapes — each is derived from a collection that actually runs, extended by field groups and roles.

A tidier editor:

Field groups are the main order, not the field type. Type tabs only appear once they earn their place, and a value gets a control instead of a box.