Fields
A content type is its fields. Each field has a kind, and the kind decides what it stores, how it is edited and how it renders.
The kinds
| Kind | Stores | Typical use |
|---|---|---|
| Text | A line or a paragraph | Names, codes, short descriptions |
| Rich text | Formatted content through a text format | Body copy, descriptions |
| Number | Integer or decimal | Quantities, dimensions, prices |
| Boolean | Yes or no | Flags |
| Date / date-time | A moment | Valid from, delivered on |
| Reference | Another record | Manufacturer, parent product, responsible person |
| Term reference | A taxonomy term | Category, tag, status |
| File | A stored file | Datasheets, certificates |
| Image | A stored image with styles | Photographs, diagrams |
| Media | A media item | Video, 3D model, chart, map |
| Link | A URL and a label | External resources |
| Address | A structured address | Delivery, billing |
| Money | Amount and currency | Anything priced |
Settings live in three places, and that is on purpose
- Field settings — what the field is: required, repeatable, which type it references, which vocabulary it draws from.
- Form settings — how it is edited: the widget, its order in the form, which field group it sits in.
- Display settings — how it renders: the formatter, its label, its order, and whether it appears at all in a given display.
The same field can be a dropdown in the form and a linked label on the page, mandatory for one role and hidden in a listing. Keeping the three separate is what makes that possible.
A field you do not want on the page
Do not delete it — switch it off in that display. A date is the usual case: useful in the back office, wrong on a product page. Every display has its own answer.
Field groups
Long forms become unreadable. Group fields into tabs, fieldsets or accordions under the type's Form display, and the form gains structure without any field changing.
Repeatable fields
A field can hold many values. The form grows a row at a time; the display renders them in order. A product with three certificates is one field with three values, not three fields.
References, and what they resolve to
A reference field renders as a link to the target's own address — answered by the platform's single address rule, never assembled by hand.
A reference across organizations resolves to nothing
Not a broken link and not a bare label: silence. A label is data, and data does not cross the boundary.
An unpublished target behaves the same way, so a draft never leaks its title through somebody else's page.
Term references
A term reference field names the vocabulary — or vocabularies — its values may come from. Two firms may each have a vocabulary of that name with different terms, so the field resolves the one belonging to the record's firm, and a term from another firm's is refused on save rather than stored.
Free tagging lets an editor type a value that does not exist yet and have it created. The new term is written into the record's own firm's vocabulary — never into another firm's list, and only if the editor may create terms there.
A value stored before these rules existed keeps saving: the platform never refuses a record for what it already holds. Only new values are checked.
Formatters
A formatter decides how a stored value reads. A date can be a date, a relative time or a year; a number can carry units; a reference can be a link, a plain label or a full rendering of the target.
The catalogue is per field kind, and the first entry is the default.