Description
Is your feature request related to a problem? Please describe.
In documentation-heavy projects, organizing content purely by content type (e.g., all Markdown files in a flat list) becomes difficult to navigate at scale. The current Frontmatter CMS dashboard doesn't mirror the folder structure of the underlying filesystem, which limits intuitive navigation and makes it harder to understand the content's hierarchy—especially for teams working with structured documentation (e.g., guides, references, tutorials).
Describe the solution you'd like
I’d like the CMS dashboard to optionally support a “Structure” view that mirrors the project’s actual folder hierarchy. This would allow users to browse and manage documentation in a tree-like format, similar to how files are arranged in the repository. Ideally, this would include:
- Collapsible folders based on directory structure
- Ability to click into files directly from this view
- Optional toggle between "flat content type view" and "structure view"
This would make the CMS feel more aligned with how developers and writers conceptualize and organize documentation projects.
Describe alternatives you've considered
- Using tags, categories, or custom fields to emulate hierarchy. While this works, it doesn’t visually or functionally replicate the nested folder structure, and it requires additional manual configuration.
- Navigating and editing files directly via VS Code instead of the CMS dashboard. This bypasses the dashboard entirely, which negates the benefits of a visual content management interface.
Additional context
This would especially benefit documentation sites using structured formats (e.g., Docusaurus, Astro, or custom static site generators), where directory depth often conveys meaning (e.g., /guides/advanced/ vs /guides/basics/). A structure-aware dashboard would make the CMS more intuitive for both technical and non-technical contributors.