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.
Thanks for the thoughtful reply. Some additional details on the cons:
- 1) Mobile support. We don't have a mobile app but you can access it on mobile using tools like GitJournal or IaWriter. Admitted this is not ideal but we do plan on a native mobile solution later this year. See FAQ here: https://wiki.dendron.so/notes/401c5889-20ae-4b3a-8468-269def...
- 2) As for navigating notes, this depends on your style. If your use case includes always having the preview side by side, then navigating with Dendron is not always consistent. If you mainly use the markdown view, navigation is our strong point since you can navigate and create links without leaving the keyboard
- 4) As for order with notes, there's a few thoughts here. You can embed notes into other notes using [note references](https://wiki.dendron.so/notes/f1af56bb-db27-47ae-8406-61a98d...) and control the order there. for how it displays in the hiearchy, its alphanumeric sorting. custom sorting is something we can implement if there's enough demand. for lots of short notes, this is where I would push back. VSCode has a fantastic windowing system which lets you split your editor into multiple panes (that can be automatically maximized). I regularly have 5-6 panes open at any given time that are views into different notes, sometimes the same notes. this is actually one of our strongest features since tools like notion only let you view one note at a time
I'm thankful you gave us a chance and do know that we're working on all the points you mentioned!
I think your tool might be helpful for documenting requirements, for teams that have not adopted something like BDD. And maybe for mapping the requirements to tests and source code. Have you seen examples of this?
Yep. We have quite a number of technical writers using Dendron. Dendron also integrates nicely with public projects - we support publishing docs as dendron pages with github links back to the original project. This results in publicly referencable docs that can be cloned and used locally. See example here: http://tldr.dendron.so/
Yeah, those are some of the core features that I can't live without. A lot of the reason for building in VSCode is because they have a good VIM extension :)
It’s VS Code in your browser tab, and works great.
Separately, I don’t necessarily use that, since it’s an online experience. I use Working Copy and Textastic (or other local native editor depending). Benefit of git sync and markdown. A smattering of local editors do have both Markdown and mermaid support.
Dendron's main difference from obsidian is that we put the emphasis on structuring and organizing your notes.
Obsidian (and other tools like it) focus on backlinks and using a graph to connect your ideas. This is valuable for connecting disparate ideas but its still hard to find any individual note once you have a lot of them.
Dendron helps you organize your notes into hierarchies that you can enforce using schemas (think type system but for your hierarchies)
The problem we're solving: once you have hundreds or thousands of notes, how do you find a specific one?
How are people using tools like this and Roam, Obesdian, etc. etc. etc?
Personally I could see the use if you were writing a book or something, but I feel like in practice for normal notes I would just have all of these notes that I'd never look at again or spend so much time traversing my notes and not getting things done. As someone with distractive tendencies I'd love to hear the situations where this is useful so I stay on track.
I hear the term "second brain" used a lot. The thing is with your brain, you don't actively spend time searching and traversing your "notes" consciously. Generally your mind brings things to be recalled just as you need it. Is there something like that?
A big part of my note-taking is just to get stuff out of my brain. I might never revisit any of it, and that's fine. If I write it down I know I can always go back when I need to, but if I don't, it's going to be an annoying distraction in my subconscious.
A lot of my note-taking therefore becomes an excuse to successfully ignore the things I know I don't need to pay attention to.
I do have a bunch of notes that I use for everyday stuff, however. My engineering journal is a hierarchical notebook, allowing me to go back and see all of the contributions I've made to $PROJECT, which is great come review time.
I also have a tech notes section for problems that I seem to have to solve over and over again. For example, every time we have a power outage, my Mac Mini gets stuck in a reset password screen, and I need to reset the NVRAM to fix it. I don't remember the keycode to do that, so I have a note called "Fix mac mini password reset" that tells me that it's `Cmd-option-p-r`.
Lastly, anything that might be good in a self-hosted wiki goes in my notebook; basically, my own little set of `README.md`s.
That first paragraph is exactly my experience, too. When I read "Getting Things Done", the lightning bolt that struck me was learning that simply getting stuff out of my head and into a trusted system is enough to let me stop obsessing about it and concentrate on other things.
Last week I had one of those dreaming-about-writing-code sort of nights, where I half woke up and was thinking about the stuff I'd been dreaming about and couldn't go back to sleep. I tossed and turned until I grabbed my phone, opened my notes app, jotted down some of the idea, then closed it. That alone let my mind say "ok, now I won't forget it" and I was finally able to go back to sleep.
Some people go full-on Zettelkasten, which is awesome and I'm happy for them. Turns out I really don't need all the organization. I just need somewhere to offload my thoughts where I know I can find them later, and just the process of writing them down usually gets me 99% of the benefit of having such a system.
Same here. The combo that seems to work for me is onenote combined with zotero.
- Onenote for ideas and scribbles
- zotero for bookmarks and documents. Supports tags
- physical notebook for note taking during meetings
btw you can easily connect zotero to your own nas via webdav and you have unlimited storage. Works fine for me. The only drawback of zotero is that you dont have a native mobile client.
I love Drafts for the Mac ecosystem. It has two giant things going for it:
- It opens instantly to a blank window ready for me to type into.
- It's extensible with built-in actions and JavaScript so that I can automate things like posting the text I just wrote to Twitter or Mastodon, or add it to OmniFocus, or text it to my wife, etc. etc. etc.
I believe this does not work well. At least it did not for me.
We routinely conflate todos/plans ('need to do this') , observations and patterns ('this is what i see happening when...'), events ('this happened...') and learnings ('this is what i did wrong, right...') as "notes".
I started with dropping everything in notational velocity (till it broke on my Mac upgrade) and / or 'email thyself' and like you said, it builds and its there but of little or no use. Unless its in my brain, I can't make connections. Without connections I cannot recall when I need it. It really does not help. Its actually net negative with the effort that goes into putting it in there.
I now use Google docs. One doc for each topic I am currently working on (e.g interview preparation, home purchase research, kubernetes, etc..) This builds topic wise documents which are exponentially faster to navigate/guess without needing text search or any filing system. I can skim through 1-2 documents and it provides context, history, insights, quotes in 1 place that I try and read more often which tends to stick in my head. Also given that I am more a visual learner, the place where something particular was on a document also brings in what was written next to it simply because I've seen it so often.
I’m with you, tried it but couldn’t keep up. I didn’t commit to it for very long which isn’t a fair trial, but I just didn’t see it panning out.
One thing I realized was that most of my notes were links to pages on the internet with maybe a few extra words as context, and the rest were chicken scratch step-by-step things I did setting up something nontrivially complex. For the links, now I just use bookmarks in Firefox and add tags religiously to make them searchable. For the step-by-steps... I’m not really sure what to do, thinking of running a WebDAV server on my LAN and using Joplin as a client to just contain arbitrary markdown docs.
I found Zotero (academic reference software) with the browser plugin to be a simple and very effective way to file general information, web bookmarks, Arxiv papers, conference materials, PDF books, etc, etc. My basic workflow is:
* Keep Zotero open, and navigate to one part of its collection (topic) hierarchy.
* Click on the Zotero button in the browser, to save the current web page, PDF doc, paper in Semantic Scholar etc into the currently selected place in the Zotero hierarchy.
* Zotero saves all the metadata about the object.
In parallel, I keep project specific markdown files in the folder I create for every project.
I tried Roam-like hyperlinked Markdown files for a couple of months, but found I kept wanting to keep them alongside other project-specific files.
I also use Zotero, and it supports notes, but I don't think it's very good at them. IMO, Hypothes.is takes the right approach for this. Zotero should probably overhaul its notes subsystem and add direct support for Hypothes.is (and Web Annotations) out of the box.
I use Obsidian pretty regularly. I started in earnest about 6 months ago, and I've been really enjoying it.
I like it because it's a wrapper around a folder of markdown files. I really my notes being just a folder of markdown files, so that's the selling point of Obsidian to me. I can open my notes in VSCode just as well as Obsidian, if I'm editing. Obsidian gives me some nice functionality (backlinks, hotkeys for different notes formats mostly, and just being a separate application from VSCode), but it could disappear tomorrow and VSCode would take over as my notes.
I setup a cron job to `git add .`, `git commit`, and `git push` every day, so I have my notes in a github repo that I can pull down if I ever need to switch devices. Or if I just want to look at my notes from a device, I can just browse the Github repo.
I use it for two different things:
- a daily log of my work for the day, including notes of what I did, and where each branch left off. All of my "four little things to finish this jira ticket" end up in the daily log.
- notes on various personal projects. For example, if I am looking for a contractor to prune a tree I create a note for that. I put in all the contractors I'm contacting, their bids, etc, into the note.
> The thing is with your brain, you don't actively spend time searching and traversing your "notes" consciously. Generally your mind brings things to be recalled just as you need it.
Maybe your mind does! My mind will often come back with: "there were _definitely_ 5 little todos that you needed to do to finish the branch, and I have 3 of them here ready for you. Maybe do a `git diff` to try and remember the other 2?", or "Hey, I was looking for a contractor to prune the tree. I called three of them, I think. Maybe four. Who knows. A couple sent in bids, but I don't remember which ones. Let's check gmail and see if we can find any there?".
So, personally my use of notes isn't to stop my brain trying to _come up_ with a task to complete. My notes are basically an index for when I want to resolve a task, to all the information I need to pick it up again. Or, alternatively viewed, it's the context when I put a task down, to help resume the task when I context switch back to it.
>... it could disappear tomorrow and VSCode would take over as my notes.
Yep. This is why I've been enjoying Obsidian too. I've been able to organize how I want, and it works just fine... and it keeps working, without not-so-subtly forcing me into a new structure that I don't want, just to work with it more smoothly. (e.g. Notable)
On mobile I just use some other markdown app (Epsilon is marvelous for reading). Nearly every single one works great with a folder of md/cm files. If I can't even do that, just opening plain text files works fine. The lack of lock-in is wonderful.
Software can't read your mind, so how should it know what you need right now? It's up to the user to build a system that works for him, and the user must stick with it. Software can only supporr you there, but not replace you.
Though, you can use the system of someone else and cope with it and use this person tools. But usually this does not really work well long for most people.
- I will create a folder for a topic with multiple ideas (e.g. transformers), and then put inside it a few separate files. One might contain a link to a paper or blog post and then my notes from reading that (really the most important snippets, occasionally a summarizing statement by me). Another might contain a list of ideas to try, or a pros/cons list.
- I have a folder called "book reviews" in which I put a single file per book I read. I try to write down a single sentence about each chapter, and I copy quotes I particularly like. I don't refer to these often, but it's reassuring to know that I won't have to reread the entire book to regain my state of mind.
- Very often when putting together a written document I write drafts inside the editor. I know there are "better" tools, but the writing feels organic here, since it's adjacent to notes.
- During meetings I'll sometimes make a document for the meeting, and then write down a todo list while we're discussing. This usually gets sent out as an email to the meeting participants (a very useful habit).
I use Obsidian, and have really started this in the past year, when note taking apps took off on Hacker News. Fiddling too much is kind of a distraction (I spent a few too many hours tweaking themes).
Each time, it catches my interest, I try it out, and I cannot make it work for me. It looks really fantastic with a lot of documentation, but learning curve, preview, conflicting with existing vscode plugins, etc;
I'll likely continue to try it out, because the marketing and documentation looks so good. Having spent a fair bit of time on this now, I don't think it's really possible to have a good experience with VSCode as the input.
compared to something like org-mode how complex is the learning curve here? with org you can be up and running with the basics of the notes in a few min.
My biggest gripe with note taking apps is that basically all of the ones I've seen take the IDE approach. They are not as much note taking apps as specialized document editors. Because of this I'm still stuck with Tomboy which is very far from ideal but at least it's quick and easy to start typing a new note . (Unfortunately it doesn't support markdown, only starting bullet points with typing a *, it does support wiki links, which I don't use much but it uses some xml format.)
Most notes, at least the way I work, start as just that: notes. Then some of them grow more complex and evolve into a larger document (or ideally, could evolve into multiple linked ones), but Tomboy doesn't really support it (at least if it had support for copy-ing away text as markdown...) and I really don't feel like having yet another IDE like app taking up the whole screen for every small note.
I use it and like the way it's implemented md and other format support in that you can either create a new note formatted as markdown, or update existing and previously created journals and the tool will re-render them to md: https://jrnl.sh/en/stable/formats/#markdown
I realise part of their marketing is in that their filetype is readable in 50 years when all the iPad apps are gone, but does anyone know of any iPad apps that are compatible in the meantime while it is still being used?
Phone actually, specifically. I'd love to be able to just drop in a jrnl entry without faffing with text files on iOS
If you're on the Apple ecosystem, Bear is quite nice. It's basic markdown and the only hierarchical structure is parsed from "tags" which are created by typing #tag in the document. There is some nesting too, so you can do #work/project or #personal/ideas. I've found it really intuitive and the UI/UX is clean.
Collecting, writing and managing notes are each different steps, demanding different UI&features. But writing is the step taking most time. So naturally the focus is there.
And collecting is more a matter of your setup. It's unhealthy easy to collect stuff with any mature noteapp this days.
one note on Foam vs. Dendron .. reminds me of vim vs emacs.
One of them is simple and just gets out of your way, the other is more powerful and complex and requires more investment to set up correctly to your use case. Probably different strokes for different folks here.
I tried Dendron once and was put off by the dotted namespacing (foo.bar.note.md). Would be a lot simpler if I could just use folders instead (much less clutter, and I'd be OK with specifying the folder name in links).
Not sure if the current version already allows that - but this is a common flaw with most Markdown note-taking software (I have around 8000 posts/notes spanning 16 years of hierarchies, some time-based and some context-based).
the dotted namespace has been a back and forth in our community. some people love it, some people not so much.
we're still using the dotted namespacing but we've also introduced the ability to export your notes to plain markdown (it inlines dendron specific markdown like note references to regular markdown). if you have folder based markdown, you can import them to dendron's format using our markdown importer and then export them to the same format as well (this is coming soon)
I did, and I sort of like and sort of dislike it because of the way it handles metadata.
For me, this kind of note taking app ought to use folder names as topics or categories (dev/rust) and have an index.md (dev/rust/index.md) as an entry point, and some sub-documents/sub-sections in the same folder.
Also, many of these tools only go half way: they have folder support but instead of a "bag of posts" you have to put images in a "bag of media" folder, which is even worse sometimes...
It's up to you how you use it. If you want folders being categories and have index.md'd, then do it, create them. Obsidian is very liberal in it's usage and does not enforce a specific workflow or structure.
I remember there is also a plugin which allows to use folder as notes, by loading a kind of index.md when opening the folder.
I just use awesome GistPad [2] vscode extension and add tags to notes (just array of #tag1 #tag2 in description).
This is accessible easily via various tools on ad hoc place (mobile, browser or whatever), such as GistList [1], GistPad / vscode has some good filtering features and I can download all gists locally and use any file manager to filter out tags. Its also a collection of mini git repositories with all nice things (revisions, multiple files etc.) and me not having to think about any of that.
You can easily go from there to graphs and folders and other advanced stuff (PlantUML et al are all possible via extensions) if you need them, but I have around 200 notes and do not usually need any of that. What I do need is an easy system not depending on any particular technology - all parts of it can be replaced with something else or nothing at all and still be usable with regular OTB OS tools.
Since you're doing a Show HN for a product which has previously had a full discussion [1][2], it'd probably make sense to mention what has changed.
According to the guidelines, "New features and upgrades ("Foo 1.3.1 is out") generally aren't substantive enough to be Show HNs. A major overhaul is probably ok."
I found Dendron via HN a few months ago and absolutely love it. I was hemming and hawing with my Dendron file structure until I found the PARA method (in a Dendron tutorial): https://fortelabs.co/blog/para/. I love that the dots in Dendron file names (e.g. resource.orgs.pacific-energy-center) lets me avoid the awkwardness of folders while still having hierarchical organization. I move around and make changes fast with Dendron's shortcuts. I'm opting to keep a lot of my lists (e.g. my to-do list) in Excel, and rely on Dendron more for the written-out stuff.
I'm grateful for this free open-source awesomeness!
There's a weird recursive bug I found on dendron.so where if I click the "Blog" heading, go to "Film" on the left, choose "Agents of Shield", click one of the notes to get a tooltip saying "This page has not sprouted yet", and then click the "Dendron" link in that tooltip. What I'm seeing is dendron.so within dendron.so. This process can be repeated using the inner frame.
Zettlr is great for some things. It has a couple downsides relative to something like org-mode:
It doesn't have any real outliner capabilities. Not that everyone wants an outliner, but you get it with org-mode.
It doesn't work like a wiki. In other words, if you link to a file that doesn't exist, it just says the file doesn't exist. It's kind of annoying to have to create those files manually and then reopen the document so you can add a link, even worse if you've linked to several notes you want to create.
I use org-roam extensively and create many many tiny files. Usually I start writing in daily note and simply link to the file. Then when I have something substantial I move to the linked file (automatically created when linking first time) and write stuff here. I get backlinks simultaneously so it is pretty easy to follow my chain of thoughts.
I have not seen it mentioned here a lot, but Joplin (another open-source, local-first, markdown-based, note-taking tool) also has a vscode extension (to search and edit notes in code), in addition to desktop and mobile apps. Joplin is much simpler however (no linking between notes for example), depending on what you do that may be an advantage.
I really like these in depth, detailed note taking strategies/tools, but I've come to just using markdown files with good naming. Even then, I'm getting annoyed with myself splitting up class days into separate files. I think I may even just go back to plain text.
I use markdown because it looks great when rendered to HTML, but I've only ever used my rendered notes once in three years. I always just grep them or vim search them instead. Since I'm not getting a benefit from markdown, I'm just going to switch back to text files, using one per class for the rest of the semester and a separate file for misc topics/notes.
I think I'm just not the audience for this, but I like the concept of these detailed note systems a lot, I'm just not very often searching my notes again without just using plain old grep.
At the core, Dendron is a tool to help you manage markdown files with consistent naming structures :)
And for the most part, I don't use HTML rendering but Dendron gives you easy ways of creating notes from links, creating relative links to files, and pasting images into your markdown.
I've struggled for so long to find a note-taking app.
I basically need something like Atom, VSCode, or Notepad++ (advanced text editing features) and then ability to embed images. Half of my job is taking screenshots and analyzing logs.
I use Atom for text right now, and OneNote for images, but it would be ideal to combine them. I've tried a few Atom plugins that say they can do this, but none work (possibly due to API changes over time).
This looks really cool! I'm going to give it a try. I always lose my notes. My workaround is a personal Discord server, to post notes to myself, which is nice to have a mobile app where I can share links to on mobile I want to save for later, but the different channels doesn't really provide enough structure to the notes, plus searching is not great in discord.
Do you have like a hack to post notes to and from mobile?
I built a similar tool but as a new-tab extension, basically dumps all my notes into Sqlite, simple PHP script for "sync". Just recently got the web-share-targrt on Android working so I can drop Trello.
And I built the silly "discovery" feature where it randomly pushes an old one to the top to help keep it clean.
I notice that your directory structure and markdown formatting are very similar to those that are used by static site generators such as Hugo or Nikola.
Do you have, or thought about, integration with one of these?
I like the idea of writing my notes in Dendron and being able to automatically publish them (or a subset of them).
One thing that's kind of important to me is that Dendron does not (as far as I can tell) have much in the way of outliner functionality. Other tools in this space do - for instance, org-mode for Emacs users. That would be a nice addition, given how powerful outlines can be.
Yeah, we don't do outline in the workflowy sense. we do outlines in the sense that we have shortcuts to create notes from bullets and autolink the new note. not the same but gets close. you can see an example here: https://wiki.dendron.so/notes/593206ea-5658-4874-bafd-18a138...
While Dendron is not my Core Note-Taking app yet (only use it while programming), I do have to say it is super amazing. It is one of the Best Note Taking apps out there. The founder Kevin is a super cool guy too. Recommend trying it out at least.
I tried hopping onto the Zettelkasten/self-markdown-wiki bandwagon with Obsidian but its non-commercial clause was really discouraging... so I said "F it" and returned to OneNote (which BTW does have pretty permissive links!).
I was a long one note user. I think they have great UX. I found it difficult to export from one note or drill down to something specific quickly. If it helps, we do have a bunch of former one note users as well as scripts to convert from one note to markdown
How do you learn how to write notes like this or is it natural?
The representation of my notes would be noise, but surprisingly I can find everything I want easily.
I actually started with Obsidian. It's a beautiful editor and was pretty easy to pick up. I must've built my first batch of notes in Obsidian.
I picked up Dendron due to 2 things:
1. Hierarchies leading to better note structure - I can have my notes be folders (kind of like notion)
2. VSCode - working with something extensible and familiar to me.
We have so many roam-alikes but so very few with web publishing as a first-class citizen and the ones that do have it paywalled (Roam, Obsidian) or don't support org-mode (Neuron v2 though there's plans to reintroduce), which just blows Markdown out of the water.
To be honest, I don’t see much appeal in publishing your entire unfiltered notes to the web. Synthesize interesting portions of them occasionally into coherent blog posts that other people can consume without digging through a forest of links, backlinks, and footnotes.
You should try logseq[1], been using it for quite some time now and it's coming really well. It is an Open source local-first roam alternative, it supports both markdown and org syntax and it has a lot of features like publishing, encryption, time tracking etc.
tldr: obsidian is easier to get started with and is good for free association of notes. dendron is better integrated into the development workflow and is amazing at helping you organize your notes into well defined hierarchies
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.