Chapter 1. Introducing hapi
Figure 1.1. hapi can be used to build all sorts of networked applications.
Figure 1.2. Where hapi fits into an example application
Figure 1.3. Comparing different framework types
Figure 1.4. How an e-commerce API might be structured as a hapi app
Figure 1.5. The building blocks of hapi
Figure 1.6. How the building blocks fit together
Figure 1.7. The console interface for Make Me hapi
Chapter 2. Building an API
Figure 2.1. The user stories that I’ve collected from the customer. These are the requirements for the DinDin application.
Figure 2.2. A high-level overview of the API
Figure 2.3. The entity relationship diagram for the dindin SQLite database
Figure 2.4. Simple HTTP requests and their corresponding hapi routes
Figure 2.5. Overview of endpoint A
Figure 2.6. Response to endpoint A with no search parameters
Figure 2.7. hapi parses query parameters into the request.query object
Figure 2.8. Overview of endpoint B
Figure 2.9. Cookie-cutter analogy of schemes and strategies
Figure 2.10. The Postman interface
Figure 2.11. Overview of endpoint C
Figure 2.12. Overview of endpoint D
Chapter 3. Building a website
Figure 3.1. Sitemap of the DinDin website
Figure 3.2. The visual design and functionality of the website
Figure 3.3. Overview of how the whole application will work together to serve clients
Figure 3.4. A request and response cycle with reply.file()
Figure 3.5. The unstyled home page. We need to fix this by making some assets available.