Dot Navigator

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)

Installation

Until the plugin is officially released, you can install it through BRAT (Beta Review and Testing)

1. Install the BRAT plugin if you don't have it already
2. Install Dot Navigator using BRAT

Features

• Hierarchical note organization with a tree-like interface
• Instant loading with IndexedDB caching, the tree view loads instantly even for large vaults by caching the tree structure
• Performance optimized for very large vaults, meaning you can expand all 10K notes from your vault at once on your phone, it will still run and scroll smoothly 👌
• Designed and optimized for mobile before desktop with lazy loading of suggestions for better mobile performance
• Rule-based suggestions that surface virtual child notes based on configurable JSON rules so you can scaffold structures before the notes exist

• 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)

• UI for renaming a note and its children with a nice UI

• Undo the last rename operation that was done in the rename dialog of the plugin (through the UI or with a command dedicated for that)

• Customizable context menus (click the "…" button or do a right click on a file or folder)

• Easy access to global commands in UI

• Support for all file types with appropriate icons and extensions

• Theme-aware styling with proper dark mode support

• 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)

• Internationalization support, based on the language set in the settings, defaulting to English. (As of now, only English and French 🇫🇷 are supported, you can request a new language by creating an issue)

Rule Configuration

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.

Setting Up Rule Configuration

1. Create a configuration file named dot-navigator-rules.json in your vault root, or specify a custom path in settings
2. Define rules as a JSON array of rule objects

Rule Syntax

Each rule object can have these properties:

• pattern (required): String or array of strings defining which files to match
• exclude (optional): String or array of strings defining files to exclude from matching
• children (required): Array of strings defining suggested child note names

Pattern Syntax

Dot 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 /.

Examples

[
  {
    "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:

• Files matching prj.* (like prj.frontend, prj.backend) will suggest children roadmap, ideas, issues, and hierarchical children architecture.backend and architecture.frontend
• Files matching work.** (like work.tasks, work.2024.tasks, work.deep.nested) will suggest notes, tasks (except work.archives)
• Files matching /^blog\.2025\.[0-9]$/ (regex for single-digit months) will suggest draft, published

Hierarchical 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".

Configuration File Location

The configuration can be stored in:

1. JSON file: dot-navigator-rules.json (recommended)

2. Markdown file: dot-navigator-rules.md with JSON in a code block:

   # Dot Navigator Rules
   
   ```json
   [
     {
       "pattern": ["prj.*"],
       "children": ["roadmap", "ideas"]
     }
   ]
   ```

Creating the Configuration File

1. Open the Dot Navigator settings in Obsidian
2. Go to Schema Configuration section
3. Click "Create new file" to generate a template
4. Edit the generated file with your rules

The plugin will automatically reload rules when the configuration file changes.

Available Commands

Dot Navigator provides several commands that can be accessed via the Command Palette (Ctrl/Cmd+P):

Core Navigation

• Open Tree View: Opens the Dot Navigator View in the left sidebar
• Show File in Tree View: Highlights and reveals the current file in the tree view
• Collapse All Nodes in Tree: Collapses all nodes in the tree view
• Expand All Nodes in Tree: Expands all nodes in the tree view
• Open Closest Parent Note: Opens the nearest existing parent note of the current file (checks dotted parents like a.b.c → a.b → a)

Note creation

• Create Child Note: Will create a new child note for the currently active file with the node name being "untitled" (e.g. if you trigger this command on a.md, it will create a.untitled.md) and will open the rename dialog for the new note (you can customize the name of the new note in the settings)

Suggestion Interaction

• Double-click suggestions: Quickly create suggested notes by double-clicking on them in the tree view
• Single-click suggestions: Focus/navigate to the suggestion in the tree

Rename

• Rename Current File: Opens the rename dialog for the current file or folder
• Undo Last Rename Operation: Reverses the most recent rename operation

Acknowledgments

• Dendron for the inspiration on hierarchical note management

Other tools that inspired this one:

• Structured Tree
• Obsidian Structure
• Obsidian Dendron Tree