Haven't tested it so have no idea what its like. Its not native though, I think it is written with JS/HTML using Electron.
I personally prefer the separation of plain text markdown and rendered live preview.
Possibly-crazy idea: Keep writing Markdown files. Save them to a Dropbox folder. Also install Dropbox on a server or old computer or VPS. Then create a cron job that converts the entire ~/Dropbox/MarkdownNotes/
folder to HTML using pandoc
, spitting the HTML output into ~/Dropbox/HTMLNotes/
. It could run every 15 minutes or every hour or whatever. You could also share this folder via Dropbox's web interface.
The downside is you'd have two folders containing your notes in different formats, but it shouldn't be a problem if you only ever edit the markdown, and treat the HTML as view-only.
Also look into the free Linux markdown editor called Abricotine, which has a WYSIWYG-type interface. http://abricotine.brrd.fr/
That's really cool.
I have similar goals to you for remote editing and the like. Having no experience with LaTeX but being a Redditor, I ended up settling on using Markdown (and storing my works in a Git repo).
Conveniently, there are WYSIWYG editors for Markdown and easy ways to export to HTML for distribution. I'm currently following the development of Abricotine quite closely. My other like of Markdown is the way its syntax seems fairly intuitive to read plain
An example from one of my drafts:
# Chapter 8(?) ## The Hall of Records
The door was plain and black, just like everything else on the Ministry’s lowest level. A small black plaque sat in its centre, reading simply Hall of Records. Harry straightened his robes slightly and rearranged the files under his arm, before pushing open the door and stepping inside.