The parallelization of the process layout between the coders?

Hello!
The question is. How do you or does your company distribute/distribute the project between coders.
For example, there is a task to make up a project (nothing, only psd), you need to finish in a short time, there are three of the designer. How to make so (what technology to use) to styles\scripts\other files do not overlap each other, there was no conflict and, accordingly, do not spend time for their resolution?
July 9th 19 at 11:14
4 answers
July 9th 19 at 11:16
Solution
Distribute the work component.
Any layouts can be disassembled into the following components and stages.

0. A shared repository for the project.
All work is done from it. The more commits are made, the sooner will come out and will fix problems. Each component has its own css/less/sass file to make it easier to manage code and avoid merge-conflicts.

1. Basic building blocks:
- Typography and styles for content (tables, quotes)
- The elements of the forms + styles validation
- Decorative graphics (icons, dice)
- Modular grid (just responsive)

Each coder is responsible for its own piece of work and creates a demo page with a list of features that he laid out. The work designers do not intersect.

2. Recurring components:
Navigation
- News, events, blogposts, search results, anything
- Standard forms (login, register, search)
- Taba
Sliders
and so on

Every coder does its category of elements to create a demo page with a list of components and all their versions. The work of coders almost never intersect, but each component based on the styles written in the first stage.

After these two phases the team is ready, UI-kit project.

3. Pre-Assembly of all page templates with real content

The work is divided in pages. Each coder copy-paste blocks from a UI kit and fills the real content. In the end, the team assesses where what else needed to be done.

4. Rare custom components and modifications

On the basis of the issues that came out in the third phase, each coder dopilivat blocks, for which it is responsible.

In General, it is necessary to impose from simple to complex, from General to specific and independent units. Then, a few web designers can safely coexist in one project do not interfere with each other and not break each other's code.

All this Atomic Design, ITCSS and many other methodologies.
July 9th 19 at 11:18
Solution
Is it possible to use BEM and bootstrap? - ansel.Donnel commented on July 9th 19 at 11:21
:
We do not use bootstrap.
But there is on the Internet examples:
g.zeos.in/?q=%D0%91%D0%AD%D0%9C%20bootstrap - Weston98 commented on July 9th 19 at 11:24
: can be used. - Bobby commented on July 9th 19 at 11:27
: can tell you in the end, the bootstrap is more pluses or minuses, when considered in the context of BEM? - ansel.Donnel commented on July 9th 19 at 11:30
: this is the scale of your development depends. I think 2 people can negotiate better and without BEM. - Weston98 commented on July 9th 19 at 11:33
: cons had not noticed for himself. You can safely use. As here properly speaking, BEM for small projects to use for what. Well, git of course. - Bobby commented on July 9th 19 at 11:36
You three coders still on bootstrap the project was going to cut? facepalm - Rowena commented on July 9th 19 at 11:39
all not so easy. Of course, if you are curious about can explain. Half of the project already exists and works. The other half of the project was made by the designer. The first half is made solely on buttrape. In the new part bootsrap - not to break the continuity of the technology and not bother with the mobile layout. But at this stage the issue with the project is resolved well (with your permission, I will not describe how). What would you do in this case? If you have had a short period of time, the finished part of the project, a few web designers and the volume of work is not feasible for one? - ansel.Donnel commented on July 9th 19 at 11:42
July 9th 19 at 11:20
BEM + git pull + the one doing the cap, the other basement, the third sidebar, etc.
July 9th 19 at 11:22
So with the move, without the common repositories? Spread across the DOM-hierarchy - the one doing the layout (skeleton, rubber, adaptability, and partitions), different typesets already inside sections, and the third is decorative things (form elements, icons, design graphics). So at least the code style and the selectors will not be particularly confused.
In BEM immediately very difficult to enter. And zbytecne it for small projects.
>> In BEM immediately very difficult to enter. And zbytecne it for small projects.
Both assertions are not true. - ansel.Donnel commented on July 9th 19 at 11:25
Officer Of Yandex? Yeah already got all these freaky Bamom. They themselves have scored on him! - Weston98 commented on July 9th 19 at 11:28
:
>> In BEM immediately very difficult to enter.
>> Yes, already got all these freaky Bamom.
Well, obviously, what is really there :) - Bobby commented on July 9th 19 at 11:31

Find more questions by tags LayoutProject management