The subject managed a micro team (8-10 people) when participating in the Laravel5.1 project. The responsibilities of the front-end and back-end personnel were separated, but the following problems were encountered:
Laravel front-end uses blade template, which is PHP. When the front-end progress is greater than the back-end progress, it is not easy to debug (the back-end has no relevant routing and logic);
Controller->View transmits data. Does the specific data display responsibility belong to the front end or the back end? What writing standards should be followed for the front and back ends?
After using blade template, the readability and maintainability of html are slightly reduced. How to solve it?
Has anyone encountered the above problem? How was it resolved? Thanks!
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
What I think is the separation of front-end and back-end is this
The backend is responsible for producing the API
The front-end uses JS to implement view
If it’s like what the questioner said, it’s more like the front-end staff is responsible for blade cutting
To give the questioner a reference on my current development status of Laravel 5.1 project
The same feature is developed by the same person, backend and blade template
The backend prepares data for the frontend, and the writing specification is currently
. The variable naming is unified
. Throw the processed data to view (view is only responsible for display, not too much processing of data)
I think blade is just an extension of php template, and does not support variable assignment (which is quite annoying). If the readability is better, you can try other templates, such as tale-jade in the jade series, but it seems to be quite new. of