Applied screens
Creator configuration
Registration, payments, email, and final actions share a recognizable settings rhythm.
On this page
Composition notes
- Keep provider connection and course configuration distinct.
- Use explicit labels, help text, and a confirmed save state.
- Registration dates and timezone are part of the same task.
Capture context
These are selected UI portions with surrounding breathing room, not full-height page exports. Desktop and phone examples preserve their native responsive layout. App examples include both themes; marketing has one light theme. All dynamic records and provider responses are isolated fixtures.
Source references
| File | Responsibility |
|---|---|
| src/app/make-class/[classId]/registration/page.tsx | Availability |
| src/app/make-class/[classId]/email/page.tsx | |
| src/app/make-class/[classId]/payments/page.tsx | Payments |
| src/app/make-class/[classId]/cta/page.tsx | Final action |
Interface examples
Native TeachKit interfaces with fictional course, account, and learner records. Service responses and media are isolated demonstrations; no customer data or live changes. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-22 · Revision 903bbf05ca9d · Documentation v2.0.0