In general, I think it's good advice, but I guess it comes down to what you consider “close”.

For our bigger apps that have lots of logic and models we like to work with a domain oriented approach.

🧵 A few examples and thoughts on this.

https://twitter.com/aarondfrancis/status/1484695350590029826

#laravel #php A domain is basically a way of grouping the logic of some parts so that you can work on that small parts without having to deal with all classes in your app.

It's sound heavy but it's actually a pretty lightweight practice. We talk about it in our book: laravel-beyond-crud.com

🚀 I'm proud to share that our team has released a new major version of Ignition. It's the most beautiful error page you ever seen, and it will be the default in @laravelphp 9

👍You can also install it in Laravel 8!

🧵 Let's take a look at all the features At the top there's a new Docs item which will go straight to the Laravel documentation. That red dot means we found a very specific page (for instance the Eloquent page for query errors)

Settings can now be saved right in Ignition itself, you don't have to edit a config file.