jeansordes651 downloadsA Dendron-like hierarchical note management system for your vault.
A hierarchical note management system with Dendron-like features.
This tool brings hierarchical note management capabilities to your vault, inspired by Dendron. It allows you to organize your notes in a tree-like structure, making it easier to navigate and manage large knowledge bases.
(While Dot Navigator maintains some compatibility with Dendron-structured notes, future compatibility is not guaranteed. It is primarily intended for use with notes in your vault, utilizing a Dendron-like structure)
Until the plugin is officially released, you can install it through BRAT (Beta Review and Testing)
Hierarchical suggestions from dotted children - when a rule specifies children like ["foo.bar"], it creates nested suggestion nodes where "foo" contains "bar" as a child, allowing for deeper scaffolding of note hierarchies
Double-click to create notes from suggestions - quickly create suggested notes by double-clicking on them in the tree view
Persistent expanded state across sessions (the tree view will remember which nodes are expanded or collapsed when you close/reopen the app)
Horizontal scrolling support for deeply nested structures (you can write very long path notes and scroll horizontally to see the full path of the note)
Drag-and-drop to move files, folders, and virtual nodes directly in the tree (children are moved/renamed along with their parent). Press Escape while dragging to cancel.
.git/, .gitignore, .obsidian/, etc.) are included in the tree and hidden by default; use the header eye toggle or Settings → Dot Navigator → Hidden nodes to reveal them. You can also define glob hide patterns (e.g. archive/**).
.md stub files with redirect frontmatter to place a note at alternate locations in the tree. Shift+drag (or Alt+Cmd/Ctrl+drag) onto another node to create a stub; drag the stub row to move it; delete stubs from the context menu without deleting the target note. Title click opens the redirect target; use the symlink icon to open the stub file.The redirect value accepts a vault path, a note name, or a wikilink. Ambiguous names follow Obsidian wikilink resolution relative to the stub file.
---
redirect: notes/target.md # full vault path
redirect: notes/target # path without extension
redirect: target # note name (no folder, no .md)
redirect: "[[My Note]]" # wikilink
---
Child count badges — optionally show direct children, total descendants, or both on tree rows (configurable in settings under Tree display)
YAML title support - displays custom titles from frontmatter instead of filenames (e.g. prj.md with the property title = "Projects" will be displayed as Projects in the tree view)
Dot Navigator supports rule-based suggestions that automatically suggest virtual child notes for existing files. This allows you to scaffold note hierarchies before the actual notes exist.
Each rule is edited as a card with pattern, exclude, and children fields. You can preview which notes match a pattern, drag to reorder rules, and use View JSON to copy or back up your configuration.
If you previously used a dot-navigator-rules.json file in your vault, rules are migrated automatically into plugin settings on first load after upgrading.
Each rule object can have these properties:
pattern (required): String or array of strings defining which files to matchexclude (optional): String or array of strings defining files to exclude from matchingchildren (required): Array of strings defining suggested child note namesDot Navigator uses enhanced glob patterns with special wildcards:
* matches any sequence of characters within a single path segment (stops at dots)** matches any sequence of characters across multiple path segments (matches dots)For more complex pattern matching, you can use regex patterns by prefixing with /.
[
{
"pattern": ["prj.*"],
"children": ["roadmap", "ideas", "issues", "architecture.backend", "architecture.frontend"]
},
{
"pattern": ["work.**"],
"exclude": ["work.archives"],
"children": ["notes", "tasks"]
},
{
"pattern": ["/^blog\\.2025\\.[0-9]$/"],
"children": ["draft", "published"]
}
]
What this does:
prj.* (like prj.frontend, prj.backend) will suggest children roadmap, ideas, issues, and hierarchical children architecture.backend and architecture.frontendwork.** (like work.tasks, work.2024.tasks, work.deep.nested) will suggest notes, tasks (except work.archives)/^blog\.2025\.[0-9]$/ (regex for single-digit months) will suggest draft, publishedHierarchical Children:
For dotted children like "architecture.backend", the plugin creates nested suggestion nodes. In the tree view, you'll see:
architecture/ (intermediate folder-like node)backend (clickable suggestion that creates backend.md)You can create deeply nested hierarchies by using multiple dots, such as "a.b.c.d".
Rules are stored in plugin settings and reload immediately when you save changes in the editor.
Dot Navigator provides several commands that can be accessed via the Command Palette (Ctrl/Cmd+P):
a.b.c → a.b → a)a.md, it will create a.untitled.md). Use Rename Current File or the tree context menu to rename it afterward (you can customize the default name in settings)