Scenario 1
Mariner Academy Dashboard
The "vision" page rebuilt on Docebo Pages & Menus: four native widgets plus one iFrame widget for the parts native widgets can't do (overall %, progress by certification level, What's Next).
- Login as any of five personas (new hire, mid-path, fully certified, other branch, cancelled/waitlisted ILT)
- "Show how it's built" overlays the source of every element
- Identity via Docebo's Advanced Settings: user_id · username · 30-second auth code · salted SHA-256 — tamper or replay and the widget refuses
- Verification harness: each persona checked three ways
Scenario 2
8-Week Cohort Program
One learning plan, one enrollment: prework, an ILT course whose single session holds all four events (in person + Zoom), three Docebo assignments and three LinkedIn Learning courses released by rule at the right week.
- The Docebo configuration as a tree — release days are editable
- Enroll a test learner on Day 0 and drag the clock through the program
- Scenarios: late joiner, missed workshop, withdrawn, other time zone
- Automated checkpoints for every release day; risks of the one-session design with mitigations
What's real and what's simulated. The page, widget, identity flow, computations and test harness are real code. The tenant is simulated (Mariner has no API access for candidates): Docebo-shaped endpoints for users, learning plans, enrollments, sessions and OAuth2. Pointing the widget at a real tenant means changing one base URL and the Salt Secret. · Back to the toolkit