Get AI summaries of any video or article — Sign up free
Obsidian Dashboard Setup: Plan & Track Your Life in 2024 With Obsidian(Showcase) thumbnail

Obsidian Dashboard Setup: Plan & Track Your Life in 2024 With Obsidian(Showcase)

Prakash Joshi Pax·
5 min read

Based on Prakash Joshi Pax's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Build the vault around templates (goal, daily, weekly) so inputs are standardized and metadata is consistent.

Briefing

A personal “life OS” built in Obsidian turns goal setting, daily reflection, weekly review, and task management into a connected system—so progress updates automatically instead of relying on manual bookkeeping. The core idea is to structure a vault around templates and metadata-driven widgets: goals get a progress bar tied to frontmatter, daily notes track productivity and habits through the same metadata, and dashboards pull that information into calendars, tables, and card layouts.

At the center sits a homepage hub (“OB cdan lifeo”), designed as a control panel for the whole setup. It includes a banner with quick-action buttons (open daily/weekly notes, view tasks, toggle light/dark), a goals and habits multicolumn section, a satisfaction heat map calendar, and panels for recently created and recently updated notes. The homepage also features a heat map view based on a numeric property (0–10) and a modular CSS layout that switches between card and table styles depending on enabled CSS snippets.

Goal tracking is anchored by a “goal template” that defines key properties such as area, progress, target, start date, deadline, and completion date. A progress bar widget is wired to metadata using the Meta Bind plugin: dragging the slider updates the underlying frontmatter automatically. The template also uses Banner plugin styling for a gradient header and includes callouts (info/success/danger) plus a set of goal prompts adapted from Improve.app-style questions. A recurring method for strengthening commitment is a “why” chain: when setting a goal (example given: gaining 20 kg), the user repeatedly asks why it matters until reaching a deep root reason.

To make goals visible at a glance, a “goal dashboard” uses the Data View plugin with JavaScript queries. Goals render in a card-based layout (via Minimal theme CSS) and can be filtered and displayed through customizable Data View queries. The daily note template then extends the system: it auto-inserts the date and links to previous/next daily notes using the Templater plugin, tracks “how proud am I” on a 1–10 scale via Meta Bind progress bars, and provides a habit tracker where checkmarks toggle habit completion while updating metadata. Journal prompts capture daily wins and new tasks.

Weekly review follows a similar pattern. A weekly note template uses Periodic Notes and Templater scripts to generate week identifiers and navigation links to adjacent weeks, plus a link list to daily notes within the week. It adds a life-balance tracker (health, wealth, relationship, spirituality) using Meta Bind progress bars and a weekly wins section that writes back into metadata.

Task management is handled through Obsidian Tasks plus two custom views: a Kanban board built with the Cardboard plugin (date-board option) and a task calendar/timeline built with Data View JavaScript and CSS/JS assets. A task dashboard summarizes today’s tasks, overdue items, and unplanned tasks, and can be pinned to the sidebar for constant visibility.

Overall, the system matters because it reduces friction: templates standardize inputs, widgets write to metadata, and dashboards read that metadata to keep planning and tracking synchronized across daily, weekly, and task views—without manual updates to multiple screens.

Cornell Notes

The setup builds a metadata-driven Obsidian system for planning and tracking life in 2024. Goals use a goal template where a Meta Bind progress bar updates frontmatter automatically, and a goal dashboard uses Data View JavaScript queries to display goals in card or table layouts. Daily notes use Templater to generate dated notes and links to adjacent days, then track “proudness” (1–10), habits, and journal prompts while writing results into metadata. Weekly notes use Periodic Notes plus Templater scripts to create week navigation and a life-balance tracker (health, wealth, relationship, spirituality). Task management integrates Obsidian Tasks with a Kanban board (Cardboard) and calendar/timeline dashboards (Data View + provided CSS/JS).

How does the system keep goal progress from becoming manual work?

The goal template defines a numeric metadata property named progress (0–100). A Meta Bind progress bar element is directly attached to that property, so dragging the slider updates the note’s frontmatter automatically. The same pattern repeats in daily and weekly templates: progress bars and habit toggles write back to metadata, which dashboards later query.

What makes the daily note template “connected” to the rest of the system?

Daily notes are generated with Templater, which inserts today’s date in a specific format and creates links to the previous and next daily notes. The daily note also includes a Meta Bind progress bar for productivity/proudness on a 1–10 scale and a habit tracker where toggles/checkmarks update metadata. Because those values live in frontmatter, homepage heat maps and habit queries can aggregate them later.

How does weekly review work without losing navigation between days and weeks?

Weekly notes rely on Periodic Notes to create week-based files using a format like YY y ww (example shown: 2024 01, 2024 02). Templater scripts add week identifiers and links to previous/next weeks, plus another script that links to all daily notes within that week. This keeps weekly review anchored to the underlying daily entries.

What role do Data View JavaScript queries play in dashboards and calendars?

Data View JavaScript queries act as the “read layer” for metadata. The goal dashboard uses a Data View JavaScript query to render goals in a card layout (or table layout if card CSS is disabled). The homepage uses Data View queries for multicolumn goal/habit views and for recently created/updated lists. Task calendar and task dashboard views also use Data View JavaScript to render task schedules from Obsidian Tasks and daily-note task data.

Why are CSS snippets and modular layouts important in the homepage design?

The homepage’s multicolumn and card/list presentation depends on modular CSS snippets (notably MCL Gallery cards, MCL multicolumn, and MCL wide views). Enabling or disabling specific CSS changes how Data View outputs render—switching between card-style and table-style layouts. The system also uses Minimal theme card CSS to control whether goal tables appear as cards.

When is Obsidian a good fit for task management in this setup?

The creator frames Obsidian as suitable for personal task management rather than project-level or team-based task assignment. The setup uses Obsidian Tasks for the underlying task data, then builds personal views: a Kanban board via Cardboard (date-board option) and calendar/timeline dashboards via Data View plus provided CSS/JS assets. A task dashboard summarizes today, overdue, and unplanned tasks and can be pinned to the sidebar.

Review Questions

  1. Which metadata properties are used to drive the goal progress bar, and how does Meta Bind update them?
  2. Describe how Templater and Periodic Notes work together to generate daily and weekly navigation links.
  3. What combination of plugins and CSS assets is needed to render the homepage multicolumn layout and task calendar views?

Key Points

  1. 1

    Build the vault around templates (goal, daily, weekly) so inputs are standardized and metadata is consistent.

  2. 2

    Use Meta Bind progress bars and toggles to write user actions directly into frontmatter, enabling automatic dashboard updates.

  3. 3

    Connect daily and weekly navigation using Templater scripts (previous/next links) and Periodic Notes (week-based files).

  4. 4

    Use Data View JavaScript queries as the reporting layer to render goals, habits, recently created/updated notes, and task dashboards.

  5. 5

    Integrate Obsidian Tasks with custom views: Cardboard for Kanban and Data View-based calendar/timeline dashboards for scheduling.

  6. 6

    Make the homepage usable by combining modular CSS snippets with card/table rendering choices and pinned task summaries.

  7. 7

    Strengthen goal follow-through by repeatedly asking “why” until reaching a deep root motivation, then align daily habits to that goal.

Highlights

Goal progress becomes drag-and-update: a Meta Bind slider is attached to a numeric frontmatter property (0–100), eliminating manual progress entry.
Daily notes are navigable by design: Templater generates date formatting plus links to previous and next daily notes.
Weekly review stays anchored to daily work: scripts link each week to all daily notes inside it, while life-balance progress bars write back to metadata.
Task views are layered on top of Obsidian Tasks: Cardboard provides a date-board Kanban, while Data View + CSS/JS render calendar and timeline schedules.
The homepage functions like a dashboard: modular CSS enables multicolumn layouts, and Data View queries populate goals, habits, heat maps, and “recent” lists.

Topics

Mentioned

  • CSS
  • JS
  • YY
  • WW