Charter leader LMS and PD catalog
One PD catalog for the LMS, the dashboard, and the public site.
The situation
Leadership development was scattered across separate tools. Leaders could not see what they had finished. Administrators could not report CEUs without a manual merge. The public site, the dashboard, and the LMS each told a slightly different story about the same courses.
What I built
A learning management system for leadership PD with enrollment, progress, certificates, and CEU reporting — plus a course catalog API that feeds the governance dashboard and website from one schema.
How it works
ASP.NET Core, EF Core, PostgreSQL. A single course model drives the LMS UI and the catalog JSON endpoint. Authentication reuses the governance platform identity so leaders do not collect another password. Admin reporting surfaces completion without export gymnastics.
What shipped
Four phases: core LMS, catalog API, administrator reporting, and SSO with the governance dashboard. Phase 4 is live.
What I would tell the next client
Define the catalog schema first, then build the LMS. The catalog is the hardest thing to change later — and every surface will want to read from it.