05 / Full-stack product
Student learning record system
A role-based platform connecting teacher documentation with the way parents understand a child’s learning progress.
One system presented through two purpose-built surfaces: Teacher CMS and Parent App.
01
Core record
ISSA connects the operational work of teachers with the way parents understand a child’s development. Teachers create structured records through an institutional workspace. Parents receive the same information through a warmer, more narrative experience.
02
Problem
Learning data often exists without a coherent story.
Attendance, scores, feedback, evidence, activities, and schedules are commonly separated across different records and conversations. ISSA was designed to keep those signals connected while presenting them differently to the people who use them.
03
Teacher operations
The Teacher CMS gives educators a structured workspace for student records, attendance, scores, feedback, journals, evidence, schedules, and follow-up. Its dense visual language is deliberate: it prioritizes scanning, recording, and operational clarity.
04
Parent communication
The Parent App turns structured school records into readable summaries and narratives. Attendance, academic progress, teacher feedback, activities, evidence, and schedules remain connected without making the interface feel like an administrative dashboard.
05
System architecture
Built around the record, not the dashboard.
The product is organized around shared learning data first, then presented through the interface each role actually needs.
01
Teachers create and maintain structured learning records.
02
Authentication, academic data, evidence, attendance, and progress are managed through one production backend and PostgreSQL database.
03
Parents receive a role-specific view of the same underlying record.
06
Design system
Shared product. Deliberately different interfaces.
Shared data does not require shared visual treatment. Each surface uses Plus Jakarta Sans inside the product, but the Parent App stays warm, narrative, and restrained-brutalist while the CMS uses the structured Institutional Ledger system.
Warm, readable, narrative, and shaped around how parents understand the child’s day-to-day development.
Dense, institutional, and shaped around scanning, recording, searching, and maintaining academic records.
07
Production
A working system, not a static interface.
The production layer covers the actual system behind the surfaces: database, sessions, public demo protection, deployment, and test coverage.
01
Real PostgreSQL database on Neon with shared student learning records.
02
Separate Parent and Teacher applications connected to a production API.
03
Role-specific sessions with read-only public demo mode for portfolio review.
04
Custom domains, responsive interfaces, automated frontend and backend test suites, Vercel, Render, and Neon deployment.
08
Outcome
A full-stack product shaped from both sides of the record.
ISSA demonstrates product strategy, role-based UX, visual-system design, frontend engineering, backend integration, database architecture, testing, and production deployment within one coherent system.
The live entry point opens the Parent experience. The Teacher CMS is accessible from inside the product.