markdown-preview-enhanced VS scrivomatic

I tried out Dendron a few months ago for personal note-taking, technical docs, and organizing tasks. I was excited at first, but overall the cons outweighed the pros for me.

Pros/exciting things:

1) There's a simplicity in using VS Code for writing notes and docs if (and probably only if) you already spend your day in VS Code, like I do.

2) The Markdown Preview Enhanced VS Code extension (which is a dependency of Dendron) is super cool for having so many "batteries" included. For example, check out all the diagram types it supports: https://shd101wyy.github.io/markdown-preview-enhanced/#/diag... . I still use it, separately from Dendron.

3) Storing my data as plain text on disk (backed up by GitHub or Dropbox) has nice properties compared to how SaaS apps do it (e.g. if you use Notion, say, your data materializes out of "the cloud" when you launch the app, and otherwise has no tangible existence). When my data is plain text on my local disk, I own it; I know I can export it, I can run whatever editor or program on it; I can access past versions (via git or Dropbox); I don't have to worry about it being corrupted, or accidentally deleting some of it, or not being able to access it because of server issues, or not being able to export it, or being offline, and so on.

4) The Dendron docs ("wiki") site is created using Dendron. It's a cool thought that I could create a nice website of documentation or notes without leaving VS Code.

Cons:

1) Can't access my notes from mobile.

2) Major warts in navigating between notes. Each note has a tab for editing it and a tab for viewing/previewing it. Opening a note behaves differently depending on which tab is focused. Clicking links to go from one note to another doesn't work very well.

3) Poor full-text search (just VS Code's code search).

4) You can't specify an order for notes, only unordered hierarchy, and you can't easily view multiple notes at once, which means keeping lots of short notes, or using different notes for different sections of a document, doesn't really work. There's a tension in any note-taking tool between short notes and long notes. Should notes be as short as possible? Or stretch into long documents? The ideal tool IMO would blur the difference between an ordered hierarchy of sections within a document and an ordered hierarchy of notes within some grouping. Dendron makes it seem like it is for keeping thousands of small notes, but the ways in which you can view, organize, and navigate between notes (lack of good "browse," search, links, lists, seeing multiple notes, next/previous note, and so on) are so limited that it makes more sense to write long documents. In which case, all you really need is Markdown Preview Enhanced and the file system.

My favorite implementation is Markdown Preview Enhanced, to be exact, @shd101wyy/mume, but I want a little more features...

Editor preview: Yes

And one of the best tools to create PDF is Visual Studio Code, if you know how to use Markdown Preview Enhanced properly. (I've just noticed that I can use this in Atom as well.)

I'm a graduate student who's trying to beat the dissertation submission deadline by attempting to speed the writing process up by using Scrivener. I've got a really exciting research topic, but I'm super overwhelmed by the technical side of things like setting up the right formatting style and importing citations and bibliography from Zotero.I could not, for the life of me, figure out how to correctly use markdown as Scrivener also has styles and is essentially a WISIWYG text editor. Granted, I had never used markdown before, but I'd thought I'd be able to master it on the go. Nope. Instead, I wasted hours upon hours trying to get systems like Scrivomatic and Scrivener for Scientific Writing to work. It bore zero fruit. Some scripts gave mysterious error messages at random. Results compiled in Scrivener using Pandoc were just utter trash with misplaced headings and incorrect formatting. Installation of Zotpick (a shortcut for quickly copying references from Zotero) succeeded, but then it just didn't work (looks like the project has got outdated). Every attempt to get things under control spiraled into yet another rabbit hole.