Answer the question
In order to leave comments, you need to log in
How to separate the work of layout designer and vue frontenders?
Hello! I ran into this problem on a project.
There is a layout with a lot of logic in jquery. All logic is responsible purely for ui.
The problem is that this code is poorly implemented in SPA on vue. In other words, no way. comes out incredible nonsense and it takes a lot of time. That is, as a result, you have to write all the logic from scratch.
Based on this, the question arose - how to divide the "spheres of influence" between layout designers and front-end developers?
What should layout designers do, and what should frontend do on ONE project?
In my case, it is assumed that the frontend is a SPA on vue.
Answer the question
In order to leave comments, you need to log in
The layout designer and Frontend developer must be the same person.
If you have a person in your team who just typesets (HTML, CSS), then somewhere you are doing something wrong, it seems to me.
You answered your own question, after all.
Why is there a separate coder in the team, if the front-end developer can and does (judging by your question) everything the same? Does it speed up the development process? I don't think. Pure layout takes only a couple of hours. Essentially, you need to train Vue coders.
Since when have coders made jQuery logic?
The role of the layout designer in the presence of front-end developers ends exactly at the layout of html + css, maybe using template engines and assemblers, but definitely without any logic.
The fronts, in turn, receive the laid-out pieces and make it work fully.
If a complete symbiosis is needed, then layout designers and fronts use one template engine, and layout designers already inside the front typeset the final state, so to speak. And the fronts do not climb there at all, unlike the first option.
It seems to me - in your case - a layout designer and a frontend developer - you are, in one person. ))
If we consider a component application (in Vue, for example), then not the entire application should be typed, but a specific component, which will then be "reused". Accordingly, if there is some logic in the component, then it needs to be implemented within the framework of the vue component (and nothing prevents using jQuery next to Vue, although this is redundant - everything that can be done with jQuery is done much easier and faster with Vue and shorter).
It is quite possible that HTML/CSS layout (with preprocessors for css or templating engines, like pug) is done by one person (layout), i.e., is responsible for the static presentation, and passes ready-made templates of COMPONENTS, and not the entire page, to another (frontend- developer), which can implement some kind of behavior logic.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question