Most markdown editors structure content more or less like this:
# title
## header
Paragraph
- point 1
- point 2
Logseq quickly wants to convert it to something similar to:
- # title
- ## header
Paragraph
- point 1
- point 2
This is understandable, but there is a problem: logseq treats “header” (merged with “Paragraph”), “point 1” and “point 2” as siblings when in fact I would expect “header” to be a parent of all three: paragraph, point 1 and point 2.
I believe this was an intent of this post - I do not understand why it was moved to outline overview. @pihentagy, do you agree?
I understand that supporting both headers (##) and lists (-) would needlessly complicate syncing between logseq database and markdown files.
However, is there a way to import standard markdown into logseq in a way that would use headers as parent blocks?