Custom PHP Backend System

Customer: AI | Published: 28.10.2025

I’m ready to replace the patch-work admin area that currently sits behind my PHP site with a fully custom, secure backend built on a modern framework such as Laravel (I’m open to alternatives if you can justify them). The new system needs to present two distinct environments—an Admin Dashboard for global control and an Owner Dashboard focused on day-to-day operations—both wrapped in a clean, responsive UI that works flawlessly on desktop and mobile. Core feature set • Secure login flows for both Admin and Owner roles, complete with CSRF tokens, hashed passwords, and brute-force protection. • Comprehensive traffic analytics: total visitors, active and returning users, top pages, average dwell time, most-clicked elements, and traffic sources. • Graphical data visualisation (line, bar, and pie charts) with daily, weekly, and monthly views. • Real-time tracking; I’m fine with either a Google Analytics API integration or a custom event-tracking solution. • User management screens to add, edit, or delete users and assign roles/permissions. • Performance insights that highlight slow pages or scripts so I can optimise the public site. • Exportable reports (PDF and CSV). Technical expectations • Written in modern PHP using Laravel, Symfony, or another well-maintained framework that supports MVC, ORM, and robust middleware. • Clean, modular code that follows PSR standards, with clear separation between UI, business logic, and data layers. • MySQL (or compatible) database with prepared statements/ORM to eliminate SQL injection risks. • RESTful controller structure to keep future mobile app integration straightforward. Acceptance criteria 1. Dashboards load in under two seconds on a standard broadband connection. 2. All analytics metrics validate against sample GA data or a provided test suite. 3. PDF / CSV exports match on-screen data exactly. 4. Code passes a static-analysis scan (e.g., PHPStan level 6) and includes unit tests for critical methods. I will provide access to the current site’s repo and a staging server. Once we agree on the schema, feel free to scaffold models and migrations, but keep commit history tidy. Let’s work in milestones: authentication, analytics engine, dashboards, exports, then final polish and hand-off.