I decided to play with #Logseq as a possible tool for organizing campaign notes: https://logseq.com/
I then stumbled across a minor holy war between logseq people who proclaim it is a note taking app, and so MUST use bullets for everything, and others who are confused about why a Markdown editor adds bullets to anything.
Short version - it's not a Markdown editor. It uses its own flavor of Markdown, and its purpose built for note taking ... and forces everything to use bullets.
It's unfortunate, because it looks interesting and seems like a reasonable open-source alternative to #Obsidian. It likely is ... as long as your focus is on note collection, task management, brainstorming/dumping, etc.
Me? I need something that will let me create Markdown documents the way I want to create Markdown documents ... which is without lots and lots of bullets.
@nukehavoc There is some discussion on what route to take for #logseq to embrace longhorn writing.
This is probably the main issue to track: https://discuss.logseq.com/t/longform-writing-in-logseq/3527
The team doesn't actually care about those feature requests but implements features no one asked for. Indeed that request for longform writings is 1,5 years old and there are not even official statements about it despite it is popular
