How khawlaboukniter/youcode_filrouge works
Project type and purpose
• This is a full-stack gallery/event marketplace application (“ArtSpace”):
• Frontend: a React-based 3D/SPA client (artspace-frontend) for users, artists, and admins.
• Backend: a Laravel REST API + MVC application managing users, artists, artworks, events, reservations, tickets, payments, comments.
File structure
• Top-level separation:
• artspace-frontend/ → React client, Webpack/Vite, 3D modules, component hierarchy, routes.
• app/, config/, routes/, database/, resources/, public/ → Laravel app (MVC controllers, models, services, repositories, policies, requests, notifications).
• Architectural patterns:
• Backend follows MVC + Service-Repository layers + Policy/Middleware for auth & RBAC.
• Frontend follows component‐based UI + a central AppRouter and api.js for HTTP calls.
• Deployment/config artifacts:
• .env.example, config/*.php, composer.json, package.json, vite.config.js, artisan script.
Detailed capture of essential elements
• Do not simply list files; group by logical component (Auth, Artworks, Events, Reservations).
• Shared modules (ValidationHelper, AppServiceProvider) in the infrastructure layer.