How do Backend and Frontend developers interact?

Question

css

Hello, I am engaged in layout, development of not complex sites, most of the tasks from the field of frontend development. But I don’t understand how Backend and Frontend interact.
For example: a frontend developer builds a project on gulp and then gives the finished project to the Backend developer, and he already continues development. I see it somehow. Am I seeing right? If it's not difficult, tell us how this happens or share articles where you can learn more about this.
I want to do frontend development, but initially only one question is how to then interact with the developer of the other side, what do you need to know for this?

Answer 1

All layout is developed in a separate repository, which is connected to the main project using composer or bower. This project should have a *.json file that will describe all the necessary packages (jQuery, Bootstrap, etc.), php or html files with page templates, css (less, sass) and js files.
Next, Backend developers connect your project to theirs and pull up all your dependencies, set the paths to your css, js files and transfer the layout to their view files.
Backend developers should have full access to your repository so that they too can quickly fix bugs. Html templates are best kept up to date, you need to make changes not only to css but also to templates, so you will always have the latest up-to-date version of the site.
Part of the layout can be placed in the widget with its incomprehensible logic, where it will be quite difficult for you to figure out how it all works here, and there is no need.
I would also recommend tagging your template so as not to break compatibility.
those. if you write new functionality, you do not have to put down a new version every time. But if the html template has been changed or the css classes have been renamed, then you definitely need to set a new version so that Backend developers can fix everything in their templates in time.
According to this scheme, we developed one site in parallel with the layout and at the same time no one interfered with anyone. I think we will continue to use this approach.

Answer 2

A repository is created, such a structure in the current project
can be worked in parallel; the front is engaged in its part, the back is its

Answer 3

The front writes scripts to the version, the back writes its saves and selections.
Naturally, they agree on the paths and data formats among themselves ...

Answer 4

kick the designer