Guide section 11 of 31
Navigation Architecture
The terminology recovered from the page-flow discussions is:
| Term | Meaning |
|---|---|
| Page archetype / page type | What kind of analytical task the page supports: Overview, Analysis, Search, Detail, Monitoring, Comparison, etc. |
| Page template | A reusable wireframe/composition for an archetype, already containing expected sections and component slots. |
| Page composition / layout pattern | The arrangement of sections on the canvas. |
| Section pattern | A reusable region such as filter bar, KPI summary, trend, exceptions or detail table. |
| Component pattern | A reusable data/UI element such as KPI card, slicer, matrix, variance chart or drillthrough action. |
| Interaction pattern | A repeatable behavior such as cross-filter, drill, tooltip, field switching or reset. |
| Navigation pattern | How users move between report pages/states: page navigation, drillthrough, back, bookmark navigation. |
| User flow / analytical journey | The ordered path across pages and levels. |
| Page instance | A template populated with the actual business question, measures, dimensions and filters. |
Recommended analytical journey
Overview / Monitor
↓
Analysis / Compare / Trend / Variance
↓
Drillthrough / Entity Detail
↓
Transaction / Record DetailA second common flow is Search / Lookup → Results → Entity Detail → Related/Transaction Detail.
Primary navigation should represent stable report sections. Secondary navigation may switch local views or predefined states. Contextual navigation is usually drillthrough + Back.