How does back-end and front-end developers work together on large projects?

Question

Work organization

Good evening.
I myself have never worked in a team on large projects, so there is no understanding of how teamwork still takes place, where back-end and front-end developers are involved.
Here, let's say, the front-end worker typeset the layout of the main one. He has node.js locally with all sorts of gulp / wepback, etc. He does all this automatically and when he finishes, he gives his cherished index.html and main.min.css backenders.
Let's assume that the backend is in php/laravel. Backenders take the layout and use it in their own needs, realizing the output of information from the database through blade templates. The next day, let's say you need to add new blocks to the main one. The layout designer typesets them in the project that he did yesterday, and gives index2.html/main2.min.css extended compared to yesterday to the backenders again. What should they do in this case? Pull out the added layout and insert it into blade templates? But what if on the third day you need to change the layout of the blocks made on the first day? Or are the frontend developers working locally with a fully deployed backend environment?
In general, I have a confusion in my head) Please clarify, who has dealt with, how does this process usually take place?

Answer 1

Different companies do it differently. I will quote my old answer on the same topic, but about Django.
There are three ways:

1. The layout designer makes a fish for each type of page, the backender puts it on the template engine. With further edits, the coder corrects the fish, the backender corrects the template. Plus in the simplicity of including the layout designer in the process, minus in the additional load on the backender. Well suited for attracting layout designers from outside.
   
2. You raise a separate server for development. Set up FTP on it. Run the necessary projects on it, issue rights only to templates. Run the coder via FTP with chroot in the project directory. Minus - you need an additional server and understanding of the templating language on the part of the layout designer. Plus - reducing the load on the backender and the ability to test edits on a live project.
   
3. Python and git are installed on the coder's computer. The layout designer clones the project, launches a specially prepared batch file from the project root, which activates the virtual environment, installs dependencies and launches the dev server. It requires the layout designer to be able to work with git (and you don’t need to hire others), and the backender to make normal applications that do not require long dances with a tambourine to launch.
   

Answer 2

since when do backenders pull the layout somewhere?)) the back writes api and requests to the database, and the front typesets, turns to the back for data and displays them.

Answer 3

The front and back are both in js, inside the same project. Inside the src folder there are two folders: app for the client application and common code for the front and back (the server uses the client code, but the client does not use the server code). The output of both front-end and back-end developers is a constantly up-to-date single project configured for one database, and they are already concentrated inside their folders.