What would you like to be added/removed:
I would like single-file navigation categories to be removed.
What is the current situation:
Many navigation sections contain only one file. Some even include an additional nested subcategory. This is the case for all sections named "Tutorials" in the Infrastructure Extensions block.
For example, the Create a Кubernetes Cluster on GCP with Gardener page is the only document within the Kubernetes cluster on gcp with gardener subsection, which itself is the only subsection under Tutorials. This results in several redundant levels of navigation:
Why do we need it:
The current structure introduces unnecessary depth and makes the documentation harder to browse. Single‑file subsections lead to:
- Extra clicks and visual noise in the navigation tree
- Reduced discoverability of important content
- Inconsistent user experience across documentation sections
- Less efficient navigation for readers looking for specific guides
What would you like to be
added/removed:I would like single-file navigation categories to be removed.
What is the current situation:
Many navigation sections contain only one file. Some even include an additional nested subcategory. This is the case for all sections named "Tutorials" in the Infrastructure Extensions block.
For example, the Create a Кubernetes Cluster on GCP with Gardener page is the only document within the Kubernetes cluster on gcp with gardener subsection, which itself is the only subsection under Tutorials. This results in several redundant levels of navigation:
Why do we need it:
The current structure introduces unnecessary depth and makes the documentation harder to browse. Single‑file subsections lead to: