This chapter went into detail on the view layer of Flux architectures. Starting with getting information into views, you learned that the change event is fundamental in reflecting the state of the store in the view, and that views often read directly from stores during their initial render. Then, we went over the idea that views are stateless. The state of a given UI element belongs in a store, because other parts of the application might depend on this state, and we don't want to have to query the DOM.
Next, we went over some of the high-level responsibilities of view components. These include rendering store information, composing larger view structures out of smaller view components, and handling user interactivity. We wrapped the chapter up with a walkthrough of using ReactJS components as the view technology in a Flux architecture. In the following chapter, we'll dig into the life cycle of Flux components and how they differ from other architectures.