What are the current requirements for the layout?

Hello! Trying to collect a check-list, relevant requirements for layout.

The list, which you can give to coder before beginning work on the project and say they have these rules/requirements.

Let's joint forces distribute?


  • adaptive cross-browser, semantic coding (HTML5)
  • the use of preprocessors
  • use one of the architectures BEM (or SMACSS)
  • Pixel Perfect layout
  • GIT, GULP SVG sprites
  • Testing of their work
  • Code optimization

Help to Supplement/correct?
July 8th 19 at 16:38
9 answers
July 8th 19 at 16:40
Pixel Perfect this thing is quite murky.

On the one hand, annoy some web designers who do not "see" how the elements float on plus or minus a few pixels. The designer spent a lot of time, licking and balancing margins, and him "who cares?"
On the other hand, it is equally annoying opposite extreme, when literally dig to the inevitable microporosity.
Absolute pixel perfect in the current technological conditions is impossible. Different engines rendered different. But if the aim were, relatively speaking, almost pixel perfect - Yes, okay.

Moreover, the designer must clearly understand where the error is a technical inevitability, and where his own carelessness. Errors of the second type, of course, it must be possible to eradicate.
I agree, almost more true. But I have encountered many times when the coder started to include designer. I was very nervous :) - kathleen_Larkin75 commented on July 8th 19 at 16:43
: Do you want a responsive and pixel perfect, but you don't like it when a designer includes the designer? Then draw individual designs for all screen resolutions. But it is no good. - Leora commented on July 8th 19 at 16:46
Possible, if you give all the people of the world devices with the same fonts, OS and video cards with specific drivers. - rhianna_Yost commented on July 8th 19 at 16:49
that "no where is no good"? - kathleen_Larkin75 commented on July 8th 19 at 16:52
July 8th 19 at 16:42
Oh! thanks for the link - kathleen_Larkin75 commented on July 8th 19 at 16:45
July 8th 19 at 16:44
Already have a checklist layout!
July 8th 19 at 16:46
You question is strangely worded. The ability to test your work - it is not a requirement to the layout, and the requirement for the applicant to work. Maybe that's what you mean?
Why? Every web designer needs to take before work to test it. That would be on different browsers, including mobile, neither of which is no where wasdale - kathleen_Larkin75 commented on July 8th 19 at 16:49
Well, you yourself wrote - coder. And in the question text - layout. If you want to layout tested - the requirement for programming will sound "tested on all devices and browsers". The part of points - to the same. - Leora commented on July 8th 19 at 16:52
: corrected :) - rhianna_Yost commented on July 8th 19 at 16:55
July 8th 19 at 16:48
For the optimization of code can introduce a quantitative measure of "green" values in pagespeed.

Of course, not all items from the list, pagespeed worth vitrociset at the layout stage, some only make sense on a combat server. But if the GIT project, then throw a template on GitHub Pages and test the speed would be great.
July 8th 19 at 16:50
Preprocessors and collectors - it's whatever you like A little hand shovel - forward.
Forgot about the validation code (within reason).
the use of preprocessors and collectors is already standard for any coder
the inability or unwillingness to use them is a big minus to this specialist, it is one thing to develop, another thing to maintain. When you transfer a project to another specialist, it will be much easier to understand the structure of the file preprocessor, rather than look for the lines in a single file in a 5K row. - kathleen_Larkin75 commented on July 8th 19 at 16:53
: to a point. With proper structure and approach, the project easier to maintain. And if the project is transferred to another coder on the support, it is easier to understand - Leora commented on July 8th 19 at 16:56
: I have 3 years of use preprocessors. But no need to make a fuss. Someone on sass makes someone less or stylus, and someone has to do in postCSS. - rhianna_Yost commented on July 8th 19 at 16:59
: so in fact I never wrote about you, and about requirements for a potential coder - kathleen_Larkin75 commented on July 8th 19 at 17:02
July 8th 19 at 16:52
Let's distribute, you formulate the task, and we "throw", without a problem in all of this makes no sense.
You are right. Elaborated - kathleen_Larkin75 commented on July 8th 19 at 16:55
July 8th 19 at 16:54
and the most simple. Call you classes in normal. A bunch of typography seen classes named k1 l2 l3.... z92 and then they sit for weeks the feedback form
this designers. - kathleen_Larkin75 commented on July 8th 19 at 16:57
July 8th 19 at 16:56
What about BEM, I would argue. I myself am a server part are doing and this popularity BAM I already rather annoying. As you can see this puttee of the classes on every paragraph, picture, link, list - want to puke.

Documentation BEM States that "members are part of a unit and have no functional meaning outside the block". So why the hell to sculpt them as separate classes. If they have no meaning outside of the block, why not register styles using inheritance?

The use of ideology BEM for blocks, fine. The elements of the last level is idiocy. It's not convenient, a lot of problems to use. Again, under the visual editor does not adapt. And when the benches talking about it, they all link to this BEM send. Annoying.
For the visual editor just the same through inheritance is done. Here wrote for these purposes a small framework https://github.com/AndreyMyagkov/Typography And at the expense of the rest - you did not understand the meaning of BEM is a flat element tree, in order to avoid inheritance. For what would any element can be moved to another unit or change it the tag, and edit everything solely through CSS. - kathleen_Larkin75 commented on July 8th 19 at 16:59

Find more questions by tags LayoutAdaptive designHTML