How amirelgohr126/kasssel works
Project type and purpose
• This is a monolithic full-stack Laravel web application that provides both a Blade-based website (in resources/views/website) for blogging, job postings, contact forms and a JSON API (routes/api.php + ApiController) for programmatic access.
• It uses Eloquent ORM for data access, Laravel’s built-in queueing for background jobs, Sanctum (config/sanctum.php) for API authentication, and a multilingual setup (models/translations + config/translatable.php).
File structure
• Top-level “app” folder follows MVC:
– Http/Controllers (ApiController, BlogController, JobController, AuthController, etc.)
– Http/Middleware (authentication, CSRF, trimming, etc.)
– Models (Blog, BlogDetail, Job, Contact, User + translation variants)
– Http/Requests (validation DTOs) and Http/Resources (API transformers)
• “routes” defines web.php (Blade routes) vs api.php (JSON endpoints).
• “public” serves index.php entrypoint and all static assets (CSS, JS).
• “resources/js” + vite.config.js handle the asset pipeline and front-end bundling.
• “database” holds migrations (users, blogs, jobs, translations), factories, and seeders.
• Configuration (config/*.php) wires up database, cache, mail, queues, services.
• Storage and bootstrap/cache handle caching, sessions, compiled views.
• Tests folder for unit/feature tests.
Detail without overthinking
– Capture every logical component (kernel, middleware layers, form requests, resources).
– Show each data store separately (main DB vs cache vs filesystem).
– Reflect the multilingual translation tables as part of the Models layer.