Povilas Korop – How to Structure Laravel Project

Sale page_https://laraveldaily.teachable.com/p/how-to-structure-laravel-project

Archive: https://archive.fo/zBQ0Y

The most often question I hear in Laravel is this:

“Where should I put this code logic?”

Here’s a typical post from StackOverflow:

Basic Laravel is an MVC framework, it’s clear what should be in Model, View and Controller. But what if you have custom logic for processing data before passing it to the view? Where should it be?

• In the same Controller method?
• Separate private Controller method?
• Static function in Model?
• Separate class, like Service?
• Or, maybe, global helper function without any class?
• Also, I’ve heard Repository is a widely-used pattern?

And the list goes on.

Of course, the correct answer is it depends. But depends on what?
This is what I’m gonna talk about in this course.

The goal is to discuss practical examples of structuring larger Laravel applications, various approaches and patterns. We will analyze existing popular open-source projects and their structure.

Course Curriculum

Core Laravel MVC: Working with Controllers/Models/Views
PreviewUse More Eloquent: Accessors/Mutators, Scopes, Observers & “Magic” Methods (10:09)
PreviewControllers and Routes: Where to Put “Extra” Methods? (8:53)
StartStructuring Blade Files: @extends, @yield and Other Commands (13:17)
StartCustom Base Controllers and Base Models (5:13)
StartConfiguration: Never Use env() Directly in Controllers/Models (5:26)
Custom Laravel Classes Inside app/ Folder
StartForm Request Classes for Validation (4:35)
StartUser Notifications: Stop Using Mail::send() (5:50)
PreviewJobs, Queues and Scheduling Tasks (5:04)
StartEvents and Their Listeners (7:15)
StartAPI Resources for Data Transformation (9:17)
StartGlobal Helpers, External PHP Classes, Autoloading and PSR-4 (6:52)
SOLID Principles with Examples
Preview1. Single-Responsibility Principle (6:35)
Start2. Open-Closed Principle (11:36)
Start3. Liskov Substitution Principle (4:22)
Start4. Interface Segregation Principle (5:17)
Start5. Dependency Inversion Principle (4:43)
Growing Bigger: Design Patterns
PreviewRepositories: to Use or Not to Use? (9:11)
StartWhen/How to Use Service Classes? (6:35)
StartTraits: Good Practice or Last Resort? (4:50)
StartDependency injection in PHP and Laravel (6:30)
StartAdapter, Strategy, Factory and Other Fancy Words (5:28)
StartWait, What About Unit Testing? (5:34)
Packages and Open-Source Projects
StartCreate Your Own Laravel Package (9:19)
StartLaravel Modules: Package by Nicholas Widart (7:02)
StartReview: Akaunting Open-Source Project Structure (40:50)
StartReview: Laravel.io Community Portal Structure (12:02)
StartReview: MonicaHQ – Personal CRM Project Structure (41:54)
Practical Examples
StartPublic Website + Adminpanel: Reusing Classes and Features (12:15)
StartRefactoring Big Controller Into Various Classes/Methods (14:54)