personal / May 2026
Iron Forge
A substantial Angular and ASP.NET Core gym-management system exploring role-based workflows, records, payments, and reporting.
Overview
A gym system needs more than a dashboard. It has to connect members, memberships, payments, attendance, and reports across different roles.
I explored the system as a multi-role product with separate operational areas for owners, administrators, reception, and coaches.
Architecture and stack
The project direction combines an Angular client, an ASP.NET Core Web API, PostgreSQL, Entity Framework Core, JWT authentication, and role-based access.
Security and authorization
JWT authentication and owner, admin, reception, and coach role boundaries were part of the exploration. This is not labeled production-ready.
Testing and verification
Reviewed dashboard, member, payment, attendance, and report flows through the available project screens and iterative checks.
What I directed
I set the direction, shaped the workflows, integrated AI-assisted implementation, and reviewed the resulting system.
What I learned
How Angular and ASP.NET Core responsibilities meet around domain workflows, authorization, and operational reporting.
Current limits
Paused after substantial branching and experimentation. Resume planned; production readiness is not claimed.
AI-assisted development
AI helped with implementation, debugging, review, tests, and documentation. I directed the requirements and decisions, then verified the result through builds, tests, repository review, and manual checks.
Selected evidence
Iron Forge
Real project material, selected for clarity. No generated product screens.
