# Second Stage of navigation?

**URL:** <https://discourse.nodered.org/t/second-stage-of-navigation/86713>\
**Category:** Dashboard\
**Tags:** uibuilder\
**Created:** [24 March 2024 11:18 UTC](https://discourse.nodered.org/t/second-stage-of-navigation/86713 "2024-03-24T11:18:55Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![David83](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/david83/32/89387_2.png) [@David83](https://discourse.nodered.org/u/David83)\
**Post date:** [31 March 2024 14:42 UTC](https://discourse.nodered.org/t/second-stage-of-navigation/86713/3 "2024-03-31T14:42:18Z")

</div>

Thanks for the information @TotallyInformation !!!

For the moment i think i will use the non-route solution. I am not so firm in javasript that I could implement my own subrouter.

But I don't think multiple router instances are necessarily needed for nested routing. Nested routing can also be solved using an instance by specifying the sub-routes within the main routes.

Starting from such a configuration:

```auto
const routerConfig = {
    routeContainer: '#routecontainer',
    routes: [
        {
            id: 'lights', src: './routes/lights.html', type: 'url',
            title: 'Lights'
            subrouteContainer: '#lights-container' 
            subroutes: [
                {
                    id: 'lights/kitchen',
                    src: './routes/lights-kitchen.html',
                    type: 'url',
                    title: 'Kitchen',
                },
                { ... }
        }, 
    ],
};

```

Of course, it is then necessary to adapt the router logic accordingly and possibly the handling of the navigation events, or am I seeing this wrong?

---

_[View the full topic](https://discourse.nodered.org/t/second-stage-of-navigation/86713)._