層級化的優點可以參考 Dendron 創辦人 Kevin S Lin 在A Hierarchical Tool for Thought裡面的這段文字：
- You can create, find, update, search, and remove information by looking up their hierarchies.
- You can remember your hierarchies with schemas, custom metadata to describe and enforce the shape of your hierarchies.
- You can transform your hierarchies, either a single note or an entire hierarchy at a time.
- You can combine hierarchies with other constructs like tags, backlinks, and note references.
- You can capture chronological as well as ad-hoc information using Dendron's builtin hierarchies
- You can visualize your hierarchies through hierarchical graph views
- You can share any subset of your hierarchy as a published site.
- You can move your notes and their hierarchy to any other tool.
但層級化架構的問題在：一個筆記不一定只出現在一個地方，因此過早思考他的「層級」與「位置」可能會讓使用者感到阻力。
對於這種是否選擇層級化的兩難，我覺得透過「Daily Journal/notes」這種固定的格式來紀錄是個好方法。
從整個筆記庫的架構來看，Daily Journal 本身就是一個僵固的類別，層級與位置不需要動腦就可以產生。
但以個別筆記來說，Journal 裡的內容仍可以擁有彈性，並且可以透過 tags, backlinks 以及 embed notes （在 Dendron 裡面叫做 note references）來達成交互參照以及讓同一筆記出現在不同地方的需求。