Fieldset
A fieldset is a block of the Content Editor form that groups related inputs under a single heading. The Academy glossary defines it as the visual representation of a mixin, a set of properties that can be added to several content types. The same block therefore appears identically from one type to the next, which keeps long forms readable and consistent.
Definition and how it works
A form with thirty inputs in a row becomes a sequence of readable blocks (the core content, the metadata, the display options). Editors know where to look and what is left to fill in. Each field edits one property, while the block brings several together. Editors find the same landmarks on every content type that carries the mixin. The technical team maintains a single declaration.
The mixin is declared in the content type definition, shipped in a module. In the form generated by Content Editor, these blocks sit inside sections. Their order, labels and placement can be adjusted through a form override shipped in a module.
Academy documentation: sections and fieldsets in Content Editor forms
Fieldset vs field: the differences
This grouping organizes the interface. It changes neither the nature nor the storage of the properties it displays.
| Concept | What distinguishes it |
|---|---|
| Field | A field edits one property. The grouping gathers several of them under one heading. |
| Dynamic Fieldset | A dynamic fieldset only appears when a given value is selected in an earlier field. An ordinary one is always displayed. |
| Content type definition | The definition, a .cnd declaration file shipped in a module, declares the type, its properties and its mixins. The grouping is how that shows up on screen. |
Fieldset in practice
A team wants every article, product page and event to carry the same search fields (page title, meta description, social sharing image). Declared in a mixin added to those types, these inputs form an identical block in each form. Web editors always find them in the same place, under the same heading.
Grouping should follow the way editors think, not the way the code is organized. A block that mixes technical settings with editorial text loses its purpose.
Frequently asked questions
Does moving a field to another fieldset change the stored value?
No. Grouping organizes the interface and does not rewrite the stored property. A field can move to another section or position through a form override without existing content being modified. Removing a property from a mixin, however, is a change to the model. It affects the data and should be handled as a change in its own right.
Can the same fieldset be reused across several content types?
Yes. That is one of the benefits of the link with mixins. A mixin declared once can be added to several content types. The matching block then appears in each of their forms. Editors find the same fields in the same place, while developers only have one declaration to evolve.
Resources that cover this term
Explore related concepts
How to develop a DXP platform with the best UX for business users?
Explore this resource