How vicentem325/reutilizagt works
Project type and purpose
• This is a full-stack, monolithic Laravel web application called “ReutilizaGT.”
• Purpose: Allow authenticated users to list, browse, request, and donate pre-owned items by category, with real-time chat, notifications, and role-based access (admin, moderator, public user).
File structure
• Top-level framework directories:
• app/ contains MVC code: Controllers, Models, Actions (Fortify, Jetstream), Notifications, Providers, View Components.
• resources/ holds front-end assets: Blade templates (views/*), CSS/JS (resources/css, resources/js), markdown policies.
• public/ serves static assets and index.php bootstrap.
• routes/ defines web (routes/web.php) and API endpoints (routes/api.php).
• config/ for environment settings (database, cache, mail, queue, auth drivers, third-party).
• database/ migrations & seeders to build schema for users, categories, products, chats, notifications.
• bootstrap/ initializes the Laravel application.
• storage/ for file cache, sessions, logs, user-uploaded files.
• tests/ covers Feature and Unit tests for authentication, API tokens, messaging, profile, etc.
• dotenv (.env.example), composer.json/lock, package.json, vite.config.js, tailwind.config.js for dependency and asset build.
README for additional insights
• Confirms Laravel stack, real-time features, background jobs, caching, session management, broadcasting.
• Emphasizes routing, Eloquent ORM, migrations, queue processing, and event broadcasting.
Diagramming conventions
→ for request/response flow
⇒ for event/job dispatch
↔ for real-time bidirectional WebSocket channels.
• Blue for external clients/services
• Green for core Laravel components
• Orange for data stores (DB, Cache, Queue)
• Purple for third-party services (Mail, Pusher).