Laravel glossary
Plain-language Laravel terms.
Short definitions for the Laravel, Filament, Blade, Eloquent, authorization, queue, and SaaS architecture terms used across this portfolio.
- Framework and templating terms.
- Data, validation, and authorization concepts.
- Background work and production operations.
Definitions
Core Laravel vocabulary.
- Eloquent
- Laravel ORM used for models, relationships, scopes, eager loading, aggregates, and database interaction.
- Filament
- Laravel admin panel toolkit for resources, tables, forms, actions, widgets, dashboards, and relation managers.
- Blade
- Laravel server-rendered templating system for layouts, components, forms, and SEO-friendly pages.
- Form Request
- Laravel class for request validation and authorization before controller logic runs.
- Policy
- Laravel authorization class that centralizes who can perform actions on models.
- Queue Job
- Background work unit used for emails, webhooks, imports, exports, notifications, and slow external calls.
Usage
How to use the glossary.
The glossary is meant to reduce ambiguity during project planning. When a proposal mentions policies, queues, resources, actions, or relation managers, the definition should make it clearer which part of the Laravel system is being discussed.
For an audit or feature sprint, shared vocabulary helps separate product behavior from implementation detail. That makes it easier to decide whether a concern belongs in validation, authorization, database design, background work, admin tooling, or the Blade interface.