How ikerbuded/appcites-projectedwes works
Project type and purpose
• This is a monolithic, full-stack Laravel web application.
• From the directory names (BuscarParellaController, CitaController, MissatgeController, Preferencia, Foto, User) and views (buscarparella, cita, missatge, usuari), it’s clearly a dating/messaging platform: users register, set preferences, browse matches, exchange messages, schedule dates, upload photos.
File structure
• app/Http/Controllers → HTTP layer (MVC controllers handling web requests).
• app/Models → Eloquent ORM domain models (User, Cita (date), Missatge (message), Preferencia, Foto, Interaccio).
• resources/views → Blade templates forming the UI.
• resources/js & resources/css with vite.config.js → front-end asset pipeline.
• routes/web.php & routes/auth.php → routing definitions.
• config/ & bootstrap/ → framework and environment configuration.
• database/migrations & seeders → relational schema migrations and seed data.
• storage/app/public & storage/app/private → file storage (user photos, private assets).
• tests/ → feature and unit tests drive quality.
README
• Laravel’s routing, service container, middleware.
• Eloquent ORM.
• Blade templating.
• Vite for asset bundling.
• Migrations for schema.
Detail
• Custom modules: BuscarParella (matching engine), Cita (dating scheduler), Interaccio (interactions tracking).
• Don’t omit the asset build step (Vite) or storage symlink (public/storage).