Outcomes
What students should leave with
- Handle requests, validate input, and save data to MySQL tables.
- Build CRUD patterns for internal directories, forms, and schedules.
- Use sessions, server rendering, and safe database access for school-ready tools.
Reference map
Core topics to cover
Request flow
Sanitizing input
Prepared statements
Sessions
CRUD patterns
Flash messages
Routing basics
Module sequence
ICCT lesson flow
Module 1
Server-side request handling
Lessons: 2
What happens after a browser submits a form.
Reading requests and validating input
form data, required checks, and helpful errors
Rendering views and feedback messages
server responses, state, and confirmation patterns
Checkpoint lab
Build a program-request form that returns clean validation feedback and a confirmation screen.
Module 2
Database-backed records
Lessons: 2
Move from forms into reliable storage and retrieval.
Tables, inserts, and updates
prepared statements and consistent field mapping
Listing, editing, and archiving records
basic admin views and data lifecycles
Checkpoint lab
Create an office-hours management tool that stores staff availability and room details.
Module 3
Protected internal tools
Lessons: 2
Add accountability and user context to simple school systems.
Sessions, roles, and small permissions
login-protected utilities and user scope
Quality, security, and operational handoff
safe defaults, backups, and review habits
Checkpoint lab
Turn a public-facing tool into a staff-only system with login, role checks, and record ownership.
Capstone prompts
Projects students can actually ship
Training Request Portal
Staff submit workshop needs, administrators review them, and records stay searchable.
Faculty Office Hours Board
Teachers manage time blocks, locations, and student visit slots in a small internal app.