Page pattern

Landing / Navigation

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

Enter a report, domain or report section and choose where to go next.

Landing / Navigation — archetype wireframe

[ Header / context ] [ Navigation cards / links ] [ Shortcuts / help ]

Simulation of native Power BI behaviour
Zone 1
Header / context
Zone 2
Navigation cards / links
Zone 3
Shortcuts / help

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

Designer

Components: Buttons, Page navigator, Text boxes, Images

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: **Overview or report section**.

Navigation: Overview or report section

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