How royservillanueva2004/planificati works
Project type and purpose
• This is a full-stack web application (“PlanificaTI”) built with Laravel (PHP) following the MVC pattern.
• It supports strategic planning exercises (FODA, Porter’s Five Forces, BCG matrix, CAME, PEST) and user authentication/authorization.
Main architectural components
a. Client Layer (Browser)
• HTML/CSS/JS delivered by Blade templates in resources/views
• Assets built by Vite (resources/js, resources/css, tailwind.config.js, postcss.config.js, vite.config.js)
b. Web Server / HTTP Layer
• public/index.php → bootstrap/app.php → routes/web.php & routes/auth.php
• Middleware pipeline (app/Http/Middleware/CheckPlanSelected, auth middleware)
c. Application Layer (Laravel MVC)
• Routing → app/Http/Controllers/*.php (AnalisisFodaController, PestController, Auth controllers, etc.)
• Business logic in Controllers & Form Requests (app/Http/Requests)
• Domain models & persistence via Eloquent (app/Models/*.php)
• Service Providers (app/Providers/AppServiceProvider.php) configure container bindings (e.g., OpenAI client)
d. Data Layer
• Relational database (MySQL/Postgres) defined in config/database.php
• Migrations (database/migrations/*.php) & seeders (database/seeders)
• Queues (database/jobs table) if any background tasks are used
e. External Services
• OpenAI API (config/openai.php, invoked from controllers or services)
• Mail/Queue services (config/mail.php, config/queue.php)
Relationships & Data Flows
• Browser → HTTP Request → public/index.php → Middleware → Route → Controller
• Controller ↔ Eloquent Models → Database
• Controller → Blade view → Rendered HTML → Browser
• Asset requests (JS/CSS) served via Vite dev server or compiled assets in public/
• Controller or Service → OpenAI API over HTTPS → results fed back to Controller → View
Key architectural patterns & principles
• MVC (Model–View–Controller) separation
• Eloquent ORM for data mapping
• Service Container / Providers for dependency injection (OpenAI client, app services)
• RESTful controllers for each strategic-planning module
• Form Request validation layer (app/Http/Requests)