Higher education / Live
Juliana King University
A university web platform connecting public content with a controlled Laravel CMS.

Public website · captured 13 November 2026. Figures shown within the interface belong to the source website.
01 / PROJECT NOTES
What the platform serves
A university needs more than a collection of static pages. Academics, admissions, events and institutional content have different editorial requirements. The public website provides an accessible entry point while authorised staff need a manageable way to maintain that information.
02 / PROJECT NOTES
My engineering contribution
I developed the connection between a Next.js public website and a Laravel administration and API application, bringing reusable public pages, content-backed views and staff publishing workflows together.
03 / PROJECT NOTES
Architecture and publishing
Public content is rendered through the frontend, with Laravel supplying content and accepting the relevant public submissions. The documented publishing design uses an external static build so the public host does not need to run a Node.js application server. The administration application and relational data remain separate from the exported public site.
04 / PROJECT NOTES
The difficult boundary
Editorial flexibility has to coexist with a consistent public brand. The CMS handover describes controlled sections, draft previews and revision controls rather than unrestricted code editing. That makes content ownership a deliberate application workflow, instead of granting every editor deployment access.
05 / PROJECT NOTES
Engineering decisions
Keeping the public export and administration application distinct makes their operational responsibilities explicit. An external build can publish a static release while PHP handles the CMS. The handover also documents how another developer can take over the source, so maintenance does not rely on undocumented knowledge.
06 / PROJECT NOTES
Project overview
The platform separates the public university website from its administration and data services. This case study focuses on the public experience, content architecture and documented publishing workflow.
Explore the boundaries.
A simplified view of the application. Select a component to explore its role.
Simplified architecture study · NOT A LIVE SYSTEM
Next.js pages form the visitor-facing surface.
Laravel owns the documented content/API and editor workflows.
MySQL holds the application records behind that boundary.
Project summary & sources.
- A public website for university information and admissions.
- Separate responsibilities for public content, administration and data.
- A documented publishing workflow and technical handover.
THE PUBLIC EXPERIENCE / TWO VIEWPORTS
One product.
Different contexts.
Desktop and mobile views of the public website.
Open desktop capture ↗Open mobile capture ↗
