This looks really cool! I can't wait to check it out. I've been using various personal wikis for years, and this hits most of what I am looking for. But, I'd

This looks really cool! I can't wait to check it out. I've been using various personal wikis for years, and this hits most of what I am looking for. But, I'd like to offer some suggestions. - It would be cool if you would consider some tweaks for how the text is rendered. It can still be Markdown compatible, but for example allow linebreaks to be interpreted as linebreaks. Text used for reference often has different needs than what is being exported to HTML. - Git integration. I just use git for syncing my knowledge bases. It makes the most sense for my multiple devices, and it is very rare that I even have conflicts and can't automatically merge differences. I actually have a script that lets me use Dropbox or another syncing provider to sync my working tree, separate from the repo itself, so that my history isn't polluted with excessive automated commits, but it is still tracked relative to where it was checked out, and resolved automatically. That way you can have the strengths of git without the drawbacks. You may also want to check out git-annex/datalad. I combine it with my home grown Markdown wikis for embedding references to files in my wikis, keeping my git history just pure text. One of my goals is to bridge file management with text management. I'd be happy to share any of this if you're interested. I've had plenty of free time recently to further develop it.