Skip to content

Frontend overview

Audience: frontend
Status: idea
Owns: frontend
Depends on: Experience flows, API overview, Domain entities

App code is not started. This page reserves the frontend lens: routes and reusable UI must reference UX and OpenAPI—do not duplicate lifecycle tables here; link the lifecycle.

Area Personas UX flows API groups
Auth All Account & identity Auth
Onboarding / persona Candidate, Assessor, … Personas Auth
Candidate application Candidate Application happy path Applications, Trades, Identity
Payment Candidate Pay centre Payment
Evidence Candidate, Facilitator Evidence Evidence
Interview / appeal Candidate, Panel Interview Interview
Centre console Centre admin/staff Centre flows Centres / Assessors, Applications
Assessor / EV Assessor Assessor flows Applications
Awarding body Awarding body Certificate Applications / Certificate
Recommendations Candidate Gap training path Recommendations

Refine paths when the app scaffold exists.

Category Examples (placeholders) Driven by
Auth forms Login, OTP, reset Experience auth flows
Application status Stage/status display Lifecycle codes from API
Evidence Upload / folder / feedback chat Evidence flows
Payment Pay centre Payment flow
Scheduling Interview booking Interview flow
Recommendations Course list Recommendations API

Prefer design-system primitives once chosen; name components after domain or UX concepts, not backend table names.

  1. Implement against API overview / future OpenAPI.
  2. Screen copy and steps follow Experience flows.
  3. Status labels use shared stage/status codes from the domain.