Conclusion

In this project, I have created Laravel contact application and fully explained it here in the blog. I explained what development environment I have used, introduced lightly the Laravel and its tools. Then I showed how I have created Laravel project and installed Laravel/ui package with bootstrap scaffolding fronted. I have written short descriptions for important topics including authentication, authorization, eloquent ORM, model, middleware, blades, routing, with explanation as to where and why they were used in this Project. Besides authentication, I have used several methods of authorization such as Gate, middleware and I have applied authorization in CRUD methods inside ContactController. I have connected the project with database through .env file and created corresponding model for users and contacts tables, and from migration I have set the table filed and their properties. I have explained almost all the method, helper, or function that I have used throughout the project, for example in Controller, in blades or anywhere else.

At the start of the project, I did not have any skills in Laravel framework except in the coding due to having designed a website in PHP in second year of my college. However, this time I have learned a lot and now I feel more prepared, confident and ready for next project. Writing the blog contents was very effective and helpful. In terms of practical work, my Laravel skills improved as well as in writing posts and researching essential areas for my knowledge and understanding. I have gained a deeper understanding of Laravel Tools, Authentication, Authorization, Route, Middleware, Eloquent ORM, Database, email verification, and so many other important Laravel topics.

If I were to complete this project in the future, I would do it differently by choosing react scaffolding blades template and for authorization I might prefer policies rather than gates, because policies organize authorization logic around a specific model or resource. this way from one place i can apply authorization over all of the methods. Furthermore, for authentication I would prefer Jetstream instead of Laravel/ui, because Jetstream provide very good designed application scaffolding includes login, registration, email verification, tow-factor authentication, session management, API support via Laravel Sanctum, and etc. To restrict file access from direct URL, I would create file storage outside public folder. Also, I would spend more time on developing admin with crud functionality.