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:
- News, events, blogposts, search results, anything
- Standard forms (login, register, search)
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
and many other methodologies.