WIN Student Goal Tracker – Developer Documentation
+Date: April 2026
+Project: WIN Student Goal Tracker
+System Overview
--The WIN Student Goal Tracker is a containerized web application designed to allow -teachers and program staff to track student progress, goals, benchmarks, and -events. The system follows a modern multi-tier architecture separating the -frontend interface, backend services, and database layer. -
-1. Project Description
++ The WIN Student Goal Tracker is a web-based case management system designed to support organizations working with adults with special needs. The platform enables staff to track student goals, document services, and log critical incidents while maintaining strong privacy, auditability, and compliance with FERPA, IDEA, and FAPE. +
+System Architecture
+2. Architecture
-The system architecture is organized into four main components:
+Technology Stack
+-Browser - │ - ▼ -Angular Frontend - │ - ▼ -Traefik Reverse Proxy - │ - ▼ -.NET Core API - │ - ▼ -MySQL Database -+
Architecture Description
+-
+
- Presentation Layer: Angular +
- Application Layer: .NET API +
- Data Layer: MySQL +
3. Data Flow
+Create Goal:
User → Angular → API → Database → UI
View Dashboard:
User → Angular → API → Database → UI
Technology Stack
+4. Hosting
+-
+
- Frontend: GitHub Pages / Netlify +
- Backend: Render / Railway +
- Database: PlanetScale +
- Alternative: VPS with Docker +
| Layer | -Technology | -Purpose | -
|---|---|---|
| Frontend | -Angular 20 | -User interface and client-side logic | -
| Backend | -.NET Core 9.0 (C#) | -Business logic and REST APIs | -
| ORM | -Dapper | -Lightweight database access | -
| Authentication | -JWT + Refresh Tokens | -Secure user authentication | -
| Database | -MySQL | -Persistent data storage | -
| Infrastructure | -Docker Containers | -Application deployment | -
| Reverse Proxy | -Traefik | -Routing and SSL certificate management | -
8. Environment Variables
-DB_CONNECTION=...
+JWT_SECRET=...
+JWT_EXPIRATION=3600
+
-Authentication
+9. Partner Statement
+The partner has reviewed the developer documentation and understands the system.
+-The application uses JSON Web Tokens (JWT) for authentication. -After login, the server generates a JWT token which is used to authenticate -subsequent API requests. -
+10. Walkthrough
+An installation walkthrough was conducted and successfully completed.
+-
-
- Access Tokens authenticate API requests -
- Refresh Tokens extend user sessions -
- Program-scoped tokens restrict access to authorized programs -
11. Screenshots & Analysis
+Lighthouse metrics and Chrome DevTools analysis should include Mobile, Tablet, and Desktop views. UX is clean with improvements needed for mobile responsiveness.
+12. Improvements
+Optimize performance, reduce JavaScript bundle size, and improve mobile UX consistency.
+Database Design
- -The MySQL database stores the application data for students and progress tracking.
- --
-
- Users -
- Programs -
- Students -
- Goals -
- Benchmarks -
- Progress Events -
-The backend uses Dapper ORM to execute SQL queries and map results -to application objects. -
- -Infrastructure
- --The system is deployed using Docker containers on a Virtual Private Server (VPS). -Each component runs in its own container to maintain separation and scalability. -
- -| Container | -Function | -
|---|---|
| Angular | -Frontend application | -
| .NET Core API | -Backend services | -
| MySQL | -Database server | -
| Traefik | -Reverse proxy and SSL manager | -
Deployment
- --The application is deployed using Docker containers orchestrated on a VPS. -Traefik automatically handles HTTPS certificates and routes traffic to the -appropriate container. -
- --User Browser - │ - ▼ -Traefik Reverse Proxy - │ - ├── Angular Container - │ - └── .NET Core API Container - │ - ▼ - MySQL Container -- -
13. Sustainability
+Uses free-tier hosting, Docker-based deployment, and modular architecture to support long-term maintainability.
+Appendix – Structure
+/frontend
+/backend
+/database
+/docker
+/docs
+