Mark Conroy Tests Compound Field in a Paragraphs-Style Workflow
During a hands-on test, Mark Conroy used Compound Field to model a Drupal case-study workflow similar to one built with Paragraphs. The module, developed by Mateu Aguiló Bosch, lets site builders combine existing Drupal field types into a single structured field. Conroy worked with Alpha 1, creating media-and-text and quotation structures and nesting them inside a repeated content field.
Conroy first created one compound containing media and formatted text and another for quotations. When separate fields kept those structures apart, he created a third compound containing both and attached it as an unlimited field. The nested setup moved the experiment closer to what he called a "paragraphsish" workflow, with repeated content items built from compound structures.
The limitation appeared when he tried to give editors a compact way to choose which structure to add. During the test, Compound Field's form display offered stacked and inline-column layouts, but Conroy could not find a drop-down, accordion or similar chooser that would let editors keep unused structures collapsed. He later found comparable feedback in the project's issue discussion and said the absence of collapsible editing would stop him from using that particular setup on a live site at that stage.
The discussion under Conroy's LinkedIn post picked up the same point. Aguiló Bosch responded to the missing collapsed editor by saying he now needed to add the accordion feature, while Conroy joked that the video had been a way to get him to implement it. The exchange is not a release commitment, but it shows that the module's developer had seen the usability gap surfaced by the walkthrough. Other commenters compared Compound Field with Paragraphs and Custom Field and discussed whether its flatter storage model could reduce overhead, although those comments should be read as community reactions rather than performance evidence.
That does not make Compound Field a direct substitute for Paragraphs. The project's documentation describes a different storage and authoring model: site builders combine existing field types into one compound, while each sub-field keeps its own widget, formatter, validation and storage schema. Compound values are stored with the host entity rather than as separately referenced child entities, and compounds can be nested when one structured record contains another.
The DropTimes previously covered Compound Field's initial release, including its storage model and the AI-assisted development process behind it. Conroy's walkthrough adds a different perspective by testing how that architecture feels when a site builder approaches it with a workflow familiar from Paragraphs.
The module has moved since Conroy recorded the walkthrough. Drupal.org now lists 1.0.0-alpha2, released on 19 September 2026, as the latest tagged release. The project remains alpha-stage and is not covered by Drupal's security advisory policy.
Conroy nevertheless responded positively to the module's architecture and documentation and said he planned to follow its development. His test is therefore best read as an early usability check on one authoring pattern rather than a general verdict on where Compound Field fits.
References
-
-
-
Compound Field (Fieldable Fields) | Drupal.org, Drupal.org


