Fields are the boxes the client fills in the panel. Every page and every content type has the fields you describe, and each field has a type that decides what the panel shows: a single line, a text editor, an image picker, a list of rows. Only the title, the address and, on content types, the publish date come built in. Everything else is a field you name.
The 18 field types
| Type | What it's for |
|---|---|
text | One line: a title, a name, a button label. |
textarea | A paragraph without formatting: a summary, a subtitle. |
richtext | Formatted content: bold, headings, lists, quotes, links, images, code and simple tables. |
image | One image from the media library. |
gallery | Several images, in an order you drag. |
file | Any file from the media library (a PDF, a video, an audio), optionally limited to some kinds. |
select | One option from a closed list: House, Apartment, Land. |
boolean | A yes-or-no checkbox, good for turning a section on or off. |
number | A number: a quantity, a year, minutes. |
email | An e-mail address. |
url | A web address. |
date | A date, picked from a calendar. |
repeater | Rows of the same fields: services, each with a name and a summary. |
flexible | A list of blocks of different kinds, each row with its own layout (see Block pages). |
link | Address, link text and “open in new tab”, in one field. |
item | A reference to another entry of the site: the featured property, the author of a post. |
group | A collapsible box that organizes fields in the panel. |
tabs | Tabs that split a long form in the panel. |
Ask the AI
On the Property type of Casa Viva, a real estate agency, add: a reference code (one line), the kind of property (House, Apartment or Land), the number of bedrooms, a photo gallery, the floor plan as a PDF, a list of features where each one is a short name, and the neighborhood. Code and kind are required. Show me the field names and labels before applying.
Saying what each field holds — one line, a choice, a PDF, a list — is enough for the AI to pick the type. Reviewing the names before applying is the cheap moment to change them.
Label and name
Every field has two names. The label is what the client reads in the panel (“Reference code”); change it whenever you like. The name is the internal one the template reads (reference_code); decide it before content exists.
Renaming a field later is costly: what was saved under the old name stops showing in the panel and is dropped the next time that entry is saved. If a rename can't be avoided, say so and ask the AI to carry the existing content over.
Help, placeholder and required
A field can carry a help line under it (“Recommended size: 1200 × 630”), a placeholder — an example shown inside an empty one-line box — and be required: its label gets an asterisk and, on one-line fields, the panel won't save while it's empty. On a site in several languages, required applies to the main language only: since v3.7.4, translation tabs never block a save.
Fields that appear only when needed
With show_if, a field appears only when another one has a given value: the video link shows when “Has video tour” is ticked; the map address when the section type is Map or Directions. There are two operators — equals for one value, in for a list of values.
- A hidden field stops being required while it's hidden.
- What was typed in it is kept, so ticking back and forth loses nothing.
- The condition looks at the fields beside it; inside a list row, only at that row's fields.
Ask the AI
On the Workshop page template, add a checkbox Online workshop. When it's ticked, show a field for the stream link; when it isn't, show the venue address. Each of those is required only while it's visible.
The AI writes the conditions with show_if, and schema:validate checks that each one points to a field that exists.
Lists, groups and tabs
A repeater holds rows of the same fields; the client adds, removes and drags rows. Ask for a title_field so each closed row shows a value — the service's name — instead of Item 01, Item 02. It works with fields whose value is text: text, textarea, number, email, url, select and link.
group puts related fields in a collapsible box, closed by default or open if you ask. tabs spreads a long form over tabs, like Content, Contact and Settings. Both only organize the panel: adding or removing them later changes nothing in what was saved.
References and links
The item field points to another entry: the client searches the published entries of one type and picks one (the featured property on the home, say), and the theme shows that entry's title, image or price. For several references, like related posts, the AI puts an item field inside a repeater. If the entry is deleted, the field comes back empty.
The link field keeps address, text and “open in new tab” in one box. It takes internal and external addresses, e-mail links and anchors (links to a spot on the page), and a blank link never blocks a save — so ask for one link field, not three.
Ask the AI
On the home, let the client choose the featured property from the published ones, plus a button with its own text and link. When no property is chosen, hide that section.
The AI uses an item field for the property and a link field for the button, and the template skips the section while the field is empty.
Reusable field sets
When the same fields repeat in several places (address, phone and opening hours on Contact and on every unit of a clinic chain), the AI declares them once as a field group (field_groups) and reuses it. A change to the set reaches every place that uses it. Don't confuse it with the group type, which only draws a box in the panel.
schema:validate catches what would break the panel: a condition pointing to a field that doesn't exist, a title_field of a type that can't label a row, two tabs with fields of the same name.