We mentioned in part 3 that Elm has a Model - Update - View architecture. We've looked at the View and the Model, so let's turn our attention now to the Update. The best way to get a handle on what the update function will need to do is by taking a look at its type annotation.
So far Elm has been happily inferring the types that we are using in our application, and it will continue to do so. However let's take a moment to look at how we can make it more obvious to others who might read our code what types we are expecting.
Adding a Model and enhancing the View.
Adding a simple View to the Elm application.
Getting Phoenix and Elm to play together.
Installing prerequisites and generating a base Phoenix project
This is a walkthrough on the process of creating a new plug package and getting it published on Hex.
Short tutorial on how to add basic authentication to a phoenix web app.
Quick guide on setting alternative layouts within a phoenix web application.