The requirements you have may not follow the best UX guidelines, as it could lead to a confusing user experience. For example, once Item3 is loaded with its own DrawerContent, how would the user navigate back to the original Drawer component with the initial 3 items?
I would recommend keeping a single Drawer, and when Item3 is selected, display its related content (e.g., items 3.1, 3.2, 3.3) in a TabStrip or similar UI component.
That said, your requirements could also be implemented with nested routes and conditional rendering. This approach would check the current path to determine which Drawer component should be displayed.
Regards, Anislav Atanasov
0
Yanko
Telerik team
answered on 18 Mar 2025, 05:11 PM
Hello, Nikhil,
Yes, you can render a different component outside the drawer for `item3` by moving the route for it outside the DrawerContainer and wrapping the DrawerContainer in a separate Route. This way you can render `item3` separately from the DrawerContainer. I prepared an example demonstrating the above approach, that you can customize and extend with another Drawer for the `item3` component to meet your requirements: