Akhilesh Upadhyay386 downloadsA native dashboard for navigating your vault, reviewing documentation health, and opening files quickly.

Documentation Command Center is a native Obsidian dashboard for exploring, searching, and navigating a documentation vault from one place.
The core dashboard works locally and offline. It does not require Dataview, JavaScript queries, telemetry, or a cloud service. Dataview is an optional integration used only by the My lists tab.
LIST queries from plugin settings.Shows the configured vault scope and exposes the complete folder hierarchy. Each folder can be bookmarked or pinned as the active temporary root.
Shows files contained by saved folder bookmarks using the same tree, search, filter, count, gallery, and navigation experience as Vault tree. Bookmarks are stored in Obsidian plugin data and are updated automatically when folders are renamed or deleted.
My lists is optional and requires the Dataview community plugin to be enabled. Create saved lists in Settings → Community plugins → Documentation Command Center. The first version supports the following form:
LIST
FROM #go
SORT file.name ASC
Each saved list has a title and query. Select a title in the tab to render its matching files through the shared dashboard tree. SORT file.name DESC is also supported. Invalid or unsupported queries show an inline error without affecting the other tabs.
For the normal user installation:
No manual file copying is required when installing through Obsidian’s plugin browser.
For a manual install from a GitHub release or a locally built plugin:
main.js, manifest.json, and styles.css into:
.obsidian/plugins/documentation-command-center/Dataview is only needed if you want to use My lists.
Open Settings → Community plugins → Documentation Command Center to configure:
Bookmarks and saved lists are persisted in Obsidian’s plugin data. Search, filters, pinning, selected tab, expansion state, and gallery selection are session state and reset when the dashboard view is reopened.
The dashboard enumerates vault files locally through Obsidian so it can support configured root folders, exclusions, attachments, media, bookmarks, and saved list results. The configured scope and exclusions are applied before rendering, and no vault data is sent to a network service.
The dashboard provides vault navigation, health metrics, search, filtering, recently updated notes, expansion controls, folder counts, bookmarks, pins, and the three navigation tabs.

The settings interface brings together vault scope, excluded paths, recently updated limits, default tree behavior, file type preferences, and saved Dataview lists in one place.

The gallery provides keyboard navigation and previews for images, media, and other supported vault files.

Native Obsidian note links retain their path tooltip and hover preview behavior.

Requirements: Node.js 18+ and npm.
npm install
npm run dev # watch build
npm run build # production build
npm run sync:local # build and install into the configured local vault
npm run lint
npm test
The generated main.js is a release artifact and is intentionally ignored by Git.
For local testing, sync:local copies main.js, manifest.json, and styles.css into:
/mnt/work/workspace/docs/.obsidian/plugins/documentation-command-center/
Update the destination in package.json if your development vault is elsewhere, then reload the plugin in Obsidian.
The release tag must exactly match the version in manifest.json without a leading v. Attach manifest.json, main.js, and styles.css as individual release assets.
Each GitHub release should include a concise description of the user-visible changes, fixes, compatibility notes, and any required plugin dependencies such as Dataview for My lists.
The intended repository is akhileshu/documentation-command-center.
Before submitting to the community catalog, review the Obsidian plugin guidelines and developer policies.
PluginSettingTab API so the plugin can retain its current minimum Obsidian version.00 - Command Center is reference material and is not part of the supported native plugin runtime.The original DataviewJS implementation and visual design notes remain under 00 - Command Center as migration reference material. They are not required at runtime; the native plugin is the supported implementation.
0-BSD. See LICENSE.