apex-dashboard stores an entire workspace in one markdown file and reimplements a query language to read it
Stop switching between Obsidian notes. One page. Everything you need. Memo your thoughts, crush your todos, track your projects — and make it look incredible doing it.
At a glance
- What is it?
- An Obsidian plugin that puts memos, todos, project cards, a calendar, queries, web embeds and eleven sidebar widgets on a single page, persisted as plain text in the vault. It bundles its own Dataview-style engine, has no test runner, and commits its build output to the repository.
- Who is it for?
- The decision that makes this plugin different from a themed note is that the layout is a file. Your dashboard is Markdown in your vault, you edit it as text when you want to rename or reorder a section, and nothing is stored anywhere else.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 5 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 21, 2026, and from our analysis. They are not legal advice.
Star history
- PandoraReads/apex-dashboard879 ★ · +102
| Repository | 2026-09-21 | 2026-11-21 |
|---|---|---|
| PandoraReads/apex-dashboard | 777 | 879 |
102 Stars in the last 61 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
One markdown file holds the dashboard and deleting a card means editing text
The persistence model is the whole design. On first use the plugin creates a file called `dashboard.md` at the root of your vault, and every change writes straight back to it in plain text. The stated reason is that the data belongs to you, and for an Obsidian user that is the correct default: sync it, diff it, back it up with the vault, edit it in a text editor if you ever want to.
The cost is that some operations belong to the file rather than to the interface. Deleting, renaming and reordering sections has to be done in the note, and any edit made there shows up directly in the dashboard. That is a deliberate inversion of the usual relationship between an app and its state, and it works because a section is a block of text a human can read.
The path is configurable in settings, so the file does not have to sit at the vault root, and a template file for it sits at the repository root next to the plugin code. The plugin ships with no database, no index and no separate settings store for the layout itself.
That also bounds the feature list in an interesting way. A memo card, a todo list, a project card and a calendar are all things you could write by hand in the same file, which is presumably why the plugin can afford to make the file the interface rather than a rendering of hidden state.
There is no test runner, each check is an esbuild bundle run through node
The verification scripts in the package manifest are unusual enough to be worth reading directly:
"test:weather-mapping": "esbuild scripts/verify-weather-mapping.ts --bundle --platform=node --format=cjs --outfile=node_modules/.tmp/verify-weather-mapping.cjs --alias:obsidian=./scripts/obsidian-stub.ts --log-level=warning && node node_modules/.tmp/verify-weather-mapping.cjs",There is no test framework in that list, no runner and no assertion library. Each check is a standalone TypeScript file in a scripts directory, bundled on the spot with esbuild into a temporary directory under node_modules and executed with node. Most of them alias the obsidian module to a local stub, because the real one only exists inside the Obsidian application. The others bundle without that alias, which tells you which parts of the code they are able to exercise without the host application.
The build follows the same hand-rolled shape: a type check with no emit and skipped library checks, then the esbuild config in production mode, with a development script that runs the same config without that argument.
The built output is committed. `main.js` and `styles.css` sit at the top level of the repository, and the package manifest points its main field at `main.js`. That is how Obsidian loads a plugin, so it is the correct arrangement rather than an accident, and it does mean a reviewer reading the repository is reading generated code unless they check the manifest first.
A version manifest and a lockfile sit alongside, and the screenshots and a funding button image are committed at the root too.
The query section reimplements a Dataview-style language inside the plugin
The query section ships its own engine and does not need the Dataview plugin installed. The example given is a real query rather than a sketch:
TABLE file.name, rating FROM "Books" WHERE rating >= 4 SORT rating DESCThe output types are TABLE, LIST, TASK, CALENDAR and HEATMAP. Sources can be a folder, a tag or a link through FROM, and the clause set covers WHERE, SORT, GROUP BY, FLATTEN and LIMIT. The document counts about forty built-in functions, every implicit `file.*` field, YAML frontmatter and inline fields written in square brackets.
Three of the output types do real work rather than format a table. A TASK checkbox writes back to the source note, so the query becomes an editing surface. CALENDAR draws a month grid. HEATMAP plots any numeric field as an annual contribution map.
The configuration dialog validates the query as you type and offers one-click examples, and results update only when you press the section's refresh button, so a vault with thousands of files does not re-query on every keystroke.
What the document does not say is how this dialect relates to the language the real Dataview plugin accepts. Since the plugin exists to replace that plugin for people who do not want to install it, the compatibility question is the obvious one, and it is not addressed.
The web section pre-checks embed policy and opens a logged-in webview instead
Embedding a web page inside an Obsidian pane is where a plugin stops being a text tool, and this one handles the failure cases explicitly rather than showing a broken frame.
The section first pre-checks whether the target site permits framing. Sites that allow it embed directly in an iframe. Sites that refuse it are handled differently per platform: on desktop the section falls back to a separate webview with its own persistent login state, which is what makes Google Keep and the TickTick web version usable inside it, and on mobile it shows a fallback card with a link to open the page in the system browser.
Scale is set with preset buttons from 50 to 125 percent, for dense web applications that need shrinking. Mobile is advised to embed https sites only, and the section is framed as a browsing surface: popups and downloads are expected to happen in the system browser instead.
The persistent webview session is the part to think about. It means a session you are signed into inside Obsidian stays signed in, in a pane that belongs to a plugin with read access to your vault, for as long as you leave it there. Nothing in the document describes how those sessions are cleared.
The widget sections carry the same assumption elsewhere, since the desktop layout can run agents in a webview and one changelog entry attributes a broken drag interaction to webview event handling.
The music widget holds a third-party account login inside a vault-reading plugin
One of the eleven sidebar widgets plays music, and its description includes account sign-in. You can search and play free tracks from a Chinese streaming service from the sidebar, and if you log into an account in settings, member tracks play according to what that account is entitled to. There is also one-click import from a pasted playlist link, volume and loop controls, a persisted playlist with lazily loaded cover art, and an optional floating mini player that stays controllable with the dashboard closed. The mini player is desktop only.
The widget also documents a failure mode with unusual specificity, because a changelog entry describes an intermittent error code from the service's rights check, a change to retry on an interval before judging a track, and a decision that a confirmed failure should name the song and the reason, whether membership, purchase, or regional rights, before skipping. Earlier behaviour silently skipped to the next track.
Read together with the web section, the picture is a plugin that keeps authenticated sessions for two external services while also reading, indexing and querying every file in your vault. The document says nothing about where those credentials are stored, whether they sync with the vault, or how to revoke them.
For anyone who syncs their vault across devices, those are the three questions to answer before enabling either widget.
Four themes repaint their background on a loop between 26 and 40 seconds
There are thirteen themes, and four of them are not static. The descriptions give the cycle length for each animated background: one drifts warm parchment light over 32 seconds, one runs an impressionist garden wash over 28 seconds, one moves a tea garden floor over 26 seconds, and one diffuses ink over 40 seconds. One theme is the default and the rest are named after colour families, with four of the thirteen described as near-black or pure black bases with a single highlighter colour that behaves the same in light and dark mode.
That is a continuous animation, not a transition. A 40 second loop means the background is repainting for the entire time the note is open, on a pane that can be full screen, and Obsidian is an Electron application on the desktop and a web view on mobile. Nothing in the document offers a way to stop the drift, and no setting is listed for animation at all.
The other customisation work is heavier in a different way. One release converted every theme's buttons to tinted transparent glass for visual consistency, another added a real blur inner frame with a highlight along the top edge that rises above a background image, and another added a transparency slider per colour from 0 to 100 percent, where zero reveals the Obsidian system background behind everything.
The consequence is that the visual surface is the feature, and the cost of it lands on battery and on a phone. The settings list offers a style choice and nothing about motion.
Fifty rows per group, two thousand results, and rebuilds scoped to one path
The changelog contains the most useful material in the project, because it describes what breaks at scale and what was done about it.
Rendering is progressive in the views that group. Each group or column renders fifty rows first, with a control at the bottom to expand further, and a result set above two thousand entries is truncated with a prompt to narrow the filters. The stated motivation is that a section over a few thousand files should not stall the page.
Rebuild scope was the other half. Repository file changes now rebuild only the sections whose scan range covers the changed path, so editing a note elsewhere, an incoming feed landing on disk, or an image changing no longer triggers a refresh of every database and folder section, and a section whose query result is unchanged skips the rebuild. The changelog reports invalid rebuilds caused by out-of-scope edits and image noise dropping from three sections per pass to none, with a feed delivery refreshing only its own news section.
Scroll position is preserved across a full re-render by snapshotting and replaying it, covering the widget bar, the vertical scroll areas, each section's card column, task lists and the inner lists of individual widgets.
The one visible cost of all this is a plugin that is versioned tightly. Three releases in six days, 3.6.3 then 3.6.5 then 3.6.6, with no 3.6.4, and a package version that tracks the release number exactly.
Four settings, fourteen section types, and a configuration list that is longer than both
The settings section lists four options: the dashboard file path, the style, the interface language, and how many recent documents the sidebar shows. Language covers English and Chinese.
Fourteen section types are described, in two groups. Structural ones include todo, memo, sticky note, project notes, notes without a cover, a data view, a database, a folder, images, video, and calendar. Integration ones add WeChat Reading, TickTick, and web. Drag and drop reorganises cards between sections, tasks inside a todo card, and document links between project and note cards.
The changelog describes considerably more configuration than that. Across the recent releases it adds a layout choice between side-by-side and stacked widget arrangements with height proportions, an archive destination, new-note templates per section, a target file for calendar todos, a display range for image and video sections, transparency sliders, colour scheme presets, foreground colour pickers, and a scroll-to-top button.
The two lists also do not quite line up. The performance entry describes refreshing only the news section after a feed delivery lands, while the fourteen types do not include a news or feed type by name. And a fix in 3.6.2 records a template setting that was silently dropped when folder section settings were saved, which is the kind of bug that only appears when a setting has no visible control.
For a plugin this configurable, the settings documentation is the weakest part of it.
Editorial conclusion
The decision that makes this plugin different from a themed note is that the layout is a file. Your dashboard is Markdown in your vault, you edit it as text when you want to rename or reorder a section, and nothing is stored anywhere else. That also means every feature is bounded by what a text file can express, and two of them are heavier than their descriptions suggest: the query engine is a reimplementation of a Dataview-style language whose compatibility with the real plugin is unstated, and the web and music widgets hold live third-party sessions inside a plugin that can already read your whole vault. Check three things before adopting it. Which of the fourteen section types you actually need against the four settings the document lists, because the changelog describes far more configuration than that. How big your vault is, since grouped views render fifty rows at a time and truncate past two thousand. And whether you want a music widget that can log into a commercial streaming account.
Frequently asked questions
What is Apex Dashboard?
An Obsidian plugin that puts memos, todos, project cards, notes, a calendar, queries, web embeds and quick actions on a single page, together with eleven switchable sidebar widgets. Everything is stored as plain text in a dashboard.md file in your vault, created at the vault root on first use with a configurable path.
How do I install Apex Dashboard?
From the Obsidian community plugin marketplace: open settings, go to third-party plugins, search for Apex Dashboard, install it and enable it. Manually, download the latest GitHub Release, extract it into your vault's .obsidian/plugins/apex-dashboard/ directory, then enable it from the same settings panel.
Does Apex Dashboard need the Obsidian Dataview plugin?
No. The query section runs on a built-in engine with TABLE, LIST, TASK, CALENDAR and HEATMAP output, FROM sources by folder, tag or link, WHERE, SORT, GROUP BY, FLATTEN and LIMIT clauses, about forty built-in functions, all file.* implicit fields, YAML frontmatter and inline fields. The document does not state how this dialect compares to the language the real Dataview plugin accepts.
What sidebar widgets does Apex Dashboard provide?
Eleven, each independently switchable and drag-sortable: weather from Open-Meteo with no API key, a lunar almanac, a pomodoro timer with a statistics page, a reading tracker, a countdown, an annual progress view, a calendar, a habit check-in with streak and heatmap statistics, bookkeeping with CSV import and export, a photo album carousel, and a music player. A week strip, recent documents and a scroll-to-top button are always present.
Where does Apex Dashboard store my data?
In a plain text dashboard.md file, created automatically at the vault root the first time you open the dashboard, with the location configurable in settings. All changes are written straight to that file. Deleting, renaming and reordering sections must be done in the note, and edits there appear immediately in the dashboard interface.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/pandorareads-apex-dashboard)Star history chart for your README
[](https://hysenlabs.com/projects/pandorareads-apex-dashboard)Was this useful?