Field
A field is the user interface component displayed in Content Editor, Jahia’s editing form, that lets an editor fill in a property of a content item. Each field maps to a property (content) declared in the content model. It is where the editorial team meets the model designed by developers.
Definition and how it works
Input quality shows up directly in the quality of published content. A clear label, help text that explains what is expected and the right input control (date picker, choice list, page or image picker) prevent mistakes far more reliably than guidelines sent by email. An editor does not need to know a property’s technical name to fill it in correctly.
On the technical side, Content Editor generates the form from the content type definition, then applies any overrides. These JSON settings, shipped in a module (a code package installed on Jahia), set the label, help text, order, selector type and mandatory or read-only status. The Academy documentation states that an override cannot create an input that does not exist in the definition. A fieldset groups several of them under one heading.
Academy documentation: how Content Editor forms are generated
Related terms: Fieldset · Property (content) · Content Editor · Content Type · Content type definition · Content item
Resources that cover this term
- Jahia from the Field: jContent 3.7.1 simplifies Content Editor
- EU AI Act labelling requirements: when to label AI-generated content and how to do it in Jahia
- How to develop a DXP platform with the best UX for business users?
- How to Elevate Your CX with Personas, Customer Journey Maps, and Content Auditing
- How to Make a Website Accessible: Guidelines, Design Practices, and Compliance Strategies
- What is a composable DXP?
Field vs property: the differences
The field is what you see; the property is what gets stored. Mixing them up leads teams to change the content model when improving the form would have been enough, or the other way round.
| Concept | Difference |
|---|---|
| Property (content) | The property is the attribute stored on the content item. The field is the control used to edit its value. |
| Fieldset | A fieldset groups several of them under one heading. It corresponds to a mixin, a set of properties that can be reused across content types. |
| Content Editor | Content Editor is the full form used to edit content items, pages, folders and media. It is made of these input controls. |
Field in practice
A call-to-action block links to a page on the site. If the field is a plain text box, editors paste addresses that break as soon as a page moves. If the field is a page picker tied to a reference property, the editor picks the page from the site tree. The link then designates the page itself, not a copied address.
The same reasoning applies to dates, closed lists or images. Choosing the input control is an editorial decision as much as a technical one.
Frequently asked questions
Can we rename a field or rewrite its help text without touching the content model?
Yes. The displayed label and help text belong to the form, not to the property. They can be translated and adjusted, including through a form override shipped in a module, without changing the property’s technical name. Existing content is not affected. It is a quick way to improve the quality of what editors enter.
Can we add a field to the form without changing the content type definition?
No. The Academy documentation states that a form override cannot create an input that is not declared in the content type definition. Adding a new piece of information to capture means adding a property to the model, then deploying the module that carries that definition. That is a change for the developers to make.