ReferenceComponents

section

A heading for the blocks after it, on an answer page.

An answer page is one composition, read top to bottom, and section is what gives it parts. "Why this one", "Three for you", "My short take": a title of a few words and, when it helps, a line saying what the reader gets there.

It holds nothing. The blocks after it are its content, until the next section. That keeps every other block the same whether it sits under a heading or not.

Why this oneWhat matters most in the first weeks.

Re-rendered in the browser from the SDK’s own scales. Not a screenshot.

Rendered natively by the Flutter SDK since 0.34.0 and the web SDK since 0.11.0. A build that does not declare it is never offered it.

When not to use it

Not for a short answer. A fact, a yes or a no, a confirmation, is one sentence and nothing else; a heading over it makes a page out of something that is not one.

Never with nothing under it, and never two in a row. A heading is a promise that something follows.

Props

Every block also carries type and a required fallback_text of 1 to 300 characters.

PropTypeRequiredConstraints
titlestringYes1 to 80 characters.
subtitlestringNoUp to 160 characters.

On the wire

{
  "id": "blk_30",
  "type": "section",
  "fallback_text": "Why this one",
  "props": {
    "title": "Why this one",
    "subtitle": "What matters most in the first weeks."
  }
}

Interaction

None. It is a heading.

On a page and in a thread

On an answer page it is a heading over the blocks that follow, with the page's own spacing around it. In a thread it is drawn as a small heading above the next block, without a plate.

Accessibility

Announced as a heading, so a screen reader can move through a page section by section.