T
T
Treniki2016-11-25 01:09:15
Freelance
Treniki, 2016-11-25 01:09:15

How does a layout designer work?

Good day. Not so long ago I became interested in the subject of site layout, in connection with which there were several questions that I would like to get an answer from the old-timers of this profession or from those who are "in the know".
1) Website layout - is it Front-end or a combination of front-end and back-end?
2) Are there front-end developers who make up websites (pages) on pure html, css, js (I think it's the best for some kind of business card)?
3) If there are articles/images in the PSD layout indicating that these are dynamic elements that will be updated/added through the admin panel/php/something else in the future, then what does the front-end developer do in this case? Does it lay out the site (pages) strictly according to the layout with these articles \ pictures or somehow adjusts these elements to the back-end of the developer?
4) Heard about template engines. When front-end development, should you always rely on them?
5) If you received an order for website layout on freelance, does it mean that you will have to do front-end and back-end development or is it divided by different people?
6) Now any CMS for sites (WordPress, Joomla, Bitrix, etc.) is used almost everywhere to make it "manageable" (add articles, delete, comment, etc.)? Nobody invents their "bicycles" when ordering, for example, some online store?
7) Is adaptive or fluid layout already available as "default", or is this discussed separately with the customer for an additional fee?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
D
Denis Ineshin, 2016-11-25
@Treniki

1. They say "site layout". The layout is just HTML+CSS. The layout is part of the Frontend. Frontend is already programming. Here you need to have an excellent knowledge of JavaScript and the technologies around it, the layout here is just a mandatory appendage.
2. What do you mean by pure HTML, CSS, JS? For the browser, they are all clean, it's another matter that now, for example, few people write in pure CSS. This is not convenient when there are crazy LESS / SASS and other preprocessors that make the job easier. It's the same with JavaScript. Of course, everything can be written in clean language)), but this is the invention of the wheel. For a long time, thousands of libraries have been written that solve problems of varying degrees of routine. And even on a business card site, the same jQuery can come in handy if there is something to decide.
3. Depending on how you agree. Usually, with cheap development, the backend already exists in some form, and all that the layout designer does for typical text pages is to design the basic elements (lists, paragraphs, headings, tables) so that they look as similar as possible to the layout. If the content is very complex, then the backend is already customized for it.
4. Template engines are primarily dynamic single page applications or SPAs written in serious frameworks like Ember or Angular. When making up sites, they are practically not used. Of course, even here you can make your work easier, if you know Handlebars, Grunt / Gulp well, then you can assemble the layout from pieces using template engines, but that's another question.
5. Layout is only part of the frontend. The backend is made by completely different people. Such orders, where there is both layout and backend, are usually called "turnkey", although usually design is also included there)
6. Sometimes something is invented, it all depends on the experience and ambitions of the backender. Of course, this is if we are talking about freelance orders and small sites. Any large project with its own team most likely has self-written technologies for most of its tasks. This is due to the uniqueness of business processes and security (known CMS is easier to crack
) fee. But today, many people want it and need to be able to.

I
Igor, 2016-11-25
@imikh

1) Frontend
2) Yes
3) Depends on the technology, of course, you need to take into account what will be generated by the backend
4) Not always
5) As agreed with the customer
6) If the store is standard, it makes no sense to invent. If you want to make some kind of special store, then the framework will only interfere. Ozon does not work on WordPress.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question