Outcomes
What students should leave with
- Define interfaces and types for forms, records, and API responses.
- Use typed functions and object shapes to catch mistakes earlier.
- Organize a front-end project with clearer contracts between files.
Reference map
Core topics to cover
Primitive types
Interfaces
Unions
Utility types
Typed functions
Narrowing
Project structure
Module sequence
ICCT lesson flow
Lessons: 2
Turn loose data into reliable shapes.
Core types and interfaces
primitive types, object shapes, and arrays
Optional fields and safer branching
unions, guards, and narrowing
Checkpoint lab
Model a student support request object with fields for urgency, status, and follow-up.
Module 2
Functions and app state
Lessons: 2
Build logic that stays readable as projects expand.
Typed functions and return values
safer helpers, callbacks, and reusable logic
Collections, maps, and derived values
working with arrays of records and summaries
Checkpoint lab
Create a typed queue manager for lab support tickets.
Module 3
Project organization
Lessons: 2
Keep medium-size projects maintainable for student teams.
Separating types, utilities, and UI logic
file structure and shared contracts
Handling remote data safely
validating response shapes and fallbacks
Checkpoint lab
Refactor a loose JavaScript dashboard into a typed project with shared models.
Capstone prompts
Projects students can actually ship
Student Task Tracker
Create a typed interface for planning assignments, deadlines, and progress states.
Service Desk Queue
Build a typed status board that groups requests by urgency and owner.