countdown
Dashy vault/Reference/countdown
Reference/countdown.md

countdown: what is coming

Properties
code block
countdown
keys
3 on the block, 10 on each date
checked on
Dashy 2.2.0

Cards counting the days to a date.

Prefer to have your agent write it? Build a dashboard with an AI agent.

From the demo vault

countdown
```countdown
columns: 3
items:
  - { label: IRONMAN 70.3, date: 2027-06-14, icon: 🏊 }
  - { label: Holiday, date: 2027-01-20, icon: 🏖, sub: two weeks off }
  - { label: Review, date: 2027-03-01, icon: 🗒 }
```
renders as
Three cards counting the days to a race, a holiday and a review

A minimal block

The shortest config worth pasting. Change the folder and the property names to yours.

countdown
```countdown
columns: 3
items:
  - { label: IRONMAN 70.3, date: 2026-11-15, icon: 🏊 }
  - { label: Holiday, date: 2026-12-20, icon: 🏖, sub: two weeks off }
  - { label: Birthday, date: 1990-05-12, repeat: yearly, icon: 🎂 }
```

Keys on the block

KeyWhat it doesTypeDefault
columns columns in the grid, 1 to 6. On a phone a block never shows more than two columns number 3
date_format a date format for field values and for the note names that pick the newest note, when they are not written as YYYY-MM-DD, in moment notation like DD.MM.YYYY. Applies to every card, read the way a stats card reads it; a written date stays YYYY-MM-DD. Month and weekday names (MMMM, dddd) are read in Obsidian's language, or in the Plugin language setting when one is picked text none
items required the list of dates list none

Keys on each date

Each entry under items is one date.

KeyWhat it doesTypeDefault
label requiredalso title, name what the date is text none
date the date itself, YYYY-MM-DD. Required unless field is set, and not allowed together with it: exactly one of the two text none
fieldalso property, prop a date property to read the date from instead of writing it: 2026-03-02, with or without a time after it, one in the block's date_format, or an Obsidian date property; dotted for a nested one like meta.expires. By default read from the newest note in the selection that has it filled in, the way agg: latest picks one: by the date in the note's name, and a note without one, like Passport.md, after every dated note; pick: next reads every note instead and counts to the soonest date. A value that is not a date, or no note having the property at all, is an error on the card that names it; with pick: next a value that is not a date is skipped with a warning instead text none
sourcealso folder, from with field only: folder to look for the note in; includes nested ones. Without it, the whole vault text none
tag with field only: tag the note carries, with or without the hash text none
where with field only: a condition the note must meet, like type = passport, or several joined with and or written as a list, the same language as on a stats card text or list none
pick with field only: which note in the selection the date comes from. latest reads the newest note, as described under field. next reads field in every selected note, dated name or not, and counts to the soonest date from today on, today included, for the next race in a folder of races; the card shows that note's name as its sub unless you write one. With repeat: yearly each note's date moves to its next anniversary first, so a folder of people counts to the next birthday among them. A tie goes to the first note by path. A note whose value is not a date is skipped with a warning naming one; when every date has passed, the card shows an error naming the latest one. Any other value is an error. Next to date a valid value warns and is ignored; an invalid one is an error text latest
repeat yearly counts to the next time the date's month and day come round, today included, for a birthday or an anniversary, and shows how many years that one is: 37 years. 29 February falls on the 28th in a year without one. A date still ahead counts to itself, with no years shown. Works with date and field alike; any other value is an error text none
iconalso emoji emoji text none
sub small caption under the label; with repeat: yearly it comes before the years text none

How it behaves

  • A date that has passed is shown too, counting up instead of down. What happened yesterday is still worth seeing.
  • The day count is whole days, so a daylight saving switch cannot shift it.
  • A birthday or an anniversary repeats with repeat: yearly. A date kept in a note, like a passport's expiry, is read with field and stays current when the note changes: { label: Passport, field: expires, where: "type = passport" }.
  • A field written as 15.11.2026 is read once the block names its format: date_format: DD.MM.YYYY next to items:.
  • The next of many dates, one per note, is pick: next: { label: Next race, field: date, source: Races, pick: next } counts to the soonest race still ahead in Races and shows that note's name on the card. With repeat: yearly the same card over People counts to the next birthday.