Exactly, the mentality is the same as client SPA routing (see: package.elm-lang.org/src/frontend/Main.elm at master · elm/package.elm-lang.org · GitHub). Sections within a page barely need multiple processes. OP took some inspiration from Live Dashboad, but even Live Dashboard has only 1 process which is PageLive.
Given OP’s GUI layout, I have to ask myself why <main> needs a separate process instead of live_component with the following requirement:
Not sure if this is the need to access same set of state/truth or the need to use the same data structure which would be a share module in a phoenix context. If it’s the former case they should live in the same process, right?
render_headerwill also call a method on my child view.
I’d love to see what the exact method is, to understand more about the relationship between the header and the main.
