Folders are a weak ontology

Putting a note in backend/redis/ forces one primary category. Real topics span layers: caching touches auth, billing, and ops. Wiki links express many-to-many relationships without copying content.

What stays in the file

  • Body text, code fences, and images—standard Markdown.
  • Optional YAML frontmatter for tags, status, or dates.
  • [[Wiki links]] and embeds like ![[Related note]] where supported.

What the app adds at read time

  • Backlink index — who points here?
  • Graph — what cluster does this note belong to?
  • Search across titles, bodies, and tags.
  • Rename propagation — update link targets when a note moves.

Choosing a Markdown-native app

Avoid lock-in: if you cannot open the folder in another editor tomorrow, you are renting your vault. Lunote, like Typora and Obsidian, treats the directory as the vault—but emphasizes comfortable writing and built-in linking without requiring a plugin stack to get a graph or export to PDF and Word.

The best knowledge system is the one whose files you would still want if the app disappeared tomorrow.