Headers in markdown to become parent blocks

[sotn3m]

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?

[laughedelic]

Am I missing something, or is this still an issue in 2024? Maybe there is some configuration option for this?

I also expected it to threat headings as hierarchy markers without actually changing the underlying markdown. I don’t think that - ## title is even a valid markdown in the way most other editors understand it. So when Logseq adds bulletpoints everywhere without the real need, it makes the documents unusable in other applications.

[laughedelic]

I just found this thread with some very relevant discussion, but no conclusion:

Allow non-outline (freeform) text

Hi all! I’d like to use logseq as an outliner, like one can use Word (in the good sense now). So, if I have a file like this: # This is h1 Some text ## This is h2 Text under h2 ## Another h2 Some text It should render as: [image] not as: [image] Note, that this rendering went through a great progress! However, if I format the text in Logseq, the markdown file turns to this: - # This is h1 Some text - ## This is h2 collapsed:: true Text under h2 …

Allow non-outline (freeform) text

One of the things I don’t understand is why Logseq doesn’t simply use typical OPML outliner-markdown conversion conventions as the basis for alternative views. Here Bullets=Headers Lines and paragraphs in a note under the bullet are converted to text under a header. The only decision required is how to handle deeper hierarchies. H7 , 8 etc is not uncommon. Lines starting - are treated as bullets within bodytext. There’s no obvious reason why Logseq couldn’t offer this as an alternative view …