Patterns
Configure course integrations
Use source sections to separate payment, email and CTA configuration while keeping external account state truthful.
On this page
Workflow
| Step | Responsibility |
|---|---|
| 1 | Choose the relevant course sidebar section. |
| 2 | Inspect the source provider connection state. |
| 3 | Connect only through the actual authorized OAuth workflow. |
| 4 | Select real course-specific configuration and save it. |
| 5 | Verify the final learner/public behavior separately. |
Decisions and composition
- Connected does not mean paid, enrolled or subscribed.
- Course-specific email tags differ from connecting a Kit account.
- The portfolio captures disconnected or local specimen states with no outgoing email.
Errors, recovery and limits
- No credentials are copied into the capture snapshot.
- Live OAuth, checkout, tag creation and email sending are excluded.
- Capture-only connected specimens must remain labeled simulated.
Source references
| File | Responsibility |
|---|---|
| src/components/ExternalConnection.tsx | Provider panels |
| src/constants/sidebars.tsx | Course sections |
Examples from the app
Actual TeachKit UI with Thomas McGee’s course content. Session, progress and connection specimens are simulated; no student data or live changes. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-07 · Revision d8cf23d0a329 · Documentation v0.1