ruur31337/nmc-lab

How ruur31337/nmc-lab works

Northern Metro College Lab is a collection of four independently presented campus web applications: a public college website, Academy learning portal, Admission Portal, and Registrar System. The documented user journeys include browsing college information, using Academy services, applying to and checking admission status, and submitting or tracking registrar document requests; staff also manage registrar requests. The graph captures these domains and their evidenced runtime relationships. Admission route behavior and some registrar workflows are represented at subsystem level; links between apps are shown only where documented.

Main entry points: server.js Academy server · init.js Academy data · index.php College pages · db.php Registrar database

Components 27

Public Website

College pages main-web/www/index.php
Careers page main-web/www/careers.php

Academy Portal

Academy server academy/server.js
Authentication academy/routes/auth.js
Token guards academy/middleware/auth.js
Academy data academy/db/init.js
Announcements academy/routes/announcements.js
Courses academy/routes/courses.js
Photo services academy/routes/photos.js
Inbox APIs academy/routes/v2/inbox.js
User APIs academy/routes/v2/users.js
Internal routes academy/routes/internal.js

Admission Portal

Admission pages admission/app/routes/views.py
Application APIs admission/app/routes/api_v1.py
Application API v2 admission/app/routes/api_v2.py
Admission records admission/app/models.py

Registrar System

Public portal registrar/www/index.php
Document request registrar/www/apply.php
Student search registrar/www/staff/search.php
Request management registrar/www/staff/view_request.php
Session guards registrar/www/includes/auth.php
Registrar database registrar/www/includes/db.php

Other components

Website visitor
Portal user
Applicant
Public requester
Registrar staff

Connections 36

Website visitor → College pages: browses README.md
College pages → Careers page: links to
College pages → Portal user: links to portal
College pages → Applicant: links to admission
Portal user → Academy server: uses portal README.md
Academy server → Academy data: initializes academy/server.js
Academy server → Authentication: mounts academy/server.js
Academy server → Announcements: mounts academy/server.js
Academy server → Courses: mounts academy/server.js
Academy server → Photo services: mounts academy/server.js
Academy server → Inbox APIs: mounts academy/server.js
Academy server → User APIs: mounts academy/server.js
Academy server → Internal routes: mounts academy/server.js
Authentication → Academy data: reads and updates academy/routes/auth.js
Authentication → Token guards: verifies tokens academy/routes/auth.js
Announcements → Academy data: uses academy/routes/announcements.js
Courses → Academy data: uses academy/routes/courses.js
Photo services → Academy data: uses academy/routes/photos.js
Inbox APIs → Academy data: uses academy/routes/v2/inbox.js
User APIs → Academy data: uses academy/routes/v2/users.js
Applicant → Admission pages: uses README.md
Applicant → Application APIs: submits application README.md
Applicant → Application API v2: uses API v2
Application APIs → Admission records: uses records admission/app/routes/api_v1.py
Application API v2 → Admission records: uses records admission/app/routes/api_v2.py
Admission pages → Admission records: uses records admission/app/routes/views.py
Public requester → Public portal: tracks requests registrar/www/index.php
Public requester → Document request: submits request README.md
Public portal → Registrar database: queries requests and notices registrar/www/index.php
Document request → Registrar database: stores request registrar/www/apply.php
Registrar staff → Student search: searches students README.md
Registrar staff → Request management: manages requests README.md
Student search → Session guards: checks session registrar/www/staff/search.php
Request management → Session guards: checks session registrar/www/staff/view_request.php
Student search → Registrar database: queries registrar/www/staff/search.php
Request management → Registrar database: reads request registrar/www/staff/view_request.php

Drawn by GitDiagram on September 30, 2026 from the repository's file tree, README and source files. Read as Markdown ·