Got a few questions regarding the best way, or what options there are for scaling up to a large site. If i have a site with lots of features what is the best way to orgainze everything?
*One Elm page to rule them all?* With this approach you only have to deal with one update happening, you can separate code into different modules, but the update function would be HUGE. Guess this would be the same as a single page application? *One Elm page per HTML page?* This way every page deals with only what it is used for. You can write common things in reusable modules. One problem might be switching to other elm pages. The only really good way right now that i have is using a port to "window.locaion.href" to another elm page. Then pulling all the data it requires from the server using more ports. *One Elm page per feature?* This way you can write separate apps for each part of your page. One for the header menu bar, one for a sidebar, and one for each main feature. This way you can mix and match and piece together for a full page. BUT you might have to do a lot of port talking between each section. *Some other way?*????? Been searching around a cant seem to find any blogs or topics on this subject. Our stack is Elm/Phoenix/Elixir/Postgres. If anyone has created a large application using Elm would happy to have your input on what worked/ didn't work for you. Thanks, -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
