Side Navigation Root Difficulty

[jrjohnson91]

Hi @chalin and fellow community members,

I am trying to replicate the side navigation behavior found on https://www.docsy.dev/docs/ site.

Particularly the difference in the side navigation for pages https://www.docsy.dev/docs/get-started/other-options/ and https://www.docsy.dev/docs/content/adding-content/. The former stays at the top most level of the "Docs" and the latter sets the navigation root to "Content and Customization".

What is driving the difference in this behavior? I cannot seem to figure out how to create this behavior in my own site.

1. The front matter of each _index.md of the respective folders don't seem different.
2. I don't see an explicit type of type: "docs" anywhere. I am using cascade: [ { type: "docs", _target: { path: "/**" } } ] at the root _index.md

[jrjohnson91]

I have done a little more reading and I would like to mention that this is a doc-only site and I've added

# Publish docs pages/sections at site root (no /docs prefix).
[permalinks]
  [permalinks.page]
    docs = '/:sections[1:]/:slug/'
  [permalinks.section]
    docs = '/:sections[1:]'

# Make home pages link-only so docs section landing pages can own root URLs;
# this avoids Hugo warning about duplicate pages rendering at the site roots
# (for each locale).
[cascade]
  [cascade.build]
    render = 'link'
  [cascade.target]
    path = '/'

Having done that, I moved all the .md files into content/en/docs so the permalinks would work.

Including build: { render: link } in content/en/docs/_index.md causes a 404. Not including it in the front matter results in a successful site, but I still end up having the sidebar change to section root when I want the sidebar to always be the same. Any advice?

Including @adlerzei because I found your issue helpful.