Auto Navigator Pages

by Carlos Chen
5
4
3
2
1
Score: 50/100

Description

Reviews

No reviews yet.

Stats

1
stars
24
downloads
0
forks
6
days
6
days
6
days
0
total PRs
0
open PRs
0
closed PRs
0
merged PRs
0
total issues
0
open issues
0
closed issues
5
commits

Latest Version

7 days ago

Changelog

Changes

  • Fixed marketplace manifest description punctuation warning by ending the bilingual description with ASCII punctuation.
  • Added metadata regression checks for manifest description punctuation and version mapping.

README file from

Github

Auto Navigator Pages

English 简体中文

Auto Navigator Pages automatically creates and maintains folder navigator pages and Home.md for folder-based Obsidian vault organization. It is useful when you organize notes by folders and want each folder to have a managed overview page linking to child folders and direct notes.

Features

  • Create and maintain same-name navigator pages for folders.
  • Create and maintain Home.md for top-level folders and notes.
  • Automatically use Chinese or English UI text based on the current Obsidian language.
  • Require explicit initialization before modifying navigator pages.
  • Back up existing same-name notes during first initialization.
  • Preserve user-editable content outside the generated navigator section.
  • Support custom navigator page templates with the required {{navigator}} placeholder.
  • Hide empty child-folder or note sections.
  • Use real-path links with aliases for child folder navigator pages.
  • Sort underscore-prefixed files and folders last in the file explorer.
  • Optionally pin navigator pages to the top of their folder in the file explorer.
  • Optionally route new empty notes created from ordinary wiki links into a _node subfolder.
  • Support exclude rules for folders, folder names, file names, and extensions.
  • Save and restore the previous workspace layout.
  • Clean orphan managed navigator pages.

Installation

From the Obsidian community plugin browser

  1. Open Obsidian settings.
  2. Go to Community plugins.
  3. Search for Auto Navigator Pages.
  4. Install and enable the plugin.

Manual installation

  1. Download main.js and manifest.json from the latest GitHub release.
  2. Create this folder inside your vault:
VaultFolder/.obsidian/plugins/auto-navigator-pages/
  1. Copy main.js and manifest.json into that folder.
  2. Restart Obsidian or reload plugins.
  3. Enable Auto Navigator Pages in Community plugins.

Usage

  1. Enable the plugin.
  2. Open the plugin settings.
  3. Click Initialize current vault to initialize the current vault.
  4. The plugin scans your vault and creates managed navigator pages for folders.
  5. After initialization, creating, deleting, or renaming notes and folders updates the affected navigator pages automatically.

You can also run the initialization command from the command palette.

Navigator Page Template

The default template contains a user-editable description area and a generated navigator area:

## Description

Write folder notes, project background, or useful links here. The plugin will not edit this section.

{{navigator}}

The {{navigator}} placeholder is required. The plugin replaces it with the generated navigator section.

About _node

The _node folder collects lower-level notes created from ordinary notes through wiki links. This keeps frequently used first-level project notes visible in the working folder, while detailed sub-notes can live in _node.

The plugin does not move notes into _node when they are created from:

  • The file explorer.
  • A managed navigator page.
  • A note that already has content.
  • Any workflow before the plugin is initialized.

Support

If this plugin helps you, you can support its maintenance:

Repository

GitHub: https://github.com/ccccarlos0504/auto_navigator_pages

Notes

  • File explorer pinning and sorting use internal Obsidian file explorer interfaces. Some Obsidian versions may require compatibility updates.
  • Workspace snapshots only restore the tabs and layout from the previous session.
  • Before submitting a new community plugin release, make sure README.md, manifest.json, the GitHub release assets, and the version number are consistent.