Abstract

This is my attempt to get closer to a block-reference architecture (SiYuan, Logseq) inside Obsidian – without any extra vibe-coding.

Please leave a comment if you like the material. Right now I specifically want feedback from people who use the same Obsidian features I do – to hear suggestions and questions, and figure out what could be improved. Thanks.

How it works?

In day note creation simulation

Features

• Automatic note creation from a template
• Capturing and adding a note to the Daily Journal page
• Collapsing and expanding callouts
• Capturing the active page onto the Daily Journal

Context

I really love the block-references approach in editors like SiYuan or Logseq.

The Problem

• Obsidian has a page-based architecture, so I had to adapt (with block references everything is far more convenient).
  • If Obsidian only has pages, then the page becomes the minimal block.

Three things remained fundamental

1. Daily Journal
   1. Because I like the idea of a "single window". I have almost no folders – everything works through backlinks. So the Daily Journal is not just a feature. It's the heart of the vault.
2. Outline formatting
   1. Since my WorkFlowy days I've understood that taking notes – and especially working and thinking – is, for me personally, more comfortable in "nested bullets" format. That's what sold me on Logseq in the beginning.
3. Frontmatter properties
   1. Following from point 1, everything rests on links, so I stick to the rule – the more links, the better. Yes, the Graph becomes less pretty, but the practical benefit – namely the number of points through which I can reach information – grows, raising the chances of actually finding the note I need.

And Bases too: more properties = more flexibility, even with the Better Properties plugin.

Here is the main template of a content unit inside the vault.

---
aliases:
date: '[[05-10-2026]]'
related:
type: "[[{{fixed by template}}]]"
note-type:
  - "[[{{fixed by template}}]]"
note-related:
  - "[[{{enter from suggestions}}]]"
note-about:
  - "[[{{enter from suggestions}}]]"
---

Over 3 years of working in Obsidian, I've split all my notes along several axes

• note-type – the type of note. Answers "What is the note?". All of them are baked into QuickAdd.
  • Bookmark
  • Observation
  • Idea
  • Knowledge
  • ... and so on
• note-related – the context of the note. Answers "In what context did this note come about?". This will be unique for everyone; mine are verbs.
  • Working
  • Thinkings
  • Walking
  • ... and so on
• note-about – the topic of the note. Answers "What is the note about?". Also unique; mine are nouns.
  • Family
  • Mind
  • Sport
  • Money
  • ... and so on

And there's one more note, just "Note", with no pre-filled properties. It's for when I can't determine the note-type of the information.

This is already the second version. It mostly differs in CSS – the standard callout rendering is turned off so the page looks more uniform.

>Few words about type: This property sets a category above note-type. If note-type answers the question "What is the note?", then type answers the question "What is it?" – for example: Note, Flashcards, Task, Project.

What next?

Right now I'm testing a version where these embedded callouts live comfortably inside nested outline bullets.

System requirements

• Daily Journal
• QuickAdd
• Templater
• Outliner

Inspired by

• https://community.obsidian.md/plugins/feed-bases
• SiYuan, Logseq

Hello team!

Thanks for your product, i've been using paid version for two years even you've launched totally free version, i'am doing it because want to support the greatest health app! But, fellas... every time i spend time in Bevel my 16 Pro Max is overheating, it force me to quit app, but i won't do it, you know :) Also, while syncing and few time after the process UI are freezing, so i need to wait for some time before do something.

You are doing great updates, so may i ask you to optimize the performance in one of the following update.

Kind regards, your user!