Level 1
Dashboard
Overview surfaces that help users understand priorities and enter operational work.
- Summary metrics and action alerts
- Workstream context
- Routes into L2 lists
Page Level Map
Internal users and applicants each have an L1 to L3 page structure. Compare the two maps, then review the PRIZM component source for implementation guidance.
Internal users
L1 → L2 → L3Operational workspace
Internal pages support oversight, queue management, and focused operational tasks.
List Page
Operational scanning and management surfaces for Programmes, Projects, Requests, and Applications.
- One heading and one primary creation action
- Search, filters, tabs, table or card list
- Clear entry points into L3 tasks
Level 3
Create / Edit / Review / Detail
Task-focused pages for creating, modifying, reviewing, or inspecting a specific object.
- Form or stepper flows
- Review and confirmation
- Object detail and related records
Applicants
L1 → L2 → L3Applicant experience
Applicant pages support orientation, browsing, and completion of one application or journey task.
Level 1
Home
A personal overview of application progress, upcoming milestones, and the next action to take.
- Current applications and statuses
- Interviews, offers, and pending tasks
- Routes into L2 collections and L3 tasks
Level 2
Opportunities / Applications
Collection pages for exploring internship opportunities or managing the applicant's own applications.
- Browse, search, and filter opportunities
- Compare relevant status and deadlines
- Open one opportunity or application
Apply / Review / Detail
Focused pages for completing an application, reviewing information, or acting on one journey item.
- Application form and project ranking
- Application, interview, or offer detail
- Review, confirmation, and next steps
PRIZM 4 component source
Open component libraryStart from the component library
Page rules should name the PRIZM component family first, then define how TOA applies it. Avoid inventing local patterns when Breadcrumb, Card, Select, Table, Button, or related primitives already answer the need.
Breadcrumb + heading Select
Breadcrumb shows hierarchy. For page-internal jumps, use a Select in the heading area; the persistent left rail stays reserved for app or guide sections.
Card, Frame, Group, Stack
Use Card for bounded content groups, Frame for preview or media surfaces, and Stack/Group to keep spacing and actions predictable.
Table, Badge, Pagination
Use Table when users scan, compare, sort, or act on records. Badges should carry status or metadata only; pagination belongs with long list surfaces.
Button, Input, Select, Combobox
Keep one primary action per section. Use Select for short fixed choices and Combobox when search or long option lists are needed.