Routes modules embedded in multiple pane layout - is it possible?

[estenp]

I am being asked to implement a multiple pane layout where you can create on the fly, split pane views. The purpose of this feature is to improve multitasking within the app. The goal is for any page (really any route, or at least route tree), to be able to work within a pane among other routes living within panes. In other words, parallel routes. The existing routes lean heavily on RR patterns, so there seems to be a lot within my existing routes that would break this paradigm like hyperlinking to other route URL's for an obvious example, but it seems like most RR API's would not work with the code being oriented this way.

Some ideas that have crossed my mind:

• iframes
• harded route configurations or convert route URL's to use search params exclusively to configure routes
  • create a dedicated route for every permutation of the pane combinations
  • rework all routes to enable navigation within their route tree without impacting the URL
• dedicated custom components per route
• break up existing routes in to the absolutely most modular components possible to maximize code reuse between real route modules and routes within panes
• rework Link component to be aware of pane context and turn off traditional navigation and turn on some sort local route management within the pane component
• MemoryRouter ?
• Server Components ?

I've considered a number of approaches, consulted LLM's, Github discussions, etc., and it feels like there is no good answer here, but I'm desparate for a solution other than rebuilding the functionality of every page in my system. Any thoughts on this matter is greatly appreciated as this is a must have feature for us.