Answer the question
In order to leave comments, you need to log in
The results of the layout designers' work - what to expect?
Good afternoon!
We ordered a design + layout, received a set of html files, where everything looks beautiful and "as it should be".
However, when I started to screw this layout into Laravel, I found out three problems for myself:
1. Beautiful blocks in which multiple selection is made (filtering panel, for example) are ordinary links to which styles are hung with JavaScript, imitating enabled checkboxes.
2. On the page, the appearance of a form is created - there are fields and a "Submit" button, but there is no markup for the form in the code, only a few separate inputs.
3. I tried to use my own checkboxes, but it turned out that most of the standard elements are predefined in the styles, in the end everything looks terrible.
4. Bootstrap does not work for the reason described in paragraph 3.
5. Some links simply do not click because of paragraph 1, you have to go into javascript, remove onclicks.
Actually, the question is:
What is described is a normal result, usually obtained from a layout designer? (ordered "just layout", not in relation to the framework), or is it a hack on the part of the layout designer? You just get the feeling that in our case, the layout is something designed to show the customer in the browser how beautiful everything is, without implying the programmer's work in principle.
Answer the question
In order to leave comments, you need to log in
A very strange question, you are not satisfied with the layout, it is obvious that the result is not normal. This is where you decide as the customer. Semantics is also a part of the layout, you have the right to make a claim for it, it was necessary to immediately inspect the written HTML and CSS, otherwise something worse could end up "turning out".
Actually, if the "programmer's work" is not discussed in advance, then the layout should not imply it, but what you said is semantic errors (points 1,2) and poorly written styles (point 3), this does not apply to the backend.
As a person who typesets himself and tries to make sure that the customer can easily finish the forms, something else without my intervention, I will say: no, this is not normal.
I often have to get involved in work on projects that were laid out like this, I often see:
1. Tags are inserted instead of buttons, but these links are described in styles, not buttons. As a result, having corrected the link to the button, it will no longer be styled with us. This should not be.
2. What should be typeset in blocks is molded with pictures.
3. Checkboxes and stuff are styled by id, not by class.
4. Other jambs, when styling is set strictly by id, and not by class or wrapper.<a>
However, in addition to the hack work from layout designers (a person must himself understand that the site will be 100% corrected without his participation), there is a share of complaints from customers. Unfortunately, not everyone considers it necessary (or simply does not know) that all these points should be discussed. What to typeset with pictures, what with blocks, etc.
If a person who has made more than one hundred layouts most likely knows most of the nuances (and with experience comes the desire to write everything so that later you can expand the functionality yourself, if you have to do it), then a person who not so long ago hit the layout , will do everything quickly so that "at least it works", will receive money and be forgotten. Knowing how our people like to save on everything they can, what usually happens is what you described.
To answer the question "Is the result normal," you also need to answer the question "Did I pay enough to get a normal result." Therefore, until you write how much you paid, it is difficult to answer the question. Not enough data.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question