awesome-laravel VS laravel-best-practices

Awesome Laravel

Do you know about Awesome repositories? Here it is Laravel's Awesome Repository often they discover us some curated list of communities, videos, books and courses to unlock your doubts and obstacles. I do know very little about Laravel, but some co-workers are using it for a mega project .

There are a lot of excellent packages that you can use to build certain components of your app, but they're not (for the most part) plug & play like you're used to with WP plugins

Laravel Best Practices

You should keep controllers and separate logic in services class, I try to follow best practices for readability separation of concerns DRY … this repository helps me find the way when in doubts https://github.com/alexeymezenin/laravel-best-practices

https://github.com/alexeymezenin/laravel-best-practices check this out and make sure you follow the best practices

A good starting point might be: https://github.com/alexeymezenin/laravel-best-practices

Once everything is ready, just keep on coding until you realize a specific code snippet does not follow a best practice. Let’s take a simple example with this Laravel best practice, but assume you’ll define a practice specific to your context.

I have seen in laravel-best-practices that the business logic should be in service class , and I agree with that because I'm planning to have a web routes and a a Restful routes so I have few questions