Does laravel practice the division into backand and frontend in a similar way to Yii2 Advanced?

Question

Laravel

Put for a look and there was such question.

Answer 1

This approach is convenient only for small sites and shops. In normal projects, controls are built into the main template, in the form of additional links and buttons, if we are logged in as an admin / moderator
For example, imagine a bulletin board? With a separate approach, you will have to make the ad edit page twice, one for the back, the other for the front, different models, templates, but why do this when you can implement everything in one place?
It’s more convenient to take out dashboards, site settings, user management, page roles, in stores it’s adding, deleting products and categories
PS If you liked Yii so much, then why don’t you write on it

Answer 2

It is possible, everything is done by Raut groups, with domain => "backend.{domain}.{tld}". You can divide the project itself into different parts, but why? It's not convenient, not best-practise, and not even good-practise.