type: decision
timestamp: 2026-06-20
tags: [architecture, sites, journal]

journal-site — best features of all five journal apps

journal.oriz.in mines best features of Day One, Bear Notion, Obsidian, and Logseq into one journaling experience. Big scope chosen knowingly; flagship-grade polish target.

journal-site — best features of all five journal apps

The decision

journal-site at journal.oriz.in mines the best features of all five major journaling apps: Day One, Bear, Notion, Obsidian, Logseq. Scope chosen over the recommended “Day One + Bear + Notion only” — user wants the full feature soup.

This makes journal-site a flagship project, not a side site.

What to take from each

Day One

Bear

Notion

Obsidian

Logseq

What ties them together

The synthesis is bigger than the parts:

Tension with the auto-only-tracking rule

The existing auto-only-tracking.md rule says metrics must be auto-captured, not manually entered. Journal entries are content, not metrics — explicitly carved out in that rule. So journal-site is allowed.

But the metadata on each entry (mood, location, weather) should be auto-captured by default to stay consistent with the spirit of that rule. Manual override allowed; manual-only not allowed.

Tier B — curated TOC + recent. See sidebar-4-tier.md. The curated TOC is the templates list + section navigation; “recent” is the last 5 entries.

Why scope-creep is OK here

User picked “all five apps” over the recommended 3-app subset. Reasoning that survived:

The risk-mitigation: ship in vertical slices. Don’t try to ship everything at once. Phase 1 = Bear’s typography + Day One’s daily prompts + Obsidian’s plain-markdown storage; Phase 2 = Notion’s databases + templates; Phase 3 = backlinks + graph; Phase 4 = E2E encryption + auto-capture.


Edit on GitHub · Back to index