Linking pages, buttons, and section anchors

Documentation / Pages and navigation

Use a link destination that matches the kind of target: a page reference for an internal page, a full address for another website, or a fragment for an existing anchor on the current page.

Link text or Buttons

For a text link, select the words in an editable Text block, open the link control, enter the destination, and choose Apply. Reopen the link control to change it or use Remove Link. Write link text that identifies the destination, rather than relying on surrounding sentences to explain it.

For a call to action, insert Buttons. The dialog provides button destinations and a preview. Its page-aware normalization converts recognized site paths to stable internal references. Structured internal links use /@p/{pageId} and can retain a query or fragment suffix.

Do not assume an arbitrary pasted text URL has been converted to a stable page reference. Check stored destinations when working through source or an authorized connection.

Anchor limits

A fragment such as #details only works when the rendered page contains the corresponding HTML ID. A section's editor address, such as pageId.sectionId, identifies content for editing or reuse; it is not automatically a browser anchor. The managed section renderer exposes its section identity as editor data, not a universal anchor-creation control.

Custom source IDs must follow that fragment's required prefix. Use the actual validated ID when linking into custom content, and check that later source changes retain it.

After saving, test links outside the editor. Verify the destination page, language, fragment scroll position, and access behavior.

See Page anatomy and the managed editor for blocks and Design and styling for custom source.