← Projects

Seminary Academic Management Portal

An academic portal for students, faculty, and academic administration at the Seminario Diocesano de Matamoros-Reynosa.

Website · Portal entry · Code

Problem & contribution

The portal is designed to connect enrollment, teaching assignments, coursework, and grades while giving each role access to the information it needs.

I developed the web interface, authentication and role-based access controls, and Python/Docker SQL regression tests. My CV describes these contributions, and the public repository provides the implementation evidence.

This case study describes the reviewed source; it does not establish exclusive authorship of every file or institutional adoption.

Implemented workflows

Architecture

The frontend uses HTML, CSS, and vanilla JavaScript, without a frontend build step. Supabase provides authentication and the data API; PostgreSQL holds academic records and enforces access rules.

Browser → Supabase Auth / data API → PostgreSQL (RLS + SQL functions)

Responses return to the browser through the data API. Private coursework files use Supabase Storage policies. Invitations use a separate TypeScript Edge Function with server-side credentials; the browser frontend is JavaScript.

Authentication and authorization

Authentication verifies who is signed in through Supabase Auth. The frontend checks the session and active profile.

Authorization determines which records and operations that person can access. PostgreSQL Row Level Security (RLS) and SQL functions check identity, role, profile activity, and course or enrollment relationships. Hiding a button is not the security boundary.

Two technical decisions

Keep access rules close to the data

Student grade reads are filtered to their own published records. Controlled SQL functions validate teaching assignments before grade changes. Changing a URL or browser request does not itself grant access.

SQL migrations

Separate drafts from publication

Grade drafts are stored separately from the grades students see. Revisions detect stale edits, and audit events record changes. After an uncertain write outcome, the interface requires a fresh read before another attempt.

Grade-capture documentation

Existing tests

Frontend: Python/Playwright checks cover page states, pagination, grade editing, retries, and late responses after navigation or sign-out. They use a simulated API, so they do not verify a hosted Supabase deployment.

Database: Python runners create disposable PostgreSQL containers with Docker and apply SQL migrations. Grade tests check isolation between students, hidden drafts, inactive profiles, denied direct writes, and score constraints. Local Auth fixtures do not exercise hosted authentication.

Frontend tests · Grade regression runner

These tests were inspected in the source, not executed as part of this portfolio update. Their presence is not a security certification.

Status & limitations

The repository contains the workflows, migrations, tests, and setup documentation described above. Publishing static files does not apply SQL migrations or configure authentication, storage, or invitation email.

The project provides a public website and portal address. The deployed feature set and authenticated production behavior have not been verified for this case study. No active-user counts, institutional adoption, uptime, or time-saved measurements are claimed.

No private student records or real grades are shown here.