Keep curriculum portable
Course material lives as structured Markdown while learner state and operational workflows live in the application data layer.
NSBT course platform
A teaching platform for sprint-based Gen AI and GTM courses, with learner progress, submissions, feedback and an instructor operating surface.
product · in use
Professor of Practice, product owner and builder · Updated Aug 2026
- Teaching
- Course operations
- Gen AI
- Learning systems
01 · Problem
Practice-led courses need more than a content library: learners need pacing, submission and feedback loops while the instructor needs one view of progress and intervention.
02 · System
Structured Markdown courses feed sprint views, learner dashboards and progress tracking, while admin routes manage schedules, submissions, feedback and showcases.
03 · Outcome
The platform contains multiple multi-sprint courses, student onboarding and progress flows, and a dedicated instructor administration layer.
Context
The product treats teaching as an operating system: content, practice, evidence, feedback and pacing are connected rather than delivered as isolated lessons.
Architecture
- 01Markdown course and sprint content
- 02Authenticated student and admin route groups
- 03Supabase profiles, progress and submissions
- 04Instructor feedback and schedule tooling
- 05AI-assisted quality and summary utilities through OpenRouter
Decisions & trade-offs
Evidence
- Multiple sprint-based course tracks represented as structured content
- Student dashboard, profile, survey, progress and submission flows
- Instructor views for feedback, schedules and showcase management
What this taught me
- Teaching quality improves when the feedback system is designed with the curriculum, not added after delivery.
Follow the system
Connected work is resolved from the shared content graph.