Layout fields

Layout fields make long forms easier to fill in. They appear on the form but store no values, so they never show up in templates or exports of content.

Field	What it adds to the form
Section	Holds fields and shows them together in a bordered box, as a Group does. See Sections and tabs.
Tabs	Holds sections and shows one at a time, as tabs or an accordion.
UI Heading	A heading that splits the form into sections, with optional text below it.
UI Notice	A colored note for editors (info, success, warning or error), such as "Photos must be at least 1200 px wide".
UI Spacer	Empty vertical space.
UI HTML	Your own HTML, for things like a help link or an example image.

The text in a heading or notice can use basic formatting: links, lists and emphasis. UI HTML accepts the same tags WordPress allows in post content, and removes anything else.

Layout fields can't be used in conditional logic, since they have no value, but they can be shown or hidden by it like any other field. Hiding a section or tabs hides every field they hold.

Technical details for LLMs

• Type keys: ui_heading (content, ≤ 10,000 chars, safe formatting tags), ui_notice (tone: info | success | warning | error; content ≤ 10,000), ui_spacer, ui_html (content ≤ 20,000; wp_kses_post allowlist, extend with vxframework/fieldsets/ui_html/allowed_tags).
• Base keys are type, key, label, width / responsive_widths, and optional conditional_logic; no description (except ui_html and ui_section) or required. Nothing is stored; never serialized to REST, dynamic data or abilities. Not condition sources. A layout field inside a group or repeater row writes nothing into its value.
• ui_section and ui_tabs hold fields; their keys and settings are in Sections and tabs.

In this section

Sections and tabsArrange fields into boxes and tabs, and show or hide a whole set at once, without changing how anything is stored.