Nesting pages deeper than 2? (Great grandchildren?)

[samamstar]

Is there a satisfactory to have pages nested deeper than 2 children? I currently have a page structure like so:

Function Libraries
┕━ DRG
    ┕━ Mods
         ┕━ GetModVersion

In each page I wrote Jekyll FrontMatter formatted referencing the proper parents and grandparents, but when I serve my website "Mods" has no children in the sidebar

When opening the "Mods" page I get a table of contents like any other parent page, and am able to navigate to GetModVersion.

Additional info:
My website in its current state is available here, and the source for it is available here

The Front info for the pages in question:

FunctionLibraries.md:
---
layout: page
title: Function Libraries
has_children: true
---

DRG.md:
---
title: DRG
parent: Function Libraries
layout: page
has_children: true
---

Mods.md:
---
layout: page
parent: DRG
title: Mods
grand_parent: Function Libraries
has_children: true
---

GetModVersion.md:
---
layout: page
parent: Mods
title: GetModVersion
grand_parent: DRG
---

I worry that what I want is not possible in just-the-docs, but I wanted to ask just in case.

If it is not possible to nest 3 pages like this in the sidebar/directory, are there any known workarounds that would allow for similar behavior?

Thank you for reading.

[samamstar]

Oh and do forgive me if I have used the wrong terminology, web design is very new to me :)

[mattxwang]

Good question; this is one of our most-requested features, and is next on the roadmap for us (for context, I've just become a maintainer and am drafting a very large v0.4.0 release already). The short answer is that this feature does not exist (see this issue: #219).

If you're curious and/or would like to provide feedback, this PR is likely how we'll go about implementing the feature: #462!

[samamstar]

Thank you for the response! I will look into those and will likely start using the rec-nav-2 branch for my site.

[VerzatileDev]

Has this been worked on, or should I also take another look in aiming to implement it ?

[pdmosses]

@VerzatileDev as you may have noticed, I commented in #462:

PR #1397 should make it much easier to add recursive navigation (by reducing dependence on the parent, grand_parent, and has_children relations).

I expect to have time this month to investigate whether the directory structure could determine the navigation hierarchy (apart from the title and nav_order, which would still be specified in front-matter). I think that would have some significant benefits, although there might also be some drawbacks.

I suggest to continue the discussion in #1277, to make it more visible.

I have started looking at the possibility of using the directory structure (together with the presence of index files) to determine default values for parent and grand_parent. Pages in the root and docs directories would be assumed to be top-level pages (much as in Material for MkDocs and Hugo , so they wouldn't have default parent pages.

One of the aims is to avoid the complication of the section and ancestor fields added in #462; another is to make it possible to omit all parent, grand_parent, and has_children fields when specifying Just the Docs sites of unlimited depth. We might consider also using file names as default titles, allowing the title fields to be omitted too.

Unfortunately, I haven't yet managed to find time to start experimenting with an implementation of these ideas. If you (or anyone else) would like to take a look at implementing something similar, please go ahead! However, I think any proposed design will need careful discussion before a new PR for multi-level navigation.