At this point in the book, you probably have a pretty good handle on the role of view components in a Flux architecture. Put simply, their job is to display store information for users by inserting it into the DOM. In this section, we'll break this core view concept into three parts.
First there's the input to the views—the store data. Next, we have the structure of the view itself, and the various ways that it can be decomposed into smaller views. Finally, there's the user interactivity. Each of these three areas of view components has a relation to the flow of data through our Flux architecture. Let's look at each of them now.
If the store transforms data into information that the user needs, then why have views at all? Why not have the stores directly render the information to the DOM? We need views for a couple reasons. First of all, a store could actually be used in several places, rendered by several views. Second of all, Flux isn't necessarily...