What are the current layout requirements?

Question

HTML

Hello! I'm trying to put together a checklist of current layout requirements.
A list that you can give to the layout designer before starting work on projects and say - we adhere to these rules / requirements.
Let's throw together?
I'll start:

• cross-browser adaptive, semantic layout (HTML5)
  
• use of preprocessors
  
• using one of the BEM architectures (or SMACSS)
  
• Pixel perfect layout
  
• GIT, GULP, SVG sprites
  
• Testing your work
  
• Code optimizations
  

Can you help me to add/correct?

Answer 1

Pixel Perfect is a tricky business.
On the one hand, some layout designers are annoying, who "do not see" how the elements float by plus or minus a few pixels. The designer wasted a lot of time licking and balancing the margins, and to him "who will notice this?"
On the other hand, the opposite extreme is no less annoying, when they literally get to the bottom of the inevitable micro-errors.
Absolute pixel perfect in the current technological conditions is impossible. Different engines render differently. But if you strive for, relatively speaking, almost pixel perfect - yes, that's good.
Moreover, the layout designer must clearly understand where the error is a technical inevitability, and where his own inaccuracy. Errors of the second type, of course, should be eliminated as far as possible.

Answer 2

Your question is worded in a strange way. The ability to test your work is not a requirement for layout, but a requirement for a job seeker. Maybe you meant it?

Answer 3

To optimize the code, you can enter a quantitative measure: "green" values ​​in pagespeed.
Of course, not all items from the pagespeed list should be tweaked at the layout stage, some make sense only on a production server. But if we are already on a GIT project, then uploading the templates to GitHub Pages and testing the speed would be great.

Answer 4

Preprocessors and assemblers - it's more convenient for anyone. If you want to shovel your hands - go ahead.
Forgot about code validation (within reason).

Answer 5

Let's throw, you formulate the task, and we "throw", without a task there is no point in all this.

Answer 6

and the simplest. Name the classes in the normal way. I saw a bunch of layouts and the classes are named k1 l2 l3 .... z92 and then you sit for weeks for the feedback form

Answer 7

That's about BEM, I would argue. I myself am engaged in the server part, and this popularity of BEM is already annoying me. As I see this footcloth from the classes on every paragraph, picture, link, list - I want to puke.
The BEM documentation states that "elements are part of a block and have no functional meaning outside the block". So why the hell to sculpt separate classes on them. If they don't make sense outside of a block, why not write styles through inheritance?
Using the BEM ideology for blocks is great. But for the elements of the last level - this is idiocy. It is not convenient to work with this, a lot of problems in use. Again, you can’t adapt to a visual editor. And when you tell workbenches about this, they all send a link to this BEM. It's annoying.