So, for the past few years I’ve been diving into different kinds of projects, from converting PSDs designs into HTML(5) websites using CSS(3) and my favorite tool SASS or Bootstrap 3, to coding backend modules with Go or PHP(Laravel) and creating clusters for Neo4j with Docker containers, its been one heck of a ride, but all of these projects have one thing in common, Reactjs.
At first I started modifying existing components, getting used to the idea of component based websites, but as the projects evolved, I had to create new websites from scratch, only having the PSD design or creating new components to consume an API. So here is where my journey really begins.
After getting the hang of webpack , and stablishing a basic starting point for every Reactjs project (I just fork that from my repo and I know I have a working starting point), I moved to reactjs itself, playing around with it, seeing how it worked, what can I do with it, the use of the virtual dom. I though life was good again, but then here comes Redux, although not made only for reactjs, it really helped me managed application state, at first it was confusing, jumping from handling the states within reactjs to using a (middleware) for it, but boy, I have to say, it’s really handy for creating clean and understandable code. All of this I had to learn it while working on projects and applying that new knowledge to it, I think its the best way to learn, under pressure!!! and on live projects(wouldn’t you agree?) :)
My journey with Reactjs or any related technology is far from over, as the projects grow in complexity and its popularity keeps increasing, I’ll learn even more.
So to recap my steps for leaning and working with Reactjs
- Learn webpack
- Learn Reactjs
- Create a working initial point of modules and .conf files to save time
- Play around and keep creating with Reactjs
- Consume APIs (here is a collective list of public JSON APIs you can use to practice or even use on your projects)