Chapter 3. Building a Skeleton Architecture
The best way to think in Flux is to write code in Flux. This is why we want to start building a skeleton architecture as early as possible. We call this phase of building our application the skeleton architecture because it isn't yet the full architecture. It's missing a lot of key application components, and this is on purpose. The aim of the skeleton is to keep the moving parts to a minimum, allowing us to focus on the information our stores will generate for our views.
We'll get off the ground with a minimalist structure that, while small, doesn't require a lot of work to turn our skeleton architecture into our code base. Then, we'll move on to some of the information design goals of the skeleton architecture. ...
Get Flux Architecture now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
