The themes Default and Cozy have an option to limit the depth of pages which appear in the main navigation menu - you could set it so only the parent pages appear. Then you could use the table of contents block on the parent page.
Anyway, if I do not want to have the parent pages in the navigation, there is still a problem. I think page hierarchy should be done inside “pages” and navigation hierarchy should be done inside “navigation”.
We’re open to ideas on how to improve the handling of the site hierarchy. Currently, the page hierarchy works in tandem to our navigation to facilitate a consistent page organization.
So that we can better understand your use case, could you explain the flow that would lead your audience to these nested pages outside of the primary navigation?
We use Omeka S to present old letters and an apparatus. The letter are described as items with many metadata. Pages serves the purpose to introduce and present the letters. We integrate some letters inside the pages with the help of media blocks. All letters are available from the navigation (this is why we don’t want pages of the apparatus in the navigation).
If we compare to printed book, each page is a chapter or subchapter. This is why we need some kind of hierarchy. And there are too many pages to integrate them into the navigation.
We would love to use the ‘table of content’ feature to order pages. But it is restricted to navigation pages. So we use a workaround with a html block which present a lists of all pages/chapters:
That mostly makes sense to me, but is there a page where your users would browse through the letters? What does your primary navigation look like? At the moment, this is how I would see your site structure looks:
|-- Home
|-- About
|-- Letters
|---- Letter
|------ Index
|------ Chapter 1
|------ Chapter 2
|------ Chapter 3
with Home, About, and Letters being part of the primary navigation. In Center Row, the top navigation would not show any of those subpages. Is there something I’m missing?