Just wanted to clarify, the elm-pages v3 architecture was built with dynamic apps in mind. Static sites were the core use case for elm-pages v2. The v3 architecture is very similar to NextJS or RemixJS, so the value proposition is similar. It’s a hybrid framework that allows you to do server-side rendered routes that respond with dynamic data resolved on the server (or statically at build-time for a static route). A lot of the core features I’ve been working on are around the Form API, which is inspired by the Remix architecture of progressively enhancing form submissions. So the main focus of my work on v3 has been to support those kinds of use cases in the same way that the modern full-stack JS frameworks do. This full-stack server-rendered approach to dynamic apps comes with a set of architectural opinions and tradeoffs and it’s definitely not the only choice, but I think it’s one with a compelling story in terms of performance and simplicity.
elm-pages v3 is still in beta so hopefully I’ll get a chance to share more about the intended use cases once the stable release is out! I discussed it a little bit in this post so in the meantime that’s a pretty good place to start for a preview: Realworld app (elm-spa-example) in elm-pages v3.