Row split components
A row split is a structural marker that ends the current layout row and starts a new one. It is used with column splits to prevent later components from continuing in the same row.
Use a row split when the next content belongs below, rather than alongside, the preceding content. It has no person-facing settings and should be added only as part of a clear page layout.
flowchart TD
A[First row of related content] --> B[Row split]
B --> C[New full-width row or a new column layout]Keep the reading order simple
People using a narrow display, keyboard or screen reader experience content in document order. A row split must not be the only thing that makes the page understandable. Review the page as a top-to-bottom journey before relying on columns and rows.
Use headings and labels to explain relationships between sections. Do not use a row split purely to create visual whitespace; ordinary content spacing is more robust.
Use rows with columns
A row split is most useful after a pair of columns, when the next component should return to the full page width. For example, two short address details may appear beside one another, followed by a full-width question that applies to everyone. Add the row split immediately before the component that starts the new row.
Keep structural markers close to the content they control. A row split separated from its layout by several components is hard to understand during later edits and increases the risk that a new component appears in an unexpected place.
Maintain and test the structure
After reordering components, review the complete page in User view. A moved row split can make later content appear alongside an unrelated question without being obvious in the Builder list. Test long errors and conditional content as well as the normal layout: a revealed component may need to remain with its controlling question rather than begin a new row.
If the page needs several column and row markers to stay understandable, it is usually a sign that the content should be split into separate pages or groups.
Check before publishing
- The next component is clearly related to the content above it.
- The page remains understandable in a single-column layout.
- Keyboard focus follows a sensible order.
- The layout does not separate an instruction from its control.
- Conditional content appears in a sensible place when it is revealed.
- Reordering a component has not changed the meaning of later layout.