Text, Markdown, headings, and lists

Documentation / Page anatomy and the managed editor

Use Text for ordinary page copy. The managed editor displays formatted text, but native text children are stored as clean Markdown. Raw HTML text children are a legacy representation, not the format to author for new managed text.

Format by meaning

Select text and use the format bar. Its choices include H2, H3, H4, and paragraph styles P1, P2, and P3. The real page header supplies the page title; body headings should organize the content below it rather than add another competing main title.

Use headings for sections and subsections. A visually larger paragraph is still a paragraph, and a short line is not automatically a heading. Use lists for genuinely grouped items or ordered steps, not to simulate spacing.

Markdown can express emphasis, links, lists, and other supported text structure. Keep visual settings, such as alignment or font role, in the block's controls rather than embedding styling tags in the Markdown value.

Numbered lists

The page's Continuous numbering option can continue numbering across separate ordered lists. Where enabled, Text Settings > Reset Numbering lets a block restart ordered lists from one. Inspect the published sequence when steps are split across blocks or Rows.

Check the result

After saving, reopen the page and review heading order, list indentation, links, and line breaks. Pasted content may carry formatting that does not belong in the site, so use the native formatting controls to restore the intended structure.

Custom HTML source and code examples belong to their dedicated content types. They should not be disguised as ordinary Text blocks.

See Design and styling for typography, alignment, and accessibility checks.