Eliminate the concept of pages

[alex0]

@ronsu

The actual structure (pages-blocks) is fine. But the all-blocks in a DB version is even better because is more flexible. And it’s proved again and again by succesful outliners like Workflowy or Tana.

None of them use references to tag blocks and their children, right? To my knowledge only Roam Research and Logseq do and they both have the concept of pages.

Anyway, wouldn’t it be better if we had the following option to treat specific blocks as pages?

Option to treat specific blocks as pages

Premise In Logseq references to pages are used to tag content. But pages are also the “root blocks” because each block is a child of a page. Problem When trying to figure out if something must be a block or a page, the difference is: A block is placed in a context and in the outliner hierarchical structure and so it is great to organize stuff. But since they are not in the graph you would lose important connections (references in the block, in its children or its path). A page will be a no…