How tamthor/km_mobifone works
Project type and purpose
• This is a full-stack web application built on the Laravel PHP framework.
• The business domain revolves around “promotions” (categories, content, contacts), banners, tags, and comments, with both a public-facing API and an administrative SPA under public/backend.
File structure
• Top-level directories:
• app/ — Laravel MVC core (Console commands, HTTP Controllers, Middleware, Models, Providers)
• config/ — Laravel config for database, mail, cache, queue, services, etc.
• database/ — Migrations, model factories, seeders
• public/ — Web-server document root (entry index.php), SPA assets under public/backend, public JS/CSS assets
• resources/ — Blade templates, front-end JS & CSS sources, Vite config
• routes/ — HTTP (web.php), API (api.php), console routes
• storage/ — File storage (public, private), cache, logs
• tests/ — Feature and unit tests
• artisan, bootstrap/, vendor/ (via composer)
Essential architectural elements
• Don’t omit the middleware pipeline, queue worker, scheduled tasks, or storage abstractions.
• Both synchronous flows (HTTP → Controller → DB) and asynchronous ones (Controller → Job → Queue → Worker → DB).
• Aim for enough granularity to show each subclass of controller (web vs. API) and each major model group (Promotion, Banner, Comment, Tag, Contact).