Two purpose-built panels
Faculty and students browse, request, and monitor materials; administrators, committee members, IT staff, and custodians manage users, catalog data, access levels, and decisions.
Institutional software
Library Management System
A role-aware Laravel and Filament platform for managing an academic reading room's materials and access workflows.
Role
Full-stack engineering, product workflows, testing, Render deployment, and shared-demo operations.
Built with
Laravel 12 · Filament 5 · PHP · PostgreSQL · Supabase Storage · Render
The brief
Why it exists.
Academic reading-room workflows need more than a catalog: they need clear access rules, request history, and safe digital delivery.
- For
- Students and faculty finding materials, plus reading-room administrators managing access and operations.
- The outcome
- A shared Laravel application for managing physical and digital research materials, access requests, borrowing, and accountable administration.
Product experience
What it helps people do.
Request lifecycle
Physical borrowing and digital-access requests carry statuses, reasons, due dates, notifications, and an auditable history.
Repository intelligence
Catalog search, filters, availability, activity trends, and system-usage views help staff operate the collection deliberately.
Screenshot 1 / 2 Role-filtered catalog discovery
Engineering notes
Decisions beneath the surface.
Secure digital material delivery
Problem
Approved materials must be accessible remotely without treating a browser link as unrestricted distribution.
Approach
Authorized viewer and stream routes validate active approval before delivery. Protected PDFs are kept in private object storage and normalized with a user-and-time-specific QR watermark.
Rationale
A delivery control cannot prevent every capture method, but it adds traceability while preserving a practical reading experience.
Access that matches institutional roles
Problem
A material’s visibility and request eligibility change with access level, availability, and a user’s existing request state.
Approach
The catalog and access workflow model roles, per-material access levels, request transitions, expiry, and notifications as first-class rules.
A useful shared demo without a second product
Problem
A deployable demonstration should prove real behavior without exposing production data or credentials.
Approach
The native Laravel application runs conventionally on Render with Supabase PostgreSQL and private object storage, using the canonical seeders and controlled shared-demo lifecycle.
Architecture
Small diagram, clear boundaries.
01
Students, faculty, and staff
02
Laravel 12 / Filament 5 workflows
03
Access requests and audit events
04
Supabase PostgreSQL and private storage
Quality
- Laravel test suite and focused feature tests
- Pint formatting checks
- Production JavaScript build
- CI bootstrap and Render container verification
Security & trust
- Role-aware panels and access levels
- Authenticated protected-material delivery
- Private object storage
- Controlled shared-demo lifecycle
Live application
See the product in context.
Embedding depends on the project host's security policy. The external site remains the reliable preview.
Live preview unavailable in embedded mode.
Open live application