>In fact if you look at the URL the site is called reactfordesigners.com.
You would want your designers to write frontend code that is complex enough to require React ?
The way I've worked with designers is they create sketches and prototypes just to demonstrate the concepts with whatever they are familiar with and then developers turn that in to actual maintainable code with feedback.
My educational roots are in graphic design but I have taken on more and more front end development as my career has progressed to the point that I'm mostly coding these days.
With Web design, I started with simple HTML sites, learned CSS, then learned some JS to manipulate the DOMs I created.
Having run into some of the jQuery pitfalls that the author describes, This tutorial meets me where I'm at and takes me to a new place, using incremental, concrete, and practical examples to show me that React is a logical extension of JS in certain use cases.
Designers are visual people, so being able to see each step along the way and telling me why it's important is a really big deal. I have some projects now where I'm changing state quite a bit, and I can now see where React would be really useful. Designers also tend to get into the web coding stack from the front end first, so I think we end up thinking about coding a Web site in a really different way than back-end developers with a background in software engineering.
The title says
> React.js Introduction for People Who Know Just Enough JQuery to Get By
Unless you're working at a really big shop, designer these days is almost synonymous with UI/UX engineer or front-end engineer. Considering the target audience is JQuery users, React is not too far of a jump and doesn't have to be restricted to "complex" websites.
In order for benefits of React to outweigh the costs you need to have a web application with complex data flow. jQuery is proven to work and there is no problem with it in anything less.
At the point where you actually need React you also need to understand software engineer or you're going to get a mess no matter what the framework is.
You would want your designers to write frontend code that is complex enough to require React ?
The way I've worked with designers is they create sketches and prototypes just to demonstrate the concepts with whatever they are familiar with and then developers turn that in to actual maintainable code with feedback.