ReactJS Architecture: Part 3 Alex Banks Thu, 07/28/2016 - 18:00


In Part 2 (, we discussed configuring Director to listen for route changes and run a route handler (conveniently all Director does (and why I love Director)). In this post, we will finally do some React writing. Not a lot. But some. This series is intended to be about React architecture, not necessarily React code creation (which maybe maybe we’ll do later).

ReactJS Architecture: Part 2 Alex Banks Tue, 04/26/2016 - 20:21

In React Architecture: Part 1 we discussed a desire to configure a working React website with as few addons as possible. The post ended with the creation of a basic Webpack config, which left us with a project structure like...

ReactJS Architecture: Part 1

The Why

React is awesome. 11/10. In my opinion, the best UI library currently in the ecosystem. It streamlines UI componentization, reusability, UI state, and a ton of other client side headaches devs have been mitigating for years. React's greatest flaw, in my opinion, isn't even really a React flaw as much as a "new stuff hype" flaw, where the infrastructure surrounding React changes almost hourly and can be extremely difficult to keep up with. What libraries are required, which ones will make devs' lives easier, which will bring performance gains?  

Ready to get started?