Is your feature request related to a problem? Please describe.
Yes.
Current behaviour of the navigation sidebar:
If a single page content item has a parent path of a content item under a multi-page, it won't be listed/displayed in the navigation items list. Since multipage items cannot be sorted individually and so as those that are "parented" to it.
Customer use-case:Re: the sidebar, while makes sense from a URL routing perspective - our perspective is that the way a given page is displayed in Zesty Admin’s Sidebar, and the actual URL routing of a page, are not necessarily always desired to be the same thing. There are instances where the team may want a page to be a top-level page from a URL perspective (i.e. acorns.com/my-page/), but still have & display underneath a parent content model. In fact, we ran into this earlier today.
So while it definitely is understandable that that may not be possible today based on the way the Zesty platform is set up, we’d request that at some point, Zesty Admin Sidebar Nav structure & URL structure be decoupled from one another, at least as far as it relates to “parent” content models.
Decoupling these would also solve the issue of a single page content item not being able to appear underneath a multi-page content item, because the Admin Sidebar Nav Structure & URL Structure would be different.
Describe the solution you'd like
Request to decouple the navigation structure of content item URL, and content models
Is your feature request related to a problem? Please describe. Yes. Current behaviour of the navigation sidebar: If a single page content item has a parent path of a content item under a multi-page, it won't be listed/displayed in the navigation items list. Since multipage items cannot be sorted individually and so as those that are "parented" to it.
Customer use-case: Re: the sidebar, while makes sense from a URL routing perspective - our perspective is that the way a given page is displayed in Zesty Admin’s Sidebar, and the actual URL routing of a page, are not necessarily always desired to be the same thing. There are instances where the team may want a page to be a top-level page from a URL perspective (i.e. acorns.com/my-page/), but still have & display underneath a parent content model. In fact, we ran into this earlier today. So while it definitely is understandable that that may not be possible today based on the way the Zesty platform is set up, we’d request that at some point, Zesty Admin Sidebar Nav structure & URL structure be decoupled from one another, at least as far as it relates to “parent” content models. Decoupling these would also solve the issue of a single page content item not being able to appear underneath a multi-page content item, because the Admin Sidebar Nav Structure & URL Structure would be different.
Describe the solution you'd like Request to decouple the navigation structure of content item URL, and content models
Additional context Related to ticket #590