Why is the Webmaster constantly indignant when he puts pages on Bootstrap on joomla?

Question

CMS

Hello! While working on the project, I do the entire client part of the development using the bootstrap3 framework. After the development is completed, I transfer it all to our web master who puts the site on cms, mainly on joomla. And almost always he is indignant about Bootstrap, explaining everything by that there are a lot of extra classes, everything superfluous, incomprehensible, that it is difficult for him to put on joomla due to the fact that bootstrap classes are prescribed, etc. Then it starts that the design is not made according to the bootstrap markup, so he insists that I not use it and off we go went further. And thus chaos begins in the office about the fact that I use this framework, although I know very well that it is clearly not superfluous and it has more pluses than minuses using it in development.
Maybe someone had a similar situation or similar to mine to express their point of view, well, suggest what to do in this case, who is right and who is wrong?
Thank you for your attention!

Answer 1

Using bootstrap for casual projects (even online stores) is like trying to get to the nearest store around the corner using a fast car or plane.
All these gadgets that bootstrap is stuffed with will never be useful on 99.5% of sites.
For example, bootstrap requires the use of additional reserved classes, which, it would seem, speed up the layout, but in fact, interfere with another person (not familiar with bootstrap) and make you sweat a lot to understand all these classes.
95% of layout designs are not drawn on a grid optimized for bootstrap layout. Half of these layouts are drawn without any grids at all. Here one more point pops up - it turns out that we are trying to shove the bootstrap into layouts that were drawn without bootstrap at all. Most designers don't know anything about bootstraps at all. It's good if they know how to use grids correctly.
I can list the reasons for the webmaster's dissatisfaction for a very long time. I myself am against the use of bootstrap in ordinary sites. Bootstrap was created for developing interfaces - for them, you need to use it.
There is only one conclusion: do not use bootstrap when working in a team with people who do not work with bootstrap. It annoys everyone who hasn't read the documentation for it. And those who read the documentation and decided that using bootstrap is a perversion is also quite a large number.

Answer 2

Let's start with the fact that the work of the "webmaster" was supposed to remain in the zero.
Well, he can be indignant because pulling on the layout is a stupid, uninteresting job for anyone.
If the designer does not draw on the grid, this only indicates the incompetence of the designer in general and in the web in particular.
Bootstrap is, of course, designed more for prototyping. But for simple sites, it is prototyping, in fact, that is needed. There is nothing like that to use it for tsms.
Bootstrap is, nevertheless, the simplest framework, because it allows you to do a lot and it probably has the best documentation. A person who "couldn't figure out the bootstrap" is sad. If a person comes to html, then knowing at least a superficial knowledge of bs, foundation, semantic-ui, pure-css should already be the norm
. Bootstrap developers say to use the classes row, col- visible- hidden-, etc. - Not recommended. It’s better to do some extend, include using the preprocessor, so that you get a class, for example, articles, which included, among other things, .row, and in it the article class that would contain .col-xs-12 .col -sm-6 .col-sm-4 .col-md-3 .col-lg-2. In this case, the markup is clean and changes more and more centrally.

Answer 3

If you don't need a grid, but need other bootstrap features, build your own bootstrap, without a grid.

Answer 4

Hello. Nobody is right, nobody is wrong.
Pay attention here. Perhaps you are not typing according to the ideology of the framework
Maybe this is the reason, maybe you should make the layout more understandable
Bootstrap is really cool, but you need to use it wisely, yes

Answer 5

I will assume that due to the specific functions of the CMS Joomla , it is difficult to generate the required HTML . This one is like with Wordpress functions like wp_nav_menu(); , which generate monstrous HTML already with their classes, and in order to replace them with what the layout designer brings, one who pulls the layout on the CMS has to think.
Conclusion: Frontend and Backend should work together, and agree on some rules for writing code for certain layout elements, well, at least the Frontender should find out which CMS they will use for layout.

Answer 6

in short, the problem is in the gasket between the designer and the programmer))
if the designer draws the layout without taking into account the bootstrap markup, then why use it (bootstrap)?

Answer 7

"... a lot of superfluous, incomprehensible ..." - that's the key phrase. It seems that a person simply does not understand what a bootstrap is and what it is eaten with. Then it would be worthwhile for him to tighten up his knowledge a little.
On the other hand, if initially the design layout was not drawn according to the grid, but you are laying it out in a rigid grid, then you will almost certainly break the layout conceived by the designer. To what extent this is acceptable in your production process - you know better. So there is probably some justice in the webmaster's indignation

Answer 8

Never used it and don't intend to. Why the extra code that will load the page?

Answer 9

Try Susy