bcquality/microsoft/knowledge/style/abouttitle-abouttext-teaching-tips.md
Jesper Schulz-Wedde 2b5550c346
Some checks failed
Validate knowledge index / validate-index (push) Has been cancelled
Validate AL review fixtures / validate-review-fixtures (push) Has been cancelled
Validate frontmatter and structure / validate (push) Has been cancelled
Improve partner onboarding and documentation navigation (#174)
Lead with a complete plugin quick start and add task-oriented usage, troubleshooting, customization, and contribution guides. Preserve the broader plugin framing, correct conflicting contract guidance, support Agents folder reviews, and align repository validation. Convert existing sample references to clickable links without changing knowledge rules.

Co-authored-by: Jesper Schulz-Wedde <jesper.schulzwedde@microsoft.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
2026-09-09 17:31:03 +02:00

1.9 KiB

bc-version domain keywords technologies countries application-area
21..
style
abouttitle
abouttext
teaching-tip
onboarding
page
al
w1
all

Use AboutTitle and AboutText to surface teaching tips on top-level pages

Description

The AboutTitle and AboutText properties on a page render a teaching tip — an onboarding callout that appears the first time a user opens the page. They are supported on pages, individual page controls, FactBoxes, and report request pages. They are NOT supported on Role Centers or modal dialogs. The conventions: AboutTitle answers "what is this page about?" and uses the plural for list pages ('About sales invoices') and the [entity] details form for card and document pages ('About sales invoice details'); AboutText answers "what can I do with this page?" in two or three short sentences. Both are translation-aware and surface to the end user verbatim.

The reviewer signal is "this is a new top-level card or list page in an app whose sibling pages already define teaching tips" — when the surrounding app sets the precedent, a new page without AboutTitle/AboutText is an inconsistency worth flagging.

Best Practice

Set AboutTitle and AboutText on every new top-level card, list, and document page in an app that already uses them. Keep AboutText to two or three short sentences. Describe what the page does, not the navigation steps to use it — teaching tips explain WHAT, not HOW.

See sample: abouttitle-abouttext-teaching-tips.good.al.

Anti Pattern

A new top-level page in an app whose siblings have AboutTitle/AboutText, but with no teaching tips defined. Equally wrong is filling AboutText with step-by-step instructions ("Click New, then enter…") — the property is for orientation, not procedural help.

See sample: abouttitle-abouttext-teaching-tips.bad.al.