Obsidian Dashboard Gallery

The Problem

Obsidian users who want a polished home‑page must assemble markdown, CSS, and media manually. Without a curated, ready‑to‑copy set, they spend time hunting for screenshots, tweaking CSS, and guessing required plugins, which slows onboarding and reduces consistency across vaults.

What This Does

The repository supplies four complete dashboard examples—Dashboard-Atlas.md, Dashboard-Brutalist.md, Dashboard-Komorebi.md, and Dashboard-Zen.md—each paired with a matching CSS snippet in .obsidian/snippets/ (e.g., Dashboard-Atlas.css). The markdown files embed images (e.g., images/Atlas/atlas.png) and video previews (e.g., images/Atlas/atlas.mp4) and list required Obsidian plugins such as Dataview and optional QuickAdd. By copying a pair of files into a vault and enabling the snippet, a user instantly gets a functional dashboard with minimal configuration.

How It Is Wired

There is no executable code; the “wiring” is purely declarative:

File / Folder	Responsibility
`dashboards/*.md`	Provides the dashboard layout, front‑matter, and links to CSS snippets and media.
`.obsidian/snippets/*.css`	Supplies the visual styling that Obsidian applies when the snippet is enabled.
`images/*`	Supplies static assets referenced by the markdown (e.g., `![Banner](images/banner.png)`).
`README.md` and `docs/*.md`	Explain usage and multilingual documentation.
`.github/*`	Holds issue templates and contribution guidelines but no CI workflow files.

Execution flow is driven by Obsidian itself: when a user opens a copied .md file, Obsidian renders it, applies the enabled CSS snippet, and loads any referenced media. No functions, imports, or runtime code exist in the repo, so a call‑graph cannot be constructed beyond the static file references described above.

How To Use It

Clone the repo ``bash git clone https://github.com/moses-y/Obsidian-Dashboard-Gallery cd Obsidian-Dashboard-Gallery ``
Copy a dashboard into your vault, preserving the relative paths: ``bash cp dashboards/Dashboard-Atlas.md <your‑vault>/Dashboard-Atlas.md cp .obsidian/snippets/Dashboard-Atlas.css <your‑vault>/.obsidian/snippets/ ``
Enable the snippet in Obsidian → Settings → Appearance → CSS snippets.
Install required plugins (e.g., Dataview) via the Community Plugins browser.
Add any external API keys (e.g., OpenWeatherMap) to the plugin settings as described in the dashboard markdown header. No additional build or runtime commands are required.

If you wish to use a different dashboard, repeat step 2 with the matching pair of files.

Real‑World Use

A knowledge‑worker maintains a personal vault for research notes. By cloning this repo once and copying Dashboard-Zen.md + its CSS snippet, they obtain a glass‑morphism home page that displays weather, a habit tracker, and a task pipeline—all powered by Dataview queries already embedded in the markdown. No further scripting is needed, reducing onboarding time for new team members.

Code Health & Issues

Medium – Large binaries – images/Komorobi/komoribe.mp4 (9.6 MB) and images/Brutalist/Dashboard‑Brutalist.mp4 (6.0 MB) exceed 5 MB; they increase clone size and CI checkout time. Fix: track .mp4 files with Git LFS or host them externally and fetch at setup.
SDLC observations – No test files, no CI/CD pipeline, no Dockerfile, and no lockfile. The repository includes a LICENSE (MIT) and a CODE_OF_CONDUCT.md, but lacks automated quality gates.

The Bottom Line

The repo delivers a straightforward, copy‑and‑paste solution for high‑quality Obsidian dashboards, backed by clear documentation and ready‑made assets. Its limitations are the lack of automation (tests/CI) and the presence of large media blobs that bloat the repository. It is suitable for individual users or small teams who need instant visual templates without a build step, provided they are comfortable managing the media size or moving it to LFS.