Repository navigation
Why did you choose Markdown instead of a traditional database? #27
Answered
by
XY-code1
Cvessel-prog
asked this question in
Q&A
|
Why did you choose Markdown instead of a traditional database? |
Answered by
XY-code1
Nov 11, 2026
Replies: 1 comment
|
We chose Markdown because personal knowledge should remain readable, portable, and easy to migrate. Users should not be locked into a proprietary database format. Markdown also makes it possible to integrate with tools like Obsidian and Git-based workflows. We may introduce additional indexing or caching layers when needed, but Markdown remains our intended source of truth. |
0 replies
Answer selected by
Cvessel-prog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We chose Markdown because personal knowledge should remain readable, portable, and easy to migrate.
Users should not be locked into a proprietary database format.
Markdown also makes it possible to integrate with tools like Obsidian and Git-based workflows.
We may introduce additional indexing or caching layers when needed, but Markdown remains our intended source of truth.