What I owned
Designed and built a custom Laravel-based CMS with content types for academic programs, faculty, departments, news, events, gallery, and testimonials. Public site reads from this CMS with server-rendered HTML. Storage layer separates uploaded media (gallery, faculty photos, settings) from theme assets so admins can manage content without touching the codebase. Faculty and student panels with role-based access for future expansion.
Constraints
- Admin team has no technical background — UI had to be discoverable
- Public site must be readable on slow rural connections
- Faculty profiles include long-form bios and publications
- Multilingual-friendly content layer
Process
- 01
Content audit
Cataloged every program, faculty member, news post, and existing asset.
- 02
CMS architecture
Custom Laravel CMS with content types tuned to college operations, not generic blog primitives.
- 03
Public site build
Server-rendered pages with cached responses. Image-heavy gallery offloaded to a CDN-friendly storage path.
- 04
Admin training
Walkthroughs, written docs, and a 30-day support window.
Approach
Laravel was the right tool because the operations team needed structured content types, role-based permissions, and a relational data model — not a flat blog. The custom CMS pattern (over WordPress) won because faculty profiles, departments, and academic programs do not fit the WordPress post primitive cleanly.
Deliverables
- Custom Laravel CMS
- Public site for academic programs, faculty, news, events, admissions
- Faculty and student panels with role-based access
- Gallery with categorized media management
- News and events publishing workflow
- Smart classroom and convocation event templates
- Server-side rendered pages with response caching
Outcomes
- Live serving 5,500+ enrolled students and 20+ doctoral faculty
- Admin team publishes news and updates without developer help
- Stable production CMS with two years of uptime
- Faculty profiles indexed and discoverable through search