Answer the question
In order to leave comments, you need to log in
How to transfer the project to the back end?
In general, the problem is this.
I want to abandon the bootstrap but connect its grid to my written framework.
I want that there were no bootstrap classes except for the grid and the container.
I type in BEM.
Now the question itself: What if almost every time when transferring layout to the back-end, programmers complain that there is no bootstrap? And even if they include bootstrap, bootstrap will break my styles.
For example: etc.
There are such classes in the bootstrap and it is they who will kill or add their own styles on top of my styles.
Have you experienced this? .btn, .pagination, .breadcrumbs
Answer the question
In order to leave comments, you need to log in
If bootstrap is specified in the TOR, then bootstrap should be in the work performed - and nothing else. If there is no such requirement in the TOR, then what are the claims?
To use the names of classes in the layout that coincide with the names of the classes of the commonly used library is a very bad tone: the same rake that you stepped on on a grand scale. Is it really more difficult to rename the names of your classes once than to correct the consequences of your erroneous decision from time to time?
If you knew that they wanted a bootstrap on the backend, then you should have taken this into account when laying it out, and accordingly take into account how to name your classes. And just by whim, you create problems that can lead to an increase in the cost of the product. The employer will not experience joy from this.
A good performer is one who realizes all wishes, especially since he is paid for it.
So add a bootstrap and rename the classes so there are no name conflicts.
almost every time when passing the layout to the back-end, programmers complain that there is no bootstrap
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question