Local Setup
Reproducible development environment using Docker and PHP constraints. Required for consistent onboarding and environment parity. See Local Setup.
Autosplash Documentation
This project was originally developed by a previous team and later taken over by the V and Bruno team for a scoped front-end focused rework.
This site is the living version of the system documentation.
Scope in one paragraph
Section titled “Scope in one paragraph”V and Bruno’s engagement was primarily front-end work: a redesign of the homepage and the authenticated user experience, not a full-stack rebuild. Two areas expanded beyond that scope due to operational necessity:
- Infrastructure continuity. When the AWS region hosting project storage was decommissioned, V and Bruno migrated the system to DigitalOcean to keep the platform operational. This was executed outside the original contract scope as a continuity measure.
- Backend alignment layers. Existing backend logic was not consistently structured for the new front-end requirements. Gaps included areas such as non-guest user handling and coupon logic without safe reuse pathways. Minimal abstraction layers were introduced strictly to enable the front-end work, without performing a full backend refactor.
Full write-up: Front-End Scope & AWS Migration.
At a glance
Section titled “At a glance”Version Control and Branching
Branching model, commit conventions, and release workflow. Defines how changes move from development to production. See Version Control.
Views Overview
Breakdown of frontend structure across guest, logged-in, and admin surfaces. Maps UI areas to backend functionality. See Views.
Architecture
Component-based structure with Component Driven Design principles. Includes service-layer patterns and backend integration boundaries. See Architecture & Codebase.
Key people
Section titled “Key people”| Name | Role |
|---|---|
| Vladimir Laskin | Project Manager and Senior Developer, primary technical contact for V and Bruno work |
| Abdallah Afify | Fullstack Developer |
| Gabriela Bruno | V and Bruno Manager and Head Designer |
For legacy system questions, contact Autosplash directly. The V and Bruno team does not maintain contact with previous developers.
Full details: Key People & Contacts.
Audience badges
Section titled “Audience badges”| Badge | Meaning |
|---|---|
| Developer | Technical documentation intended for engineers working on the codebase |
| Non-developer | Operational or business-facing documentation |
| Mutual | Relevant to both technical and non-technical readers |
| Start here | Entry point for new contributors |
Navigation
Section titled “Navigation”IntroductionProject background and documentation structure
Project PartsArchitecture, setup, deployment, SEO, assets, and system design
Reporting Bugs & Tracing IssuesBug reporting standards and responsibility tracing
Scope - V and Bruno WorkEngagement boundaries and system ownership