Why should a designer adapt to a coder in the case of Bootstrap?

Question

Design

I often hear that designers get scared when they are told that they should design a website with Bootstrap in mind. Also, I often hear layout designers tell designers that the design is not suitable for Bootstrap due to the specific designer grid.
But it's pointless. The grid is essentially created for each project separately. Yes, to speed up the process, they often take 12 columns, 70px - a column, 30px - the distance between the columns, and that's it. But that's not the rule.
If the designer has made his own grid, then the layout designer can go to the Bootstrap customization page, specify as many columns as the designer did, and specify the length of the interval between the columns as the designer chose, and then download the resulting version.
The grid is a design assistant, not a constraint. I am wrong?

Answer 1

There is also the concept of productivity. To the layout designer to switch to non-format? This is time consuming and doesn't make sense 90+ percent of the time.
Moreover, Bootstrap is inherently responsive. On responsive dimensions, also rewrite the grid?

Answer 2

You are absolutely right about everything.
And if you, as a designer, have a well-thought-out layout at the output, even if it is “non-standard”, a normal layout designer will not have any, I emphasize, there will be no problems with layout.
On the other hand, some commentators are also right in their own way. If the first place for the project is the price, then it is better to follow the beaten path.
The bottom line is that you have to choose: consumer goods or author's work. And the choice, of course, is up to the customer.

Answer 3

Also, I often hear coders telling designers that the design is not suitable for Bootstrap due to the specific designer grid.
But it's pointless.

and a grid of unequal stripes or a grid for each page?

The grid is essentially created for each project separately

no. The grid is either part of the design style or it is customized after the fact. It is the second option that fits poorly into any layout

If the designer made his grid

and the designer made a pdf with a description of the grid and uses it on all pages?

the coder can go to the Bootstrap customization page

layout designer will edit sass variables

The grid is a design assistant, not a constraint. I am wrong?

not right. Limiter. Because designers don't like it or use it randomly

Answer 4

It is not the task of some people to understand the principles of work of others. So it doesn’t matter to the designer and / or the customer how the third one will make up the layout handed to him. This decision remains only with the layout designer. Therefore, it is better to be a layout designer and draw + make layouts yourself =)

Answer 5

Because 12 columns is the best option, it's simply not better. The alternative is only 24 columns. Everything else is a perversion. Only 12 (and 24) is evenly divisible by 2, 3, 4 and 6. And web design is a craft in many ways. No wonder a good designer should be able to typeset.
If the number of columns is different, then the grid will no longer be from the bootstrap, at most, mixins from it.

Answer 6

I don’t know, someone tried to spit in the face of the layout designer, higher in the comments .. well, God help me)
let me say, if it’s a rogue project, then I’m too lazy to shovel bootstrap variables / constants in order to roll normally to poop design (also to low-budget work) .. I work with large offices and with large sales .. no matter how cool a designer is there, he can’t always resist and say something .. then the gradients on the buttons are not the same .. then the indents between inputs are not the same as you customized it globally in variables.
I have been doing markup since 2008. I had only 1 project, on the basis of which it would be mono to make my own framework. everything was clear and pixel for pixel. and so .. usually .. you look at the indents .. there are some, on the inners - others ..)