Connecting enrollment, grades, and school announcements.
Developed for Gregoria de Jesus Elementary School as a university capstone. It did not roll out.
Explore the prototype- My role
- Sole product designer and primary front-end developer. Personas, needs discovery, UI, HTML, CSS, and Tailwind.
- Timeline
- University capstone
- Collaborators
- School principal, teachers, and students; three backend engineers
Problem
The school community needed connected views of the same work.
Enrollment, grades, and announcements involved students, teachers, and administrators with different responsibilities. The capstone explored how those tasks could connect within one school portal, with Gregoria de Jesus Elementary School's principal as the client.
Scope
Design the portal and build most of its front end.
I owned product design, spoke with the school community, created personas and interfaces, and implemented most of the front end in HTML, CSS, and Tailwind. Three backend engineers worked on connecting the system.
Research
Start with the people running and using the school.
I spoke with the principal, teachers, and students about the problems they encountered and the features they needed. As the sole product designer, I used those conversations to identify school and user needs, build personas, and define the portal’s experience.
Enrollment
Start with the student’s path into the school.
The prototype included a three-step enrollment flow, with questions for returning students and students coming back after a break. The student portal then brought grades and school announcements into the same experience.

Staff
Design the work behind the student portal, too.
Faculty screens included a grading sheet, while administrators could manage announcements. These role-specific views connected the information students saw with the work needed to maintain it. I also built most of the front end in HTML, CSS, and Tailwind, working with three backend engineers to connect the interface to the system.
Reflections and impact
A connected capstone, from research to front-end implementation.
The output covered enrollment and role-specific student, faculty, and administrator screens, with most of the front end implemented. The portal did not roll out at the school.
The project connected needs discovery with implementation. Each role needed its own tasks and permissions while sharing the information that supported enrollment, grading, and school communication.





