Why NoteGit?
There are dozens of note-taking apps. Here is why NoteGit exists and what it is good at.
You own your notes
Your notes live in a GitHub repo that you control, written in markdown - a portable, widely-supported standard read by every editor, publishing platform, and static-site generator out there. A single markdown file can hold many notes; how you organise them is up to you. No NoteGit-only database, no cloud subscription tying you to a vendor. If NoteGit ever disappeared, your notes would open in any markdown editor without conversion.
Familiar tools
The editor is VS Code Web. Files are markdown. History is git. If you already know any of these, you are productive on day one.
Comparison sketch
- Notion / Obsidian / Bear: their database, their format, their cloud.
Great UX, but you cannot just git clone your knowledge base.
- Plain GitHub: stores the markdown, but the editor is a textarea and
there is no preview pipeline tuned to note-taking.
- NoteGit: GitHub for storage plus a workbench tuned to writing.
Use cases
- a personal knowledge base under your
github.com/<you>/notesrepo - meeting notes that double as a public commit log
- shared documentation that anyone with repo access can read and edit