Headers in markdown to become parent blocks

[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 …