How is front-end development organized in the West?

Question

HTML

We usually have the following scheme - first the layout is drawn by the designer, then it is typeset by the layout designer. A layout designer is also often called a web technologist, because. it works with a stack of technologies: html, css, js, etc.
But abroad, I heard, there is no such division. There is only a front-end developer. Those. he either draws a layout and then typesets it, or immediately assembles the graphic elements into a layout, without a preliminary layout (for example, I do this, it’s convenient for me). There is also a web-designer, but it's practically the same - he draws, typesets, and adds js-animation.
Is this really true or am I wrong? There will be no proofs, this is just an assumption

Answer 1

If you approach things correctly, the process is as follows:
1. Brainstorming on paper, thinking through the interface and structure and displaying in 3 versions (desktop, tablet, mobile)
2. Development of modular grids (aka wireframes) - Photoshop, Illustrator, Fireworks or chain . mesh applications and customer approval. In 3 variants (desktop, tablet, mobile)
3. Layout of a bare prototype according to these 3 variants (responsive has long been a de facto standard, not a "bonus").
4. The designer draws the design clearly according to the approved grids.
5. Changes in design, approval by the client.
6. Design layout, testing and debugging, approval.
With this approach, the processes are parallel. When there is an approved grid, we can work in 3 directions at once - the designer calmly draws a design for himself, at this time the layout designer (aka coder, aka front-end developer) creates a bare skeleton (prototype) and typesets bare content into it, and the programmer (back-end developer) can already display his part (dynamic content) in html. When the design is approved, the coder begins to "decorate" this low-level skeleton - final styles are added (indents, typography, colors, etc.).
The obligatory "step 0" should also be mentioned. For correct work, starting from step 1, you need to get real content from the client. In the process of step 1, this content, together with the client, is brought to mind, finalized and approved. In modern development, working with Lorem Ipsum is a bad form and a road to nowhere.
UPDATE:
Another bonus - when a low-level grid prototype is made, you can attach it to the CMS, and from that moment the client can fill the site (well, or our content editor). Often this is very important (if there is a lot of content).
From all this emerges:
1. A designer is a designer. His element is a graphic editor. Understanding the principles of layout and web technologies in general is a must. You don't need to be able to do something with jQuery yourself.
2. A coder / coder / front-end developer is a person who works with the client side (HTML + CSS + Javascript), transfers the picture from the designer to the code and fastens what the programmer gives him.
3. Programmer / back-end developer / just a web developer - a person who works with the server side (for example, PHP), CMS, etc.
This is the "minimal configuration" For more complex projects, the work is divided into narrower areas and specialized people appear.

Answer 2

or immediately assembles graphic elements into a layout, without a preliminary layout (for example, I do this, it’s convenient for me)

I feel sorry for you, you can't do that.
In the west, there are also front-end (layouts) and designers.

Answer 3

Front-end developer in Central and Western Europe is an understanding of the basics of web design, all aspects of layout and programming on the client side (there may be branches). But in the states it is quite often implied that a web designer should be able to typeset.