How to organize the work of the frontend team through git?

Question

git

There will be 2 browser layouts (desktop and mobile) in the work, due to their almost complete difference, each has its own repository. The popular https://nvie.com/posts/a-successful-git-branching-... is chosen as the development model. For the publication of each, there will be 2 sites, one belongs to develop (dev-desktop.example.com), the other to master (desktop.example.com).
Questions:
1. Having 2 different front-end repositories, how to ensure access to the same layouts, for example, a news card in the list?
2. The repositories will contain only source codes and service (webpack settings and the like), who and how performs compilation and deployment to the site corresponding to the branch?
3. How to transfer the result of compilation on the master branch to the backend repository?

Answer 1

1) As an option, make a mono-repo, one repository for desktop and mobile
1) a) In general, ideally, make mobilefirst design and expand it to desktop so that you don’t have to do two layouts, but get by with media queries, but each Doda has its own method.
2) Read about CI / CD, Docker, Kubernetes
https://bitbucket.org/atlassian/atlassian-streams/...
https://about.gitlab.com/product/continuous-integr...
We have tests for example and deployment after successful tests is performed automatically by merging into the master
3) Again, a monorepo for the front and backend, the back works on tasks that are already deployed from feature branches to the general dev and builds the front for itself (in the documentation, they can be described how to run, for example, npm run build front)
Merging from featurebranch to dev and from dev to master is good to do only through merge requests.