How maricielotz/sistema_legajos works
Project type and purpose
• From the file tree and README, this is a full-stack Laravel web application (“Sistema de Legajos”) used to manage personnel records (legajos), roles, labor regimes, documents, and user authentication/authorization. It supports two user roles (admin and user), PDF generation (DomPDF), and standard CRUD operations.
File structure
• Top-level directories:
• app/ (MVC controllers, models, middleware, providers)
• routes/ (route definitions)
• resources/ (Blade views, CSS, JS)
• public/ (entry point index.php, static assets & admin theme)
• config/, bootstrap/, storage/, database/, tests/
• MVC pattern: Controllers in app/Http/Controllers, Models in app/Models, Views in resources/views.
• Build tools: Vite (vite.config.js), Tailwind (tailwind.config.js), PostCSS, npm/package.json.
• Third-party services: DomPDF (config/dompdf.php), mail & queue (config/mail.php, config/queue.php).
• Authentication guards & middleware: config/auth.php, app/Http/Middleware/IsAdmin.php.
README for additional insights
• Minimal README; confirms it is a “Sistema de Legajos” with team members. No further architecture notes, so we derive from file structure.
Detail
• Middleware decision points (e.g., route passes through IsAdmin).
• Caching or session storage if used.
• Both synchronous flows (render view) and asynchronous flows (queues).