How to organize joint work of layout designer and programmer (Pug + Laravel)?

Question

Work organization

There is a project on Laravel. The coder works for Pug. In the initial development of a view for Laravel, everything is simple: you take the generated html and remake it for blade templates. But what if changes are made to the layout? How to combine changes? Line by line compare original layout and blade templates? It seems to me that there should be some more reasonable way... Does it make sense to pass the docker image to the layout designer and introduce him to the blade templates in order to eliminate the problems of a subsequent merge?

Answer 1

First, it makes sense to do it all through git.
And then either explain blade to the coder (which is better, because now you actually have 2 template engines and the same work is done twice), or build some kind of system:
- when the layout changes, the coder changes pug / html and makes a pull request
- the programmer reviews the changes and makes the appropriate edits to the blade template