Skip to main content
Seventeen section types are available in the Page Editor, grouped into five categories in the Components palette. The palette has a search box, so if you know roughly what you want you can type it rather than hunting through categories. This page is a map: what each section is for, and which ones have behavior worth reading about separately. Every section’s own fields are listed in the Properties panel when you select it.

​
Data Display

The sections built around Item and Collection data. This category is expanded by default.

​
Layout

Container and Card are the two sections that can hold others, so they are how you group things and style the group as a unit. AdminToolbar is always rendered last on the page no matter where it sits in the tree.

​
Content

​
Media

​
Interactive

They are not interchangeable, and the difference is what happens when the URL does not resolve:
  • ActionLink removes itself from the page if its URL depends on a field the Item has not filled in. This is why it is the right choice for Destinations.
  • Button and Link do not. A Button with an empty URL renders as a button that does nothing; a Link with an empty URL renders as a link to nowhere. Both are fine for fixed URLs you typed yourself, and a poor choice for URLs built from Item fields.
All three support app deep links with a fallback URL or message, so tel:, mailto: and myapp:// schemes work in any of them — see App Links & Fallback URLs.

​
What is not a section

Initials and ExpandableText show up inside other sections — the avatar fallback when an Item has no image, and the truncate-with-more control on long descriptions. They are internal pieces, not separate section types, and they are not in the palette. Every section, whatever its type, also carries an optional visibility condition; that is a mechanism of its own, covered in Conditional Visibility.