By picking a good React tutorial .

I would suggest PluralSight or EggHead videos.

ReactJS is easy to learn if you understand the basics.

• All React component has a render method which renders the elements to a virtual DOM.
• Changes to Props and State causes re-renders.
• Props are immutable and passed down by parent.
• State is mutable using setState.
• For sharing state between two components, there should be a common parent which holds that state.
• To avoid complicated data flows, use state management like Redux. This lifts state all the way to the top of the hierarchy in container components.
• HOC are functions which take a base component and return another component. For example, connect in react-redux.
• Sometimes, we need the DOM element of the component. For that use ReactDOM.findNode.
• Finally lifecycle methods for writing reusable components:
  • componentDidMount for ajax calls / redux-thunk
  • componentWillReceiveProps for setting state based on new props
  • shouldComponentUpdate - to prevent render based on criteria
  • componentWillUnmount - clear timers, handles, etc.

Joining a newsletter like ReactDOM is a great way to stay in touch with all the current changes in the rapidly evolving world of ReactJS.

The comp i work for have a Udemy account for all devs; Udemy has excellent beginner courses on react.

After taking one 16/hr or so hour course, I had enough knowledge to dive into the docs at facebook.

Diving into the documentation was the best decision ever...

I would advise reading a book covering the react stack with all the topics that you need to get started. Full-Stack React is the best bet because i have personally learnt react from it.

There are ton of other materials on the web which are free unlike the book i mentioned above but what i did was i went to web whenever i felt i needed some in depth guide for a topic i read in the book (happens very less) and it worked great.

I also learnt angular the same way. Give the book a spin !

I did learn React from 2 years ago when it was hard to find any guide or tutorials on React. I had to dig the docs and repeated coding with trial-and-error learning style. It cost me quite a time to get familiar with because at that time I was working with Angular 1.x which is different from React.

medium.com/@petehouston/how-i-learned-react-from-…

As usual, reading docs then tutorials and pratice in a side project first.

Thanks for invite but I, actually, didn't learned React on the professional level, I prefer Vanilla ES6. The good part about React and why it suck less then other frameworks is that at least by reading any examples I could instantly understand what approximately they do, when I was reading Angular-based code, I had no idea what it was doing.

Nevertheless, React IS JavaScript and I always recommend to learn your tools and languages you use on the highest level first before using and learning any frameworks. In case of frontend I still would suggest to use simple, plain vanilla JS and master it, with the help of some libraries of course. React is just a marketing, it is not better, safer, faster, cleaner. You can do the same without React. Modern JavaScript is very powerful and with combination of general software engineering and architecture patterns and principles you have maximum flexibility and simplicity.

I would recommend those resources:

• This awesome blog on Medium called JavaScript Scene by Eric Elliott. Read all of his articles, re-read, try to understand everything. It might take a lot of time, but it's worth it. You don't have to agree on all of his opinions.
• This amazing YouTube channel FunFunFunction by mpj has many JS video tutorials.
• The Ultimate JavaScript Cheat Sheet
• MDN JavaScript section is still one of the best general resources to learn JavaScript from scratch and view all of it's APIs with nice examples
• Read source code of different popular and not only popular JS projects on GitHub
• Practice, practice and practice again. Practice by writing a lot of code, write own libraries, frameworks, contribute to open source.
• You might not need jQuery
• You don't know JS
• Awesome FP JS
• Essential JavaScript Links

I still would recommend any software engineer, even beginner, to try himself as a framework developer because:

• by that he will practice software architecture,
• will understand many patterns and principles
• and will have a deep knowledge on how routers, template engines and everything works inside the box.

Other answers here will guide you though the next step on React itself. I, personally, didn't liked official documentation.

One mistake I made was trying to learn redux and other libraries at the same time, so I had to step back and take a course that only taught React (reactforbeginners.com) in my case. So my advise is build something only using React, then try to understand why would you need to use any other libraries and finally learn those if needed.

The official docs and blogs from developers. Before that, I spent a lot time on Backbone, and a lot of libraries, I was somehow experienced in this area.

2 years back React is much simpler, only ES5 APIs, Flux, no Redux, no GraphQL, no ES6 syntax, no Babel. I just got it learnt after overcome the JSX barrier.

I'm now learning ReactJS and I am taking this course from Udemy.

In this course I learned Ecmascript6 syntax, React and how to connect React with Redux.

There are as many approaches as there are people. Some will work for one, some won't, it's fine.

The way I have usually been learning, and this is what I've seen others implement successfully too, is to learn by doing.

• Learn the basics. Usually the official docs are a great place to get started. Maybe follow an official tutorial. DO NOT start running around and learning about a myriad of other libraries — Redux, Relay, React-Router, GraphQL, this that and that.

• Build a toy project. (If you're not the "idea person", well, neither am I! And yet, there are ways to come up with an idea: goshakkk.name/learning-project-ideas) You will learn insane amounts of knowledge in this phase, things will "connect" and start to fit in in your head. Doing only tutorials that hand-walk you the entire time does not give you this, they kind of show you a thing, but you have no freakin' idea how and why it works.

• While building a project, you WILL get stuck at times, and it's cool, you're not alone in that. Try to help yourself first. Do the researchin'. Try to frame your problem differently and see if it makes the googling (or plain gathering the solution by yourself!) easier. Even writing it down in words can help you see something that you were missing under your nose up to this point.

• Do not obsess with libraries. Don't run around dropping X and Y and Z into your project randomly. Try to do as much as possible by yourself and only then if something starts to hurt badly, consider bringing in a third party library. I've written about a more specific application of this rule in the case of state management with Redux et co: goshakkk.name/redux-vs-mobx-vs-flux-etoomanychoic… but it applies on a more general level as well.

• Do not try to find a ready component for everything. This is important for two reasons. One, as a beginner, you'd want to do as much hands-down as possible. Two, each dependency is a liability and should be analyzed as such. And research and such takes time, and often, it's more time effective to just write your own from scratch. Especially in cases when implementing something overly specific to your app.

Those are just a few points that popped up immediately. Feel free to reply or ask something specific.

(Update: I've published a post that further touches on some of the points of this answer goshakkk.name/next-steps-official-react-tutorial and goshakkk.name/no-tutorial-for-everything)

youtube , tons of resources and tutorials available my personal favorite : LearnCode.academy