Doubt about Laravel’s basic structure!

Question

Is there any recommendation to follow from the Laravel framework when starting a project?
I ask this because when starting a project already comes by default with some predefined structures!

saw that comes with some predefined Migrations

Vi que tbm comes with a predefined Model

I saw that also comes a Factory already created for inserting data

My doubt is the following, the standard Standard in the newest version (V8.52.0), at the moment I am posting this doubt.
By default brings an example structure, for creating an authentication system!

1 - There is a tutorial/documentation for me to better understand how to continue this clean implementation that comes with the Framework??
Or am I free to continue this clean implementation the way I see fit?
looking at this clean implementation I saw a good organization, and a good convention for an authentication system!
I would like to follow this clean implementation suggested by Aravel! I’d like to understand it better...

2 - the Migration failed_jobs, which is already predefined in the list of Migrations of the Laravel, It is part of the recommendation of the authentication system?
or this Migration is already preset so that the default language can register queues of events that have failed?

3 - This authentication structure that comes with the Laravel, has something to do with the Laravel/ui, or with the Laravel/Jetstream ?
repaired q the Laravel/ui, takes advantage of this base structure that comes along with the Laravel project.

4 - the package Laravel/ui, and the Laravel/Jetstream, it is recommended to use them?
i took a course in Nursery in udemy, where the instructor of the course taught to use the Nursery/ui, I enjoyed a lot!
Just had a few points where I didn’t like it much, I noticed that it requires me to choose between bootstrap, Vue or React!

I know that I can edit the front for my need... but I think it would be difficult for those who are beginners in the Laravel!

I want to start a stock management project, but before starting, I want to get better informed about this issue of authentication in Aravel, because I had some doubts regarding this..
Since the Laravel provides a base structure implemented with a clean design!

I’m sorry to doubt you guys, it’s just that I couldn’t summarize!

Answer 1

Laravel’s standards should be followed and to facilitate the artisan which has several commands, for example, for model creation, for Factory, for controller, for Migration... Using the commands the created structures are maintained.

failed_jobs is exactly what you said, a table for the jobs failed, not part of authentication as long as you don’t use email verification or password reset with sending emails using queue.

The authentication of the Laravel helps a lot, ta everything ready, hardly you will have a different authentication flow than that already comes in the Aravel and sometimes that I needed to change something only needed to overwrite one or other method in the LoginController.

I have nothing to complain about the package laravel/ui, If you do not use frontend it will configure everything you need to start using Vue or another framework that it supports. If you use a frontend and know the dependencies that are not required for your project, simply remove them after the installation of laravel/ui.

Anyway, everything you asked about is in the documentation, don’t be afraid to read it, it’s great documentation. If you prefer a course, there are several on youtube like this https://www.youtube.com/watch?v=376vZ1wNYPA.

I hope I’ve helped.