Compound Field

Combine Drupal field types into a reusable field. A conference can have repeated sessions, each with a title, address, topics and speaker reference. Each sub-field uses its native widget, formatter and validation, and every value is stored in the host's own field table.

When to use it

Model	Use it when
Separate fields	Values do not need to repeat together.
Compound Field	Repeated records have one fixed shape and belong to the host.
Paragraphs	Editors combine different component types, or pieces need their own URL, publication state or revision history.
Custom Field	Its own column types and widgets fit your site.

The outer field can hold unlimited items; each sub-field needs a finite cap. A compound item belongs to its host: it shares the host's revisions, translations and publication state and has no page of its own. When a piece needs to be reused or published on its own, reference it from a sub-field instead. A conference can own repeated speaker cards while each card references a reusable biography node.

Compound Field and Paragraphs both use native Drupal field types and both can nest. Compound Field stores sub-fields in the host field table; Paragraphs references child entities. Custom Field also stores composite values in one table, with its own column-type and widget system; Compound Field delegates to Drupal's field plugins, such as Address, and shares one definition across host fields. Converters exist for Paragraphs and Custom Field; run their preflight on a site copy before deciding.

• Install and create your first compound.
• Check the field types and the limits.
• Configure displays and edit content.
• Use PHP, JSON:API or Migrate.
• Deploy changes to a populated compound.

Pre-alpha software

Configuration, behavior and internal PHP APIs may change between versions without a deprecation layer, and the current item model targets fresh installations only. Rehearse upgrades and structural changes on a copy of your site before applying them to live content.