Very many novice front-end developers often ask questions on this topic. What you need to know to take place in this profession? What exactly needs to be taught? How do you generally navigate in a huge amount of information about the frontend?

Closed due to the fact that it was off-topic by the participants Athari , Dmitriy Simushev , PashaPash ♦ , ermak0ff , LEQADA 19 Oct '15 at 19:22 .

It seems that this question does not correspond to the subject of the site. Those who voted to close it indicated the following reason:

  • " Questionnaires are forbidden on Stack Overflow in Russian . To get an answer, rephrase your question so that it can be given an unambiguously correct answer." - Athari, Dmitriy Simushev, ermak0ff, LEQADA
If the question can be reformulated according to the rules set out in the certificate , edit it .

  • one
    It is commendable that you decided to share your knowledge, but such questions on CO are offtopic as too extensive (or as “questionnaires”). The problem is that the answers to such questions very quickly lose their relevance, and no one supports them. In addition, they are too open to dispute: some consider one important, others consider another. CO is primarily intended for questions that have specific answers that will not become obsolete in six months. - Athari
  • one
    @Regent Literature is a single exception (on a large CO, it is placed on the wiki tags). Questions about the literature are general and actually supported. In addition, the literature is relevant for a long time. If C # 7 comes out tomorrow, the C # 6 literature will still be relevant. - Athari
  • 2
    @Discord, this question is very often asked. And in a personal ask. Even if the question is a bit offtopic, it is more pleasant to keep the answer to it here, on CO. - IonDen
  • one
    @Discord, the principle is clear. Although, IMHO, the answer to this question will live a couple more years. - IonDen
  • one
    @IonDen it will live, but the answer to it is almost useless. It simply lists technologies and frameworks. 30 pieces. For those who are oriented in the stack - it is not needed. For beginners - especially - the list of 30 names does not mean anything to them. - PashaPash ♦

1 answer 1

I will try to structure a little:

  • Base: EcmaScript 5 , HTML (5) and CSS (3) - you need to know.
  • Future: EcmaScript 2015+ , HTML5 + and CSS3 (4) + - you need to look and be aware.
  • Popular JS Extensions: EcmaScript 2015 via Babel , TypeScript , CoffeScript , etc. - EcmaScript through Babel is preferable because it allows you to use the future of JS today.
  • HTML extensions: Haml , Jade , etc. You can try if you like the syntax, but you can get along.
  • Popular CSS Extensions: LESS / SASS / Stylus , etc. - be sure to choose something, study and use in work.
  • Well-known JS frameworks: jQuery - be sure to know; SPA frameworks / libraries ( Angular, Ember, React, Backbone , etc.) - be sure to start learning and using something. Behind this approach, the future of the web, sites are increasingly turning into applications.
  • Known CSS frameworks: Bootstrap , Foundation , etc. - can be useful, especially Bootstrap with its many useful modules.
  • Build systems: Grunt / Gulp / Webpack , etc. Be sure to start exploring and using. Without this, nowhere.
  • Where the build is in the same place as Node.js , the command line and repositories like NPM and Bower , it is also useful to study for managing project dependencies.

Additionally:

  • You should always remember to work in a team (even if you are currently working alone): this is the Git version control system and the GitHub / Bitbucket platform - I recommend each project to be stored there. Very comfortably.
  • Also, during work / study, you will definitely touch on these issues: optimization, algorithms, network protocols, features of browsers, etc., it is very important to know how everything works from the inside.
  • For general development, the same is useful to learn another programming language besides JS

As you can see, the requirements for a modern front-end developer are incredibly extensive, the technological boom continues. So, I hope my note will help you navigate better.

  • one
    GitHub has nothing to do with it. No need to throw everything in one pile. - Vlad from Moscow