Apply
Participants, collaborators and venues submit purpose-specific forms and required information.
Case study · Jan–Jul 2025
Patrones Hermosos
I helped lead and build a full-stack platform that replaced fragmented event-management work with connected registration and role-protected administration flows.
Overview
Product context and challenge
Patrones Hermosos needed one system for managing venue applications, participant and collaborator registration, groups, administrative roles and the operational information required to run the program.
The delivered platform connects public application forms with protected dashboards, a relational event model and supporting workflows for review, analytics, communication, documents and exports.
Core challenge
The product challenge was broad: many user roles and operational records had to remain connected while each administrator saw only the actions and information relevant to their scope.
Team coordination was equally important. With four people working around conflicting schedules, synchronous sessions were difficult. I adapted planning toward a more flexible hybrid workflow and used focused client meetings to keep delivery moving.
Role
My scope within the team
I served as Product Manager and Full-Stack Developer in a four-person team. My responsibilities crossed product planning, interface design, application architecture, data modeling, implementation, security, testing and documentation.
- Coordinate product work and adapt delivery around team availability
- Design the product architecture and relational database structure
- Create mockups and translate them into implemented interfaces
- Build reusable page elements, styles and animated interactions
- Implement JWT authentication and role-based restrictions
- Create questionnaires and plan usability and accessibility evaluations
- Execute page and workflow tests
- Document product progress and delivered behavior
The release-ready platform was a shared team result. This case study attributes product management, architecture, database, interface, JWT, role and testing work to my personal contribution.
Architecture
How the product layers connected
Next.js interface
Public registration and role-specific dashboards built from reusable React components.
Express API
Validated REST workflows for accounts, applications, venues, groups and documents.
Access controls
JWT-backed sessions and role checks protect administrative operations and data scope.
Relational data
Prisma and MySQL connect venues, people, groups, requests and operational records.
Workflow
One flow from application to program operations
The platform turns a public submission into a controlled record that authorized staff can review, assign and use throughout the program.
Review
Authorized users evaluate pending records and update their operational status.
Organize
Approved people are connected with venues, roles, groups, schedules and capacity.
Operate
Dashboards, notifications, analytics and documents use the same validated records.
Contribution
Work completed across the stack
Product direction
- — Managed priorities and coordinated a four-person team
- — Created questionnaires and maintained client feedback loops
- — Adapted the working model around conflicting schedules
System design
- — Defined the application architecture
- — Designed relational data structures in MySQL through Prisma
- — Connected page workflows with domain entities and roles
Interface development
- — Translated approved mockups into reusable page elements
- — Implemented styles, responsive layouts and animated details
- — Built registration and administrative experiences
Security and quality
- — Implemented JWT authentication and role restrictions
- — Ran workflow, usability and accessibility evaluations
- — Produced progress and delivery documentation
Decisions
Designing for multiple roles without fragmenting the product
Use one relational operational model
Venues, groups, applicants and roles remain connected in MySQL so the same records can support review, assignment and administration.
Protect workflows by role
JWT authentication establishes identity while explicit role checks separate organization-wide and venue-scoped operations.
Standardize reusable interface patterns
Shared form, table, navigation and feedback patterns reduce inconsistency across public and administrative areas.
Validate the real tasks users needed to complete
Evaluation focused on representative flows such as registration and sign-in, alongside keyboard, screen-reader and visual checks.
Deep dive
Delivery required product coordination and user validation
Team challenge
Conflicting schedules made it difficult for all four contributors to work together synchronously.
Working model
Flexible hybrid collaboration, asynchronous progress and targeted client meetings kept responsibilities moving.
Evaluation
Nine of ten participants completed assigned tasks such as registration and sign-in successfully.
01
Keyboard navigation
Core workflows were reviewed without relying exclusively on pointer interaction.
02
Screen-reader use
Representative flows were reviewed with assistive reading technology.
03
Contrast and legibility
Interface colors and content readability formed part of the accessibility review.
Outcome
What shipped—and what remains unproven
9/10participants completed the assigned usability tasks
Delivered
- Full-stack platform prepared for release
- Connected public registration and protected administration
- Venue, group and user-management workflows
- JWT authentication and role-based restrictions
- Usability and accessibility evaluation with 10 participants
- Nine participants completed the assigned product tasks
Limitations
- The evaluation involved 10 participants, so the result is useful product evidence but not a population-wide accessibility claim.
- The platform was prepared for release; this case study does not claim current public production usage or adoption metrics.
- Mockups, source code, client data and operational configuration remain private.
Lessons
- Product leadership sometimes means changing the collaboration model so the team can keep delivering despite limited shared availability.
- Security, data relationships and interface design need to be planned together when one platform serves public applicants and multiple administrative roles.
Evidence
Selected product evidence
Application portal
The public entry point separates the program audiences into clear, purpose-specific application flows.
Collaborator registration
Full resolutionA multi-section flow captures academic profile, preferred role, venue and participation preferences.
Participant registration
Full resolutionThe participant flow connects student, tutor, group preference, consent and document requirements.
Protected access
Full resolutionAuthentication establishes the identity used to select the corresponding administrative role and scope.
Venue management
Full resolutionAuthorized users can review program venues and their related group and participant counts.
Role-based administration
Full resolutionAdministrative navigation groups coordinators, mentors, support staff and participants without exposing every action to every role.
Attribution
Team work, clearly attributed
Patrones Hermosos was delivered by a four-person team. The screenshots use synthetic demonstration data and are shown with permission. Mockups, client records, source code and private operational assets are excluded.