Hacker News new | ask | show | jobs
by kevinslin 1927 days ago
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

- 3) Yes. We don't have full text search but vscode text search is quite good, especially if you combine it with the [search editor](https://wiki.dendron.so/notes/692fa114-f798-467f-a0b9-3cccc3...) which lets you create new docs from search results. we also have guides on how to use dendron with elasticsearch [here](https://wiki.dendron.so/notes/401c5889-20ae-4b3a-8468-269def...)

- 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!

1 comments

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/