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. Next, we'll dive into implementing some aspects of our stores.

As we start building, we'll begin to get a sense of how these stores map to domains—the features our users will interact with. After this, we'll create some really simple views, which can help us ensure that our data flows are in fact reaching their final destination. Finally, we'll end the chapter by running through a checklist for each of the Flux architectural layers, to make sure that we've validated our skeleton before moving on to other development activities.