Vault Dashboard X

English · 中文 · 日本語 · 한국어 · Français · Español · Italiano

A dashboard for your Obsidian vault: an activity heatmap, a folder-distribution view, and configurable "quick access" links — all in one pane.

Features

• Activity heatmap — GitHub-style contribution grid showing how active your vault (or a changelog) is over time, with All / 30 days / 7 days ranges. Newest weeks are on the left.
• Folder distribution — a breakdown of your notes by top-level folder, with drill-down rows, share-of-parent bars, and "new this month" counts.
• Quick access — up to 5 configurable blocks. Each points to a folder, lists its most recently modified notes, and shows the subfolders you tick as second-level tabs. Folder names are shown exactly as they are on disk. Right-click a note for the same context menu as the file list: copy its path (Obsidian URL, vault-relative, or absolute), open it in the default app, reveal it in Finder, plus anything other plugins add.
• Two data sources — a generic "note activity" source (works in any vault) and an optional "changelog" parser for markdown changelogs.
• Six themes — Minimal Tech, Y2K Console, Coffee House, Pop Fast Food, Black Stage, and Blue Sky.
• Internationalization — English (default), Simplified Chinese, Traditional Chinese, Japanese, Korean, French, Spanish, and Italian.

Data sources

Note activity (default)

Each note contributes one "activity day", resolved with this fallback chain:

1. Frontmatter field updated (the field name is configurable).
2. Frontmatter created / date.
3. A YYYY-MM-DD prefix in the filename.
4. File modified time (mtime) — on by default. Most vaults have notes with neither a frontmatter date nor a filename date, so without this fallback the heatmap would be nearly empty. If a sync drive bulk-refreshes mtimes and creates a false spike, turn it off in settings.

Note activity works out of the box in any vault with no extra configuration.

Changelog

Counts entries in one or more changelog files. A parser reads ## YYYY-MM-DD sections and counts the top-level list items under each date:

## 2026-08-23

- Publish the July report
- Fix a typo in the style guide

> Note: blockquotes under a date section are ignored.

Each file can be a single note or a folder (all .md files inside, non-recursive).

Usage

Open the dashboard from the ribbon icon or the "Open dashboard" command.

• Overview tab — heatmap and summary cards.
• Folders tab — folder distribution.
• Click a changelog heatmap cell to jump to that day's section (changelog mode only).
• Click a folder row to drill down.

Settings

Setting	Description
Language	Interface language for the settings page and the dashboard.
Appearance	Visual style: Minimal Tech, Y2K Console, Coffee House, Pop Fast Food, Black Stage, or Blue Sky.
Activity data source	Note activity or Changelog.
Activity date field	Frontmatter field used first in the note-activity fallback chain.
Fall back to file modified time	Use mtime as the final fallback (on by default).
Changelog paths	Files/folders parsed in changelog mode.
Quick access	Up to 5 blocks; each points to a folder and lists its recent notes.
Subfolders to show	Per block: tick which subfolders become second-level tabs. Tick all and subfolders added later appear automatically.

Installation

From the community directory (once published)

Install "Vault Dashboard X" from Settings → Community plugins, then enable it.

Manual

1. Download main.js, manifest.json, and styles.css from the latest release.
2. Create .obsidian/plugins/vault-dashboard-x/ in your vault.
3. Copy the three files into that folder.
4. Enable the plugin under Settings → Community plugins.

Changelog

Full changelog — every release with what changed and why.

License

GNU General Public License v3.0

Development

There is no build step — main.js is the plugin artifact. After editing, disable and re-enable the plugin (or run Reload app) in Obsidian to pick up changes.

• Bump versions with npm version <patch|minor|major>; it syncs manifest.json and versions.json automatically.
• Run the offline data-layer sanity checks with node test/harness.js.

The release tag must equal the version in manifest.json without a v prefix; main.js, manifest.json, and styles.css are attached as separate release assets.