What makes LEO great for consistent larger documentation is that one can write things like footnotes or a glossary in nodes which can be linked into multiple pages - much like files witj multiple hard links in a file system.
Also, it can re-read exported generated files into a structured outline, which is managed under version control.
Also, good support for literate programming, which is Don Knuth’s perhaps greatest idea.
Interesting. First time reading about it*. Were it not for you, this might have been completely off the radar. So thank you for mentioning it!
Yeah, it has been slowly growing on me 😜. But I would like to explore all other options before I fully commit.
What makes LEO great for consistent larger documentation is that one can write things like footnotes or a glossary in nodes which can be linked into multiple pages - much like files witj multiple hard links in a file system.
Also, it can re-read exported generated files into a structured outline, which is managed under version control.
Also, good support for literate programming, which is Don Knuth’s perhaps greatest idea.
You’ve already discovered the best editor. There’s no need to explore more. ;)
Hehe 😜. Perhaps the purpose of this exploration is to cement the idea that I’m already on the best 😂. We’ll see 😉.