> [!tldr] A type note. A template. A filter-based view system. This is how my [[Obsidian Journal]] works now. Notes have [[Systems Composability|composable]] types. There is no effectively folder-based organization. Everything operates on [[Obsidian Bases]] and views. > [!tip] TL;DR > ![[Pasted image 20261027160952.png]] Not meant to be "formal", but here's the pattern that's emerging in my new [[Obsidian]] system (which is basically just [[Kepano's Vault]]). It uses a tiny bit of [[Simple Interchange Grammar for Identity and Linking|SIGIL]]. Types are created **as they are needed**. Originally I mimicked [[Kepano's Vault]] exactly, but quickly realized I didn't need (nor want (nor fully understand))) many of his types... and I had a few of my own I wanted. ## Base Metadata Keys shared by essentially all notes. Mostly set using Templates & my [[Auto-properties Plugin]]. - `_type` - `_created` - `_updated` - `_id` ## A Type - Create ==only as needed== - Has a **type note** named after the type - e.g. `[[Person]]` - describes the type - acts as a view for that type - Has a `Template` - with `_type` pre-filled - with other metadata ready to go - Using [[#Common Property Keys]] where possible - Likely has a `View` - Likely has a `Module` or two - referring to "this" ## Common Property Keys To make it possible for a Base to meaningfully display multiple [[#A Type|Types]] at the same time - I have a small set of [[Frontmatter]] keys that have a common meaning that can be used on any note/type. - Text - **tldr** - **img** - **url** - Date - **timestamp** - When a thing took place - Number - **rating** - List - **next** - **people** - Value `_type` = [[Person]] - **period** - Value `_type` = [[Period]] - **location** - Value `type` = [[Location]] **** # More ## Source -