I love coverage of the fundamentals. Often there are a few tweaks (or things you need to know) that are not covered in the docs. Plus seeing code working (as opposed to an isolated snippet) makes it easier to understand. Thanks for your work.
I would like to see more of your ideas for this series! It helps to quickly get a project off the ground. Most of the time the basics are the same for the various projects. Then one can focus on solving the reason for the project. :)
Thank you! Great idea! The two future upgrades that I think are more popular are: emails invitations and the use of Spatie-Permissions. Maybe a "user dashbord" to update his data, change password, would be a common idea.
What about another level on this scheme? Master admin > super admin > admin > user The use case is a system to manage clinics. Where i am the master admin, there are clinic owners who may have multiple clinics and are the super admins then you have the managers of each local clinic (admin) and the users of that clinic (staff, doctors, patients)
That would require a separate long video, can't answer in a comment, sorry. But the principles are the same, I can't shoot a video for all possible roles situations.
I love coverage of the fundamentals. Often there are a few tweaks (or things you need to know) that are not covered in the docs. Plus seeing code working (as opposed to an isolated snippet) makes it easier to understand. Thanks for your work.
These types of roles/team is indeed popular, I've worked in a project with a similar structure as well!
Thank you for all the videos you post. The moment I start my work as dev I will send a postcard, Povilai :)
I would like to see more of your ideas for this series! It helps to quickly get a project off the ground. Most of the time the basics are the same for the various projects. Then one can focus on solving the reason for the project. :)
Then help me with more ideas for such topics :)
Thank you! Great idea! The two future upgrades that I think are more popular are: emails invitations and the use of Spatie-Permissions. Maybe a "user dashbord" to update his data, change password, would be a common idea.
Maybe planning and registering time for tasks? So you maybe have a calendar of to-do's and a registration of hours worked?
I was thinking more about some functionality that EVERYONE would need. A calendar seems like an optional feature to me. But thanks for the idea!
It would be great to see some content from you about using external libraries for roles and permissions
I do have already quite a lot, search on my channel.
Thank you sir.
What about another level on this scheme?
Master admin > super admin > admin > user
The use case is a system to manage clinics. Where i am the master admin, there are clinic owners who may have multiple clinics and are the super admins then you have the managers of each local clinic (admin) and the users of that clinic (staff, doctors, patients)
That would require a separate long video, can't answer in a comment, sorry.
But the principles are the same, I can't shoot a video for all possible roles situations.
Good
please more fundamentals I am coming from CodeIgniter and i am very familiar but still have some questions of things are the way they are in Laravel
The link to your second channel is not working. You have a - at the end ;-)
Thank you, fixed!
Please,
I am really curious about the tool on the bottom. It seems Laravel specific. What's that?
Probably it's Laravel Debugbar
@@LaravelDaily thanks a bunch.
I'm using spatie/permissions