Alkayan Construction Nova

Al Kayan's v2.0 rebuild on a custom PHP MVC framework (front-controller pattern): routing, JSON APIs, a reusable PHP component system across 10+ templates, GSAP animations and a Three.js hero. Rebuild complete, deployment pending.

Production · PHP · Construction · 3D Web · 2025

PHP, Custom MVC, MDBootstrap, Three.js, GSAP, WebGL

View live site Source on GitHub View architecture

The problem

Al Kayan Construction's business site needed a ground-up rebuild (Nova v2.0) with a distinctive visual identity and tighter security than the legacy codebase, without pulling in a full framework's overhead.

My role

Responsibilities

Designed and built the entire Nova v2.0 platform solo: the custom PHP MVC framework, the OOP layout component system, the 3D front end, and the security hardening pass.

Main workflows

1.Visitor browses project categories — delivered, planned, under construction, interior design, supplies — through clean URLs
2.The front controller (public/index.php) parses the request and routes it to the matching controller, either rendering a view or returning JSON
3.A JSON API endpoint (?type=api&resource=projects) serves the same project data for client-side rendering and pagination
4.Authentication and identity for the connected real-estate platform are handled by a separate microservice on a dedicated subdomain, decoupled from this app

Architecture

Select the diagram to open it full size.

Custom PHP MVC framework built from scratch on a single front-controller entry point
Reusable OOP component system (static layout classes) exposing navbar, footer, hero, and section blocks as composable methods, keeping markup DRY across 10+ templates
MDBootstrap, GSAP-driven 3D card animations, and a Three.js WebGL hero scene, with light/dark theme persisted via localStorage
File-based caching layer sitting in front of MySQL for the high-traffic project-listing endpoints

Security and deployment

CSRF tokens on every form and full-stack input validation
Removed hard-coded credentials and closed .env exposure carried over from the legacy codebase
Fixed error-message leakage that could reveal internal paths or stack traces
Security hardening headers set at the front controller

Results

Lighthouse performance raised from 50 to 80+ in the v2.0 rebuild (measured on staging) with strategic indexes and a file-based caching layer.

Performance

Lighthouse · v2.0 rebuild (staging)

Performance: 50 to 80+

Performance score before and after strategic indexes and a file-based caching layer.