elm-spa-example

Your state can be a tree, if it needs to be, so you can nest. A normal practice is to have a model per page. For e.g. https://github.com/rtfeldman/elm-spa-example/blob/master/src... And you can have another item next to it for global state if you need to. https://github.com/ohanhi/elm-shared-state explains one way to do this

I recently did a talk at Oslo Elm Day where I talked about our experience with Elm at my company after using it as the main web langauge for the past 18 months: https://youtu.be/yE9PKFI19RM TL;DR: - The experience has been terrific. - Best compilator I have ever worked with. - Mostly great tooling. Love the auto-formatter. - Great libraries - No major issues, some small itches but nothing that can't be worked around. - No runtime errors in 18 months. - Very maintainable code - New team members quickly becomes productive in Elm, even with no prior experience (It helps to have someone with experience on the team to guide the learning and answer questions). When it comes to nesting we sometimes make use of a component-like pattern, where we have modules with their own state, messages, update and view functions that are used by the main fu