Not every action in your app fits neatly into CRUD. Learn how Single Action Controllers keep your Laravel projects clean, organized, and stress-free — one small, focused controller at a time.
Chapter 1(29)
HTMX May Be All You NeedHow to Recycle LaravelHow to Bulk Insert DataLaravel Development on a Windows MachineIntroduction to Laravel PrecognitionEverything You Need to Know About Laravel in 30 MinutesHow to Provision a Server with Laravel ForgeHow to Provision a Server on Digital OceanPopping Over with PopoversUsing Generics with PHPRouting with AttributesLaravel's Flexible Cache is a Game ChangerSimpler Conditionals with when()Using Laravel's New nullOnUpdate() MethodHow to Write Custom Helpers FunctionsLaravel's Service Container Explained in One MinuteYou Can Write Your Own Laravel FacadesDeployment With Laravel Cloud In SecondsLaravel Just Destroyed Your N+1 ProblemBetter Forms, Less EffortNo Js Framework? No Problem.Single Action Controllers: One Job, Done RightInline Event Listeners In Laravel (No Class Required)Laravel's New UseFactory AttributeSingle Action All The Controllers?Should You Keep it Simple, Or Abstract Away?Code Confession: I Don't Write Tests... Until I Have ToWhere Should This Code Go?Should You Use Big Models or Services?