Laravel Community module Development

my site is about university rankings, and we are looking to add a community module to the site where users can connect, share, and engage and most important ask questions since the platform goal is to help students find dream university, so we are following the way of Linkedin mostly with adding the Asking things, The end result of your work must be 100% functioning module with success walkthrough process, which means the test of the end result we must be able to use the module successfully please check the detailed documents General Rules: 1. Do not share your email address with us at all even for github or anything, 2. Do not cuts corners to save time, best practices and standard must be followed 3. when it comes to choices please get back to us, since we don't accept unorthodox choices, and we always study all options to come up with the optimal choice. Do not make any choice on your own. 4. Coding Standards: You must follow our style of coding, template, designs, system core to achieve your task, please check Coding standards below. 5. You must follow Laravel and Vue.js standards to achieve your work please check Coding standards below 6. Workaround to achieve any point is not allowed. 7. Eloquent relations 8. public_html/routes/[login to view URL] API should contain all api controllers, and all routes in the router that lead to api 9. DataController should be be on separate classes 10. Use helper classes 11. Implement collections in models to saturate view data fields 12. Implement strong variable typing 13. Implement helpers , simple code refactoring. 14. Do not Repeat switch statements, Move to helper 15. Routes must be cleanly coded or using separation of concern for API routing of API auth. 16. the controller should use a collection instance that then returns the data necessary to populate the view. 17. Routes to get data should be through the API auth, and load controllers in the API folder 18. Every function in DataController...should be in it's own file, under App,Http/Controllers/API, 19. You must start on these tasks on the sequence as listed, once you finish a point you must take approval and push your code to github, do not jump on the next task without finishing the first one, we are using this system and we want to use the new extra features immediately once it done 20. You need to upload on daily bases your work and source code on so we can check 21. You must finish all the points, in order to request payment, you are responsible for the entire project 22. commitment to the time frame as I will allow only MAX 25% of the agreed time frame on each task 23. We are looking for long relationship on this project If we face any difficulties managing this project with you in terms of task understanding, handing over quality of work coding style it can lead to termination of the relation 24. Everything must be done within coding standards not your own standards, there is a senior developer going to check every single line of your code and he has the right to reject and ask for corrections.