Page pattern

Help / Definitions

“Derived from the page purpose; write it explicitly before implementation.”

Explain report usage, metric definitions, ownership, scope and analytical conventions.

[ Intro / purpose ] [ Navigation help ] [ Definitions ] [ Metric glossary ] [ Ownership / links ]

Simulation of native Power BI behaviour

Zone 1

Intro / purpose

Zone 2

Navigation help

Zone 3

Definitions

Zone 4

Metric glossary

Zone 5

Ownership / links

Reading order follows the zones above, top-left to bottom-right.

Designer

Components: Text boxes, Buttons, Shapes, Page navigator

Hierarchy: Context/control → status/primary answer → explanation/breakdown → detail → next step.

Developer

Interaction: Use only interactions that support the page's next analytical step; typical next level: **Return to report**.

Navigation: Return to report

Implementation: Compose from the listed native visuals/controls and the standard interaction patterns in this guide; custom visuals are exceptions.

Common mistakes

Treating the archetype as a rigid screen; adding unrelated analytical tasks; duplicating controls already handled globally.

Related entries