Parallelization of the layout process between layout designers?

Question

Project management

Hello!
The question is. How do you or your company distribute / distribute the project between layout designers.
For example, there is a task to make up a project (there is nothing, there is only psd), you need to finish it in a short time, there are three typesetters. How to do so (what technologies to use) so that styles\scripts\other files do not overlap each other, there are no conflicts and, accordingly, time is not wasted on their resolution?

Answer 1

Distribute work piece by piece.
Any layouts can be disassembled into the following components and stages.
All work is carried out immediately in it. The more often commits are made, the sooner problems will come out and be fixed. Each component has its own css/less/sass file to make it easier to manage the code and avoid merge conflicts.
- Typography and styles for content (tables, quotes)
- Form elements + validation styles
- Decorative graphics (icons, dice)
- Modular grid (immediately responsive)
Each layout designer is responsible for his piece of work and creates a demo page with a list of components that he made up. The work of layout designers does not overlap.
- Navigation
- Feeds of news, events, blog posts, search results, anything
- Typical forms (login, registration, search)
- Tabs
- Sliders
- and so on
Each layout designer makes his own category of elements and creates a demo page with a list of components and all their modifications. The work of layout designers almost does not overlap, but each component is based on the styles written in the first stage.
After these two stages, the team has a UI-kit of the project ready.
The work is distributed page by page. Each layout designer copy-pastes blocks from the UI kit and fills them with real content. At the end, the team evaluates where what else needs to be done.
Based on the problems that emerged in the third stage, each layout designer finishes the blocks for which he is responsible.
In general, it is necessary to typeset from simple to complex, from general to specific, and at the same time in independent blocks. Then several layout designers can easily get along on one project, not interfere with each other and not break each other's code. Atomic Design , ITCSS and many other methodologies
talk about all this .

Answer 2

BEM + git pull + one makes the header, another footer, third sidebar, etc.

Answer 3

To do it right off the bat, without shared repositories? Scatter through the DOM hierarchy - one makes the layout (skeleton, rubber, adaptability, sections), the other typeset the insides of the sections, and the third deals with decorative things (form elements, icons, design graphics). So at least the code style and selectors won't get too confused.
It is very difficult to enter BEM right off the bat. Yes, and it is redundant for small projects.

Answer 4

If you copy from the desktop to the server, then

[[email protected] ~]# strace ./server                                                                             
execve("./server", ["./server"], [/* 23 vars */]) = -1 ENOEXEC (Exec format error)                              
write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec format error                                 
) = 32                                                                                                          
exit_group(1)                           = ?                                                                     
+++ exited with 1 +++                                                                                           
[[email protected] ~]#