How jhonsgomez/sistemastg works
Project type and purpose
• This is a full-stack web application built on the Laravel PHP framework.
• Purpose: an academic project-management portal for handling user registration/authentication (via Fortify & Jetstream), role/permission management, project proposals (“banco”), deadlines and reminders (via Console Commands), historical reporting, file uploads/downloads, and email notifications.
File structure
• Top-level:
• app/ – core PHP code (Models, Controllers, Actions, Mailables, Importers, Middleware, Console Commands)
• config/ – environment and package configs (database, queue, mail, Fortify, Jetstream)
• database/ – migrations & seeders defining schemas (users, roles & permissions, solicitudes, campos, valores, actas, historico)
• resources/ – frontend assets: CSS/JS (Vite), Blade views (layouts, components, pages, email templates)
• public/ – entry point (index.php), static assets (js compiled, pdf examples, formatos, images)
• routes/ – routing definitions (web.php, api.php, console.php, channels.php)
• storage/ & bootstrap/cache/ – compiled views, logs, file uploads, cache
• tests/ – Feature & Unit tests using PHPUnit
• Architectural patterns:
• MVC: app/Http/Controllers ↔ resources/views ↔ app/Models
• Service providers for bootstrapping services (app/Providers)
• Console commands & Scheduler for background jobs (app/Console, config/queue.php, Kernel.php)
• Mailables & Queues for asynchronous email dispatch
README for additional insights
• The README is the default Laravel boilerplate; it confirms use of core Laravel features but provides no domain-specific architecture details.
• Domain logic lives in custom Controllers, Actions (Fortify & Jetstream overrides), Console Commands, and Mail classes.
Final advice
• Essential elements: routing, middleware, controllers, jobs, mailers, data stores.
• Avoid overcomplication: represent each logical layer clearly.
• Where custom business modules live (e.g., ProyectosController, Recordatorio commands, BaseDocumental).