What are javascript frameworks for?

Question

JavaScript

Hello.
I have been developing for a long time and the main specialization is frontend. I know JavaScript pretty well, I write my solutions (calculators, sliders, etc.) in native JS without any problems, without using third-party plugins and add-ons.
The problem is that in large projects, confusion in the code begins, especially when the project is constantly evolving. In this regard, I want to use something more serious. I use the full BEM stack, but somehow I still don't like it. As I understand it, JS frameworks like Angular, React, Vue, etc. are well suited for this. For now, I'm
leaning towards Vue.js.
I don’t think there will be any problems with training, because. as I already said, I know native JS well and do many things on it. But I don’t fully understand how JS frameworks work, so here are the main questions:
1. Can (should) be used in regular projects when there are already more than 2 pages and there are heavy elements like calculators or complex animations, for example, on SVG?
2. What about transferring the backend to a programmer to write an admin panel on the framework? 4. If there is no need to land on the CMS, how is the administrative panel implemented?
3. What about landing on the CMS (sorry if this is a stupid question, because I already said my frontend specialization, which I know very well, and I never climbed into the server)? Also, if you know, please recommend good Vue.js tutorials. It is possible in English, because. there are no problems with it. I will be very grateful for the answers.

Answer 1

Regarding the courses, everything is quite well stated in the documentation for the framework itself, besides, it is translated into Russian.
Try it, and then vue-router and vuex .
To work with REST - vue-resource or axios .
For the admin panel, you can try this framework: https://admin.vuebulma.com/

Answer 2

vue.js seems to be well chewed on the off site.
But basically, if you implemented the admin panel on a native - what is the difficulty in transferring it to vue?
Or do you have the wrong CMS===Framework association? If the latter is the case, then the framework is more like a wrapper for convenient use, unlike CMS, where you can not write a single line of code and do something

Answer 3

You either use a well-documented and designed framework, or spend a lot of time reinventing your wheel, or you don't have a framework and a mess.
The first option is much better than the other two.

Answer 4

1. You can. Whether it's worth it is another question altogether. Having gained a little experience in using them, it will be easier to determine where they are needed and where they are not (cap). The main thing is to study what kind of problems frameworks can solve and how costly it will be to apply them on a particular project.
2. REST. Programmers will be just for the sake of it :)
3. It depends on what CMS. Most often this is not a good idea, but anything is possible. Depends on how costly it will be for programmers to implement REST in such projects.
4. Again REST. There are already a lot of different frameworks for such things.
Courses:
- Udemy - there is no better course (so they say, I never found time for it myself)
- Laracasts- very good lecturer, little water, lots of practice. I advise. The truth is partially affected by VueJS in Laravel.
- Documentation. Always better than any courses. Fortunately, Vue's documentation is simply gorgeous.

Answer 5

1) doesn't really matter.
2) REST
3) REST
4) REST or according to the classics.
PS
I can only talk about learning about React.