Introduction
This documentation accompanies the Autosplash web application maintained during the V and Bruno engagement. It is intended to help future owners, developers, and maintainers understand the project, its structure, and the work completed as part of the front-end refactor.
Autosplash is a UAE-based mobile car wash and detailing platform that allows customers to book professional car care services through its website and mobile applications. The overall product consists of multiple applications working together, while this documentation primarily covers the Laravel web application that V and Bruno were engaged to work on.
Who maintains this project
Section titled “Who maintains this project”This documentation was created by V and Bruno as part of the project handover.
V and Bruno are not responsible for maintaining either the project or this documentation after delivery unless a separate maintenance agreement is established.
The documentation is intended to be extended over time. Anyone making significant changes to the project should also update the relevant documentation so it remains an accurate reflection of the codebase.
Implementation ownership is preserved through the project’s Git history, which should be treated as the authoritative record for determining when and by whom changes were made.
What this documentation covers
Section titled “What this documentation covers”The Autosplash platform consists of multiple applications:
- Laravel Web Application (covered by this documentation)
- Client Mobile Application
- Staff Mobile Application
This documentation covers only the parts of the Laravel web application that V and Bruno were engaged to design, implement, or understand in order to complete the front-end refactor. Large portions of the existing application remained outside the scope of the engagement and are therefore documented only where they directly interact with the work that was carried out.
The native client and staff applications were outside the scope of the engagement. They are referenced only where necessary to explain how the overall Autosplash platform operates.
How this documentation is organized
Section titled “How this documentation is organized”The documentation is divided into three main areas:
- Introduction provides project context, history, and key contacts.
- Project Parts documents the architecture, application structure, hosting, deployment, SEO, assets, local development, and other implementation details.
- Bugs & Scope explains how issues should be reported, how implementation ownership is traced, and what work was completed during the V and Bruno engagement.
Where appropriate, screenshots are included to help explain workflows and project structure.
Audience badges
Section titled “Audience badges”Each page includes one or more badges indicating its intended audience.
| Badge | Meaning |
|---|---|
| Developer | Technical documentation intended for developers working on the project. |
| Non-developer | Operational or business documentation intended for owners, managers, or other non-technical readers. |
| Mutual | Documentation useful to both technical and non-technical readers. |
| Start here | Recommended starting points for readers who are new to the project. |
Recommended reading order
Section titled “Recommended reading order”If you’re new to the project, the recommended order is:
- Project History & Handover
- Architecture & Codebase
- Key People & Contacts
- Local Setup
- The remaining Project Parts documentation as needed