The teacher app, before it is built

The teacher area is moving out of the Blazor ControlPanel into its own installable mobile-first PWA. This is the full design, clickable end to end, so it can be reviewed before a single line of the real app is written.

Open the prototype

How to review it

1
Everything is clickable. Every button, row, tab, filter and toggle opens something or changes state — 6 screens and 27 dialogs. Nothing is a dead end.
2
Look at it on a phone. Teaching staff work from their phones, so that is the primary layout. Open it on your phone, or narrow the window to 375 px: the sidebar becomes a bottom bar, tables become cards, and the week calendar becomes a day-by-day agenda.
3
The data is fixed demo data. Nothing is saved and nothing is sent anywhere. Actions confirm with a short message so you can see what would happen. Today is always 11 August 2026 — the date rules depend on it.

What is in it

Today: The day at a glance, the next lesson, and what still needs recording.
Teaching: Schedule and courses, including a co-teacher's lessons and clash warnings.
Students: Who they are, their lessons and attendance, notes and exam records.
Opportunities: Course invitations to accept or deny, and student requests to apply for.
Payslips: Monthly statements with the full breakdown down to the deductions.
My Profile: Who you are, when you can work, and what you are qualified for.

Why it looks like this

The navigation was rebuilt around what a teacher actually does rather than mirroring the API, and the design corrects a number of defects in today's teacher area — including one that costs money, where a teacher cannot mark an absence as excused and the student gets billed for it. All of that, the business rules confirmed along the way, and the questions still open are written up in the decisions document.

Read the design decisions Markdown

A prototype, not the product: it is a single HTML file with Tailwind loaded from a CDN, so it needs an internet connection and is not optimised. The final app will be Blazor WebAssembly with a compiled stylesheet. The product name is still open — the shortlist starts with SL for Soft Landing.